Amazon DynamoDB vs IBM Cloud Databases

• It's very easy to get started, creating a table with a partition/sort key and you're on your way.
• You can scale up and down your read/write IO as needed.
• You can store structured and unstructured data.
• It works great with Web Development as it's JSON based.

Read full review

• The ease of setup was effortless. For anyone with development experience, a few simple questions such as name and login data will get you set up.
• The web application to manage cluster settings, billing settings and even introspect the data was simple and most importantly worked all the time. This can not always be said for web interfaces of other products.

Read full review

• Complex searching (no support for case-insensitive or full-text search).
• Only supports up to two-key indexes.
• Requires choosing the indexes up-front when doing searches.
• Does not have an SQL compatible query front-end.
• No join-table support (requires putting all data into one table).

Read full review

• Better cost reports, before just increasing to another tier, thus increasing the price. This is critical for early stage startups, where budget is tight.
• Add more data center options. As a comparison, a similar service, Aiven.io has dozen more options than Compose (basically all big cloud providers). We moved from AWS to Digital Ocean, which made us stop using Compose, since Compose forces us to be either on IBM or AWS.

Read full review

• Since the Amazon manages the instance, the amount of time a developer needs to spend configuring the database is less. For comparison, if we were to manage the same instance manually, we need to set up EC2 instance, install the DB, setup backup scripts, track backup failures, which is a great overhead for the dev. Using DynamoDB this overhead is reduced and hence having a great ROI.
• Great documentation and easy setup makes an easy learning curve to transition to DynamoDB. Only caveat is as with any database, the data structure should be thoroughly analyzed for types of querying because there are limitations with the DynamoDB API.
• Ties very well with rest of the Amazon eco system. Having rest of the applications in Amazon allows managing the application security a breeze.

Read full review

• At the beginning, VERY positive. I didn't know Mongo very well when I started this project, and I needed to get a POC up very quickly. Compose let me basically ignore all database management.
• Compose basically kept up its end of the deal... until a few months ago when we started pushing the envelope. Latency problems and, despite digging deep into documentation, etc, unable to really understand if/how much our Compose instance was to blame. In the end it wasn't, but trial and error was about all I was able to do with Compose.
• Globally, Compose had a very good ROI, since it allowed me to offload DB admin at a moment when having to do it would have seriously slowed our progress.

Read full review