The key features of HyperStore 7 include:
- Multi-cloud access via a common API: Manage all cloud and on-premises storage assets, including Amazon AWS, Google GCP, and Microsoft Azure via a common API
- Merge Files and Objects: Combine file and object management to a single namespace, accessed via SMB (CIFS) / NFS protocols and the S3 API
- Scale-out architecture: Multiple distributed controllers can manage a single namespace across on-premises and cloud environments for performance scaling, increased availability and simplified data access
- Converged Data Access: Permits data stored as files to be retrieved as objects, or vice versa, providing full data interchangeability
I’ll run through these in a little more detail below.
Multi-cloud via Common API
The cool thing about HyperStore 7 is that it’s delivered as a single software image. This means you can manage your HyperStore environment from a common interface, regardless of whether it’s an appliance located on-premises, or a virtual image running in Azure, GCP or AWS.
[image courtesy of Cloudian]
The common image also means you can start out small and build up. You can deploy on-premises first, then work up to a hybrid cloud deployment, and then, if you’re so inclined, you can deploy HyperStore 7 natively in the cloud. The best thing about this feature is that you don’t need to undo the work you’ve already done on-premises, you can just build on it.
Files and Objects, Together
Once of the most exciting features, in my opinion, is “Converged Data Access”. The recent introduction of HyperFile ramps up the file and object play considerably, with a single namespace across multiple environments, and files and objects being stored in that namespace. You can access data in object or file format interchangeably as well.
[image courtesy of Cloudian]
Note also that data stored in its native cloud format. So if you’re using Azure, for example, your data is stored in blob format, and is thus accessible to other applications that can leverage that format.
The basic edition of HyperFile is included with HyperStore at no charge. The hardware appliance remains the primary model for on-premises deployments, with Cloudian noting that a lot of customers are still most comfortable buying hardware from a vendor for their storage deployments.
With the introduction of HyperFile, Cloudian made some leaps ahead in terms of breadth of offering. In my opinion, the ability to deploy HyperStore 7 on your favourite public cloud platform, and have it running a shared data pool with your on-premises HyperStore storage, is simply icing on the cake. A lot of people are talking about how they are all in with multi-cloud solutions, but it seems that Cloudian have come up with a fairly simple solution to the problem. You’ll need to do a little work to make sure your networking is set up in the way you need it to meet your requirements, but you’d need to do that if you were looking to do file or object in public cloud in any case. There are a bunch of use cases for this type of technology, and it’s nice to see that it’s not a bunch of different products glued together and called a solution.
It’s no secret that I think Cloudian have been doing some pretty cool stuff in the object space for a while now. The addition of HyperFile capability last year, and this multi-cloud capability in HyperStore 7, gets me all kinds of excited to see what they’ve got in store for the future. If you’re after a scalable object (and file) solution works well on-premises and off-premises, you’d do well to check out what Cloudian has to offer.