Compose started out only offering multi-tenant database deployments; the many databases we manage for our customers are deployed on clusters of large host systems. Using a powerful combination of container technology, software-defined networking, and advanced management processes, these database deployments operate as if they were running on isolated hardware with private networking. It's allowed Compose to deliver vast fleets of databases to thousands of users with the ability to scale on-demand as those customers grow.
Compose Enterprise uses exactly the same technology to deliver databases to customers but Enterprise allows those customers to have their own private cluster of hosts where they can deploy one, or one hundred or one thousand, databases. With Compose Enterprise, the cluster is entirely dedicated to the customer and located in the cloud datacenter of your choice. This makes compliance with various industry requirements possible and simple. It also means that you can consume all the resources your Enterprise cluster has to offer; scale databases vertically or, where supported, horizontally to fully exploit the compute and I/O power of the cluster.
Compose Enterprise also includes volume level encryption-at-rest, alongside Compose's existing options for encryption in flight for connections between the client applications and the clusters databases.
Compose Enterprise gives you all the flexibility, automated, autoscaling, manageability of Compose, but in a high compliance, dedicated and exclusive environment.
Currently, Compose Enterprise is a guided provisioning option. Contact Compose's Enterprise team through the form on the Compose Enterprise site and they will match your workload with an Enterprise cluster.
Once a Compose Enterprise cluster has been created and attached to your account you can use the Enterprise Console which enables users, with sufficient privileges, to browse the clusters attached to their account and access the Cluster View.
From the Cluster View, you can view the cluster in terms of deployments or capsules and drill down to the deployments.
Each Cluster also has Access Control options which can be set on a per-cluster basis. One particular permission that can be granted to a user is the permission to provision deployments on the cluster. When this permission is enabled for a user or team, the cluster will appear as a deployment option in the Compose Create Deployment view.
There are two routes to creating a database. One is to create it from the Compose Console's Deployment's view, using the Create Deployment button. This brings up the
Create Deployment view. Select a database type to create and then select the cluster from the
Create Database On selector - other options will include Compose's multi-tenant platform and any other clusters available to the account.
The other way to create a database on the cluster is to use the Enterprise Console, select the cluster in the console then use the Create Deployment button. This brings up the
Create Deployment view. Select a database type to create and the cluster is automatically selected in the
Create Database On selector.
In both cases, the database will be initially provisioned with the default sizes set out in Enterprise Deployment Shapes and Sizes.
If this article didn't solve things, summon a human and get some help!
Updated about a year ago