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

  • FreePBX 17 How To Add a Trunk
  • Docker Container Onboot Policy - How to make sure a container is always running
  • FreePBX 17 How To Add Phones / Extensions and Register
  • Warning: The driver descriptor says the physical block size is 2048 bytes, but Linux says it is 512 bytes. solution
  • Cisco How To Use a Third Party SIP Phone (eg. Avaya, 3CX)
  • Cisco Unified Communication Manager (CUCM) - How To Add Phones
  • pptp / pptpd not working in DD-WRT iptables / router
  • systemd-journald high memory usage solution
  • How to Install FreePBX 17 in Linux Debian Ubuntu Mint Guide
  • How To Install Cisco's CUCM (Cisco Unified Communication Manager) 12 Guide
  • Linux Ubuntu Redhat How To Extract Images from PDF
  • Linux and Windows Dual Boot Issue NIC Won't work After Booting Windows
  • Cisco CME How To Enable ACD hunt groups
  • How to install gns3 on Linux Ubuntu Mint
  • How to convert audio for Asterisk .wav format
  • Using Cisco CME Router with Asterisk as a dial-peer
  • Cisco CME How To Configure SIP Trunk VOIP
  • Virtualbox host Only Network Error Failed to save host network interface parameter - Cannot change gateway IP of host only network
  • Cisco CME and C7200 Router Testing and Learning Environment on Ubuntu 20+ Setup Tutorial Guide
  • Abusive IP ranges blacklist