The Compose Platform will be End of Life on March 1st, 2023
After March 1st, 2023, all instances running on Compose will be permanently disabled and deprovisioned. Please be sure to migrate your databases prior to this date to avoid business disruption.
But There Is Great News!
We’ve rolled our long experience with DBaaS platforms into our next-generation family of services called IBM Cloud Databases. IBM Cloud Databases have been Generally Available since 2019 and offers battle-tested, production-ready versions of MongoDB, PostgreSQL, Redis, Elasticsearch, MySQL, RabbitMQ, DataStax, EDB, and etcd.
Why IBM Cloud Databases?
IBM Cloud Databases offers many advantages, including cost savings, independently scaling RAM and disk, optional dedicated vCPUs. It is everything you love, but more.
|IBM Cloud Databases||IBM Cloud Databases||Compose|
|Compliance||HIPAA-ready, PCI-DSS, SOC 1 Type 2, SOC 2 Type 2, ISO 27001, ISO 27017, ISO 27018, ISO 27701, and GDPR.||GDPR|
|Integration with IBM Cloud||Identity and Access Management, Logging, Monitoring, Activity Tracker, Virtual Private Endpoints, and Bring Your Own Encryption Key||N/A|
|Scaling||Independent scaling of Disk, RAM, and vCPUs with serverless auto-scaling||Fixed Disk/RAM ratio|
|Backups||30 day retention on Cross-Regional IBM Cloud Object Storage where available||3 month single-region retention|
|Billing||Pay-as-you-go, hourly billing||Pay-as-you-go, hourly billing|
What Is Eligible To Migrate To IBM Cloud Databases?
We have migration strategies to IBM Cloud Databases for everything you run on Compose. While some of this documentation will have unfamiliar screenshots and references, the underlying migration concepts are still applicable.
Provisioning new instances on IBM Cloud Databases
When you visit the page to provision a new database instance on IBM Cloud, you will notice that dedicated cores are included automatically. Allocating dedicated cores to your deployment introduces hypervisor-level isolation to your database instance, using isolated virtual machines to ensure your data processing remains separated from other customers. If you don't require this feature, on the provisioning page under "Resource Allocation", select the "Custom" tab and set "Dedicated Cores" to 0.
For detailed information about our recommended RAM and Disk allocation, check out this article.
|Compose||IBM Cloud Databases||Migration Documentation|
|Elasticsearch||Databases for Elasticsearch||>>|
|etcd||Databases for etcd||Submit a ticket|
|MongoDB||Databases for MongoDB||>>|
|MySQL||Databases for MySQL||>>|
|PostgreSQL||Databases for PostgreSQL||>>|
|RabbitMQ||Messages for RabbitMQ||>>|
|Redis||Databases for Redis||>>|
|RethinkDB||Databases for MongoDB||>>|
|Scylla||Databases for Datastax||Submit a ticket|
RethinkDB and ScyllaDB
If you run either of these databases on Compose, we recommend migrating your workloads to MongoDB and Datastax, respectively.
Here are some quick links to information about IBM Cloud Databases:
- Monitoring - also see IBM Cloud® Monitoring service
- Logging - also see IBM Cloud® Log Analysis
- Compliance (security posture, encryption keys)
We are excited to have you join us on IBM Cloud Databases. Behind the scenes, the loyal IBM Compose engineering, support and product management team is here working for you. If you have questions about these migration paths, please open a support ticket at app.compose.com or send an email to [email protected] We'll be happy to help you.
Updated about 1 year ago