![]() |
From where I sit, the storage market transition is in full swing. The era (1990-2015) where the world of “persistence” was dominated by “external” storage (aka “arrays”) is shifting to one where the majority of the growth is in SDS stacks running on industry-standard x86 hardware (leveraging a lot of NAND). These SDS persistence models are delivered in 4 “packaging” forms: a) software-only; b) bundled with servers (think VSAN-Ready Nodes, or ScaleIO-Ready Nodes); c) in hyper-converged infrastructure (appliance, or rack-scale); d) as a service (think Virtustream Cloud Storage, AWS S3, the Azure blob store, etc). While the VAST majority of the market remains externalized storage, and there remain places where external all-flash arrays continue to rule the roost – anyone denying that the inflection point is upon us has their head in the sand.
I’ll say one thing that I know for sure – there will NOT be a single SDS stack “to rule them all” – for the same reason that people who have argued for “one storage architecture” for years have been consistently and totally wrong: the design requirements for different workloads and data types are totally orthogonal. This is why I’ve always scratched my head at “VSAN vs. ScaleIO”. It’s an “and” not an “or”. If VSAN is a great choice for customers all-in on vSphere, ScaleIO is VSAN’s heterogeneous (including, but not only vSphere). I’ll go so far as to make a bold statement:
Why? Well, for starters, every time that Storage Review has a go at it ScaleIO melts their faces. The most recent example (SQL Server OLTP workloads in an HCI vs a two-tier configuration) is here. Their words, not mine (but my emphasis):
Well, for seconds, I can’t think of a transactional SDS other than CEPH RBD with this sort of OpenStack ecosystem support and integration (Cinder drivers included in all distros, Mirantis Fuel/Canonical Juju integration, Puppet, and much much more)… And ScaleIO outperforms (and similarly in resource efficiency and use) CEPH RBD by a factors of 7x-10x. Wowsers - if you’re deploying (or thinking of deploying) OpenStack using KVM, you would be crazy to not put ScaleIO through it’s paces and compare it to your other SDS choices. Missing out on a 7x-10x improvement is analagous to punching yourself in the face. Take me up on my challenge, and share what you find. GO FOR IT – the bits are here. (and Randy Bias – thanks for continually pushing!) Well, I’ll throw in a third… there is no transactional SDS that is more integrated with the container ecosystem. If there are any, please, hold up your hand, and I will update the post. There’s integration with Docker, Mesos, Kubernetes, early Photon Platform work. There’s open persistence volume controllers. There’s authentication tooling. There’s wrappers to help with Puppet, Go, Python, Flocker, and more. You can get it all (and the source code) here. BTW – if you want geo-distributed, super-duper object store S3-compliant SDS stack, you can get ECS (which also snaps into Cloud Foundry via the service broker listed at the link also :-) And finally, if you want ScaleIO delivered in the best turnkey HCI Rack-scale form, VxRack FLEX is cooking, and more and more customers are going this way every day. People talk about “web scale”. This isn’t chest-beating, it’s about bringing the lower CAPEX (because you can start smaller, and don’t need to over-plan) of SDS and HCI, but even more about the operational benefits that SDS/HCI simplicity brings to bear. This is a 16-cabinet VxRack FLEX going into a customer. Why would ANYONE bother building their own – we are making this boring. My job (more accurately the job of 2500 people at EMC and soon to be 3500 at Dell EMC) is to make infrastructure invisible. People often ask “are these ready for mission critical stacks?” Answer is “hells yeah”. A recent ScaleIO customer picked it (in VxRack form) to support their Oracle RAC cluster at the core of their business. If you’re a frequent traveller, you probably will use this system several times a week. Now, the SDS stacks don’t have all the rich classic enterprise data services (high end remote replication is one area as an example) – but in practice for most customers, the workloads that need these things are the subset, not the superset of workloads. In the example above, the customer was using Dataguard for remote replication/DR – and just needed a super-scalable, super-simple, super-performant, super-simple transactional SDS. ScaleIO and VxRack FLEX fit the bill. What does all this mean for the industry?
I’ll close with my bold black-and-white statement and let it hang out there for comments, agreement, or dispute!
Have you given ScaleIO a shot? For what? What have you found (good, bad, ugly – share!) |
