Compose Review
Updated February 23, 2019

Compose Review

Joshua Dickson | TrustRadius Reviewer
Score 6 out of 10
Vetted Review
Verified User

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.
It very much depends on use case. For cases with small DBs, or for cases where ease of management is more important than cost, it's a great option. It's also a great starter for people who have not used Mongo and can make use of the GUI tools.

IBM Cloud Databases Feature Ratings

Automatic software patching
Not Rated
Database scalability
Not Rated
Automated backups
Database security provisions
Monitoring and metrics
Automatic host deployment

IBM Cloud Databases (formerly Compose) Support

Support is helpful enough, but we haven't always had questions answered in a satisfactory manner. At one time we realized that Compose had stopped taking database snapshots on its two-per-day schedule, and had in fact not taken one for many days. Support recognized the problem and it was fixed, but the lack of proactive checks and the inability to share exactly what happened has caused us to look elsewhere for production work loads.
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.