Fire-and-forget super stable deployments. Need cross-region replication/failover for true scale.
Updated January 31, 2018
Fire-and-forget super stable deployments. Need cross-region replication/failover for true scale.
Score 9 out of 10
Vetted Review
Verified User
Overall Satisfaction with IBM Cloud Databases (formerly Compose)
We use IBM Compose as a back-end storage for the content that drives our apps.
- Setup and forget - so far. I never really had to tinker with my installation or perform any maintenance.
- Support is pretty good, someone replied to my email request promptly and they were quite helpful in dealing with the emergency at hand (data loss due to application bug - not a Compose issue).
- Quite decent admin UI.
- The most substantial issue is lack of cross-region replication. My app only works well if the front-ends are sitting close to the Compose deployment (e.g. US-east). This will probably be a show-stopper down the road if not addressed.
- Backups are daily, which is usually not enough for catastrophic scenarios. I don't feel safe knowing I might lose a day's worth of data if something goes wrong. Ideally, there should always be a backup that is only a few hours long at the latest.
- The admin UI browser for browsing redis is a bit clunky, but that's a minor issue since reids-cli is enough.
- We are an early stage startup, so the numbers are not high. I can't put a price on never having to think about prod db, although the cost of that has always been high in self-managed services.