We have a multi-tenant shared solution that we use with Quality of Service to provide bare metal as a service and IP storage to our customers. We keep it very simple. It's an automated solution which customers configure on a portal and then it automatically configures storage for them.
The solution has drastically and positively affected IT's ability to support new business initiatives. It's a very easily automated solution using REST APIs.
Combined with OnCommand, the solution the solution helps improve the performance of our enterprise applications.
The most valuable feature is the ability to do QoS and keep customers from harming other customers in that solution.
It's very stable. We have not yet had any issues. All solutions have issues, but we have not yet had any with this one.
We scale up to 64 nodes in a cluster and then we just keep scaling clusters. We've had no issues with scalability.
We've been a partner of NetApp for a very long time. Their support is very good. We use a lot of direct NetApp engineering resources, as a partner at our scale. We tend to work hand in hand with NetApp.
For our use case, we were automating what we were doing so we chose to use the All Flash REST APIs.
Our initial setup involved a lot of development. It was complex mainly because we had to make it simple. We had to simplify it for our own customers, so it was complex for us but it's a very easy solution for enterprises.
The solution is too new for us to see ROI yet.
Dell EMC was our other option. Both Dell EMC and NetApp are partners of ours. We went with NetApp because of relationships and ease of set up.
It's a pretty stout solution. NVMe is coming and pretty much everything we want is on their roadmap.
In terms of connecting it to public cloud, we are a public cloud so we connect to ourselves. When it comes to setting up and provisioning enterprise applications using the solution, it depends on the customer use case. Some are quick, some are really complex.
The Register wrote a damning piece about NetApp a few days ago. I felt it was irresponsible because this is akin to kicking a man when he’s down. It is easy to do that. The writer is clearly missing the forest for the trees. He was targeting NetApp’s Clustered Data ONTAP (cDOT) and missing the entire philosophy of NetApp’s mission and vision in Data Fabric.
I have always been a strong believer that you must treat Data like water. Just like what Jeff Goldblum famously quoted in Jurassic Park, “Life finds a way“, data as it moves through its lifecycle, will find its way into the cloud and back.
And every storage vendor today has a cloud story to tell. It is exciting to listen to everyone sharing their cloud story. Cloud makes sense when it addresses different workloads such as the sharing of folders across multiple devices, backup and archiving data to the cloud, tiering to the cloud, and the different cloud service models of IaaS, PaaS, SaaS and XaaS.
But if we take a look at all these cloud offerings and also computing platforms in our own server room or in the data center, the on-premise infrastructure, the data landscape is NOT coherent. The data flow is not in harmony, and it is not congruent. If we imagine data as water, there is hindrance of data movement as it moves from one stage to another in the data lifecycle. This applies to almost every storage, system or cloud vendor today.
Even worse, organizations lose the control of the data along the way. When data moves out of an on-premise data center to the cloud, IT is almost passing off a large amount of control of their data to the cloud service provider.
Remember the Nirvanix story about 2 years ago? When Nirvanix went belly up, customers of theirs went to a panic mode. They were asked to remove their data within 2 weeks! One customer of Nirvanix had 20PB stored in the Nirvanix Storage Delivery Network. How the F do you think that customer would have felt in that whole Nirvanix fiasco?
This is exactly what I mean about losing control of data.
As Cloud Computing gains a much deeper foothold into IT, the data landscape does not change. The data lifecycle does not change. Data still moves from an active stage to a passive stage, and perhaps back to the active stage when needed. Along with the data movement though its lifecycle, the value of the data changes as well.
That is what the NetApp Data Fabric can do for data in any organizations. A single data management architecture that is able to have data transcend from on-premise data platforms on NetApp (or 3rd party platforms using NetApp FlexArray) to the data platforms on hybrid clouds in cloud service providers and on to the data platforms of hyperscalers, and back. All these data movement is secure, and more importantly, allows organizations to maintain control of their data, wherever it may be residing.
I have put my views of NetApp Data Fabric in the picture below (pardon my Powerpoint skills).
The underpinnings and foundation of the Data Fabric is NetApp Clustered Data ONTAP. And with the latest release of cDOT 8.3.1, the technology has reached an important milestone to realize the single data landscape architecture.
Furthermore, I cannot recall at this moment of any storage vendor or cloud service provider adopting a philosophy like Data Fabric, which means that their customers would likely encounter hindrance of data as it moves through different premises or clouds. Just like water trapped in a watering hole, eventually it will dry up or become useless.
I am not trying deride the writer of the article, but instead of sensationalizing the NetApp story, perhaps it would be better to have a deeper understanding of where NetApp is now and where they are going. From the outside, they looked to be going through a rough patch right now, but as an ex-employee, NetApp has always been my little engine that could.
The intend of my response in this blog is really to help everyone open up their eyes because it is all about a single and secure data architecture. Clustered Data ONTAP happens to be the technology that makes this happens.
Remember … Data will find its way. There is no stopping that.
