While validated on a cluster with 160 nodes, architecturally, HCP for cloud scale is designed for unlimited scaling. From a practical standpoint, the scaling is achieved by clustering individual nodes, which do have their own finite limitations.
The following list of entities details the boundaries of this relationship:
| Entity | Minimum | Maximum by architecture | Notes |
|---|---|---|---|
| Buckets | None | Unlimited | A user can own up to 1000 buckets. |
| Users (external) | None | Unlimited | The local user has access to all functions including MAPI and S3 API methods. However, it's best to configure HCP for cloud scale with an identity provider (IdP) with users to enforce role-based access control. |
| Groups (external) | Unlimited | ||
| Roles | Unlimited | ||
| Objects | None | Unlimited¹ | The size limit for an object is 5 TB. |
| Storage components | 1 | Unlimited |
¹Note: At the core of HCP for cloud scale is a database. When objects are written, a metadata record describing the object is logged, containing its author, date of creation, retention settings, tags, prefixes, etc. The maximum number of objects managed by a node is proportional to size of this metadata record. The total number of objects can then be estimated as:
(1500 partitions x partition size) / (metadata record size)
For example, given a default partition size threshold of 1GB and an average metadata record size of 7500 bytes, this would equate to roughly 200 million objects per Metadata Gateway node. The metadata record size depends on multiple factors—7500 is used here only as an example. Consult your presales HCP for cloud scale team to review your individual business needs.