Table of Contents
- Object Storage Primer
- Report Methodology
- Decision Criteria Analysis
- Evaluation Metrics
- Key Criteria: Impact Analysis
- Analyst’s Take
- About Enrico Signoretti
The object storage market is more active than ever. It is very popular with developers, and just about every IT organization is adopting it in one way or another. Not only is it common in the public cloud, especially with large organizations, but hybrid infrastructures and large on-premises installations are growing as well.
There are several reasons for the increasing demand for this type of storage. Today, a growing number of applications need to store data safely and access it from everywhere, from multiple applications and devices concurrently. High-performance computing applications—like Big Data analytics and AI—are also big consumers of object storage. This means that the key characteristics of enterprise object stores have changed, with much more attention to performance, ease of deployment, security, federation capabilities, and multi-tenancy than in the past. In fact, users are taking advantage of their recent experience with the public cloud to build on-premises infrastructures that can support as many workloads as possible while keeping costs under control.
Most of the success of object storage comes from its use in the public cloud. Amazon’s AWS S3 API is the de facto standard, and all software and hardware vendors adopted this interface for their solutions. Other APIs, like Microsoft Azure Blob, are now available on some products but they are not as common.
In any case, API standardization and the resulting enhanced compatibility enabled users to build hybrid and multi-cloud infrastructures more confidently and at a reasonable cost. Even better, some vendors have proposed multi-cloud data controllers aimed at virtualizing access to multiple object stores on the back end for better control over data placement, governance, and cost. Standardization on the S3 API simplified the access layer and helped accelerate product differentiation in the back end. The S3 API has now been adopted by multiple storage systems, including primary scale-up storage systems, and products are very differentiated in terms of scalability, performance, and features (see Figure 1).
Figure 1. Various Types of Object Stores Compared
Modern scale-out object stores are becoming increasingly specialized. While some products can be considered general-purpose storage aimed at serving as many use cases as possible, these solutions don’t excel in any specific vertical. Others are becoming more focused on specific applications delivering the best return on investment (ROI), with features and add-ons designed for those workloads. However, they often lack some enterprise features. Whether to choose a general-purpose approach over a more focused one really depends on business needs, including the amount of data that has to be stored and the number of applications the object store has to serve.
As with any other IT infrastructure component, security is a key area that must be carefully evaluated. With more and more applications using object stores to save their data persistently and permanently, security is crucial. For example, object storage is often used both as a primary backup target and for disaster recovery purposes. S3 offers several security features on the front end but in order to provide strong end-to-end protection against data loss and malicious attacks, object stores must include additional security features and characteristics.
Object storage usually has a very long lifespan when compared to other storage systems in the infrastructure, and the market landscape is very complex. Before deciding which solution is better, users should consider whether the object store will be relatively small and serve one or a few applications, or whether it will become a fundamental infrastructure service that will store data for a large number of applications, services, and other infrastructure components. This decision will have a strong impact on both data management and your deployment model.
How to Read this Report
This GigaOm report is one of a series of documents that helps IT organizations assess competing solutions in the context of well-defined features and criteria. For a fuller understanding consider reviewing the following reports:
Key Criteria report: A detailed market sector analysis that assesses the impact that key product features and criteria have on top-line solution characteristics—such as scalability, performance, and TCO—that drive purchase decisions.
GigaOm Radar report: A forward-looking analysis that plots the relative value and progression of vendor solutions along multiple axes based on strategy and execution. The Radar report includes a breakdown of each vendor’s offering in the sector.
Vendor Profile: An in-depth vendor analysis that builds on the framework developed in the Key Criteria and Radar reports to assess a company’s engagement within a technology sector. This analysis includes forward-looking guidance around both strategy and product.