Rackable Systems and their Microslice Clustered 1U Servers

I think there has been a lot of negative press towards Rackable Systems.  We will give their new solution credit that it is marketed very well, and comes prepackaged and ready to go.

But let's cut through the hype of both sides, the people who love this concept and the people who hate it.

What Rackable Systems have done is a first, to minimize space, power and costs into small servers.  This is great, and many companies have already built their own servers based on small depth Supermicro Chassis and using Desktop components.

The downside is that it seems they must be using Desktop components to achieve this since server motherboards don't typically come with single socket CPU options.  As some have pointed out, the concern is not with the RAM or even CPU chips, but if the motherboards are from Desktop Units.

Server Motherboards will always be tougher and more reliable than a Desktop board, but with that said, the idea in our minds is Rackable Systems is saying it doesn't matter.  You will have multiple systems operating in a load balanced cluster situation (at least this is the only sane minded use case assumption), so the failure of a number of servers is irrelevant.

One thing we don't buy is the "Virtualization doesn't always make senes", Virtualization allows more flexibiity and leverage, although it may pose a threat to hardware vendors which is where this rhetoric has come from.

If I were to use MicroSlice, I would make sure each server is virtualized so we can add RAM hard disk and live migrate them at any point.

In short, this practice of MicroSlice is a lot of hype, but it does offer an excellent cost and reduced power benefit.  People shouldn't be put off on the kind of hardware being used so long as they're operating in a clustered and load balanced environment.

We think Rackable Systems and their opponents both make excellent points and I hope we've walked you through the smoke and mirrors of what's being said.


Tags:

rackable, microslice, clustered, serversi, marketed, prepackaged, hype, minimize, servers, depth, supermicro, chassis, desktop, components, downside, achieve, server, motherboards, typically, socket, cpu, pointed, ram, tougher, reliable, doesn, multiple, operating, balanced, cluster, sane, minded, assumption, irrelevant, quot, virtualization, senes, allows, flexibiity, leverage, pose, hardware, vendors, rhetoric, virtualized, disk, migrate, reduced, shouldn, opponents, ve, mirrors,

Latest Articles

  • How To Add Windows 7 8 10 11 to GRUB Boot List Dual Booting
  • How to configure OpenDKIM on Linux with Postfix and setup bind zonefile
  • Debian Ubuntu 10/11/12 Linux how to get tftpd-hpa server setup tutorial
  • efibootmgr: option requires an argument -- 'd' efibootmgr version 15 grub-install.real: error: efibootmgr failed to register the boot entry: Operation not permitted.
  • Apache Error Won't start SSL Cert Issue Solution Unable to configure verify locations for client authentication SSL Library Error: 151441510 error:0906D066:PEM routines:PEM_read_bio:bad end line SSL Library Error: 185090057 error:0B084009:x509 certif
  • Linux Debian Mint Ubuntu Bridge br0 gets random IP
  • redis requirements
  • How to kill a docker swarm
  • docker swarm silly issues
  • isc-dhcp-server dhcpd how to get longer lease
  • nvidia cannot resume from sleep Comm: nvidia-sleep.sh Tainted: Linux Ubuntu Mint Debian
  • zfs and LUKS how to recover in Linux
  • [error] (28)No space left on device: Cannot create SSLMutex Apache Solution Linux CentOS Ubuntu Debian Mint
  • Save money on bandwidth by disabling reflective rpc queries in Linux CentOS RHEL Ubuntu Debian
  • How to access a disk with bad superblock Linux Ubuntu Debian Redhat CentOS ext3 ext4
  • ImageMagick error convert solution - convert-im6.q16: cache resources exhausted
  • PTY allocation request failed on channel 0 solution
  • docker error not supported as upperdir failed to start daemon: error initializing graphdriver: driver not supported
  • Migrated Linux Ubuntu Mint not starting services due to broken /var/run and dbus - Failed to connect to bus: No such file or directory solution
  • qemu-system-x86_64: Initialization of device ide-hd failed: Failed to get