Cloud Native Storage vs Third-Party Storage - Part 5
In the first 4 Parts of this blog post we covered off; some great use cases for Cloud Native Storage solutions, we articulated that the solution you select should be primarily driven by the needs of your application, we covered off some of the leading third party cloud storage solutions in the market today and addressed some key concerns and design considerations re third party cloud storage solution.
In this final Part 5, we will address; API’s, Governance and some important questions to think about when selecting and architecting your Cloud Storage solutions.
The Third-party storage vendor needs to have a good API that will integrate with your automation solutions.
This is a key differentiator between the different solutions in the market.
The vendor needs to have good cloud native expertise to be able to work with API’s.
Look at who is developing the solutions, consider; whether they have cloud native expertise in their team? Does their API work?
Will it work in your use case with your automation solutions and applications?
These are all important factors as you can’t just port the solution you have on premises to the cloud.
Cloud products need to be updated and released more often than on premises solutions, so if the vendor is only making annual or biannual releases this can create problems in the Public Cloud when AWS and Azure are constantly changing and updating their solutions.
Data governance and compliance
This factor works in favour of third-party solutions as many of the data leaks and hacks have been on unsecured S3 storage.
Most of this has been a result of insufficient experience with designing and managing data in the public cloud storage context. In many cases Enterprise storage will have native abilities to protect data and will be more secure.
For data governance and data protection enterprise arrays will have enterprise class answers to these enterprise questions. It can be easy to think that the cloud vendors know the best way to build cloud storage.
As per the previous blog – storage is hard and is one of the most important aspects of your environment-some would argue it is the most important thing. It is hard to make this work. Cloud native people who don’t know storage have been shown to make fundamental errors.
This has and will improve over time.
Should I just go with my current storage vendor when I move to the cloud?
As we have mentioned there are great benefits to using the same storage in the cloud as on premises. So, you should start with your current vendor, however, look at it critically and find it if it’s good going to work.
Things to consider are:
· The quality of their API and Cloud Native experience.
· Is it an array sitting in a Data Centre like Equinix or is it actually a cloud native solution?
· Can my applications use it?
· Will it integrate with my automation solutions?
· Is it enterprise class, with Enterprise features and redundancy?
· Ensure it has had and will have a significant previous and future development investment and effort.
· How does the solution work into the future? Is it supportable and reliable into the future?
If you are interested in our other Cloud, Infrastructure and Security related Blogs please click here.