Overall Satisfaction with IBM Cloud Databases (formerly Compose)
We use Compose extensively to host our application's database layer which is implemented in MongoDB. MongoDB from Compose helps us in two ways: first of all, it removed significant overhead in having to think about monitoring and maintaining our database systems. Compose also has excellent GIU tools (though they can be a bit slow with large queries) for working with MongoDB.
- Database-Interaction GUI best we've worked with
- Service has been reliable
- Pricing Is low enough to not think about hosting our own DB layer
- Customer service has been lacking at times
- Technical issues: backups have not always happened on schedule, and customer data has been lost
- Pricing for follow-on GBs is high
- Removed man-hours from managing database layer
- Low-cost for small databases
- Have not had to think about investing in scaling DB layer
We evaluated several DBaaS providers, the thing that won out for Compose was its GUI which makes working with the database very easy.
IBM Cloud Databases Feature Ratings
IBM Cloud Databases (formerly Compose) Support
Pros | Cons |
---|---|
Good followup Knowledgeable team Problems get solved Kept well informed | Difficult to get immediate help |
No - We use IBM Cloud Databases (formerly Compose) more on starter and green-fields type projects, because it's very simple to spin up new database instances and the cost profile is acceptable. At larger database sizes, Compose/IBM's pricing has always been prohibitively expensive for hosting. With hosting being that expensive, we look elsewhere for actually deploying more production-oriented workloads in the cloud, and choose to pay for support with those providers.
Unlike with other vendors, I never felt as though I received exceptional support from Compose / IBM Cloud Databases.