Amazon Keyspaces vs. IBM Cloudant

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Amazon Keyspaces
Score 6.4 out of 10
N/A
Amazon Keyspaces (for Apache Cassandra) is a scalable, highly available, and managed Apache Cassandra–compatible database service. With Amazon Keyspaces, users can run Cassandra workloads on AWS using the same Cassandra application code and developer tools without having to provision, patch, or manage servers, or installing, maintaining, or operating software. Amazon Keyspaces is serverless, so users pay only for resources used and the service can automatically scale tables up and down in…N/A
IBM Cloudant
Score 7.4 out of 10
N/A
Cloudant is an open source non-relational, distributed database service that requires zero-configuration. It's based on the Apache-backed CouchDB project and the creator of the open source BigCouch project. Cloudant's service provides integrated data management, search, and analytics engine designed for web applications. Cloudant scales your database on the CouchDB framework and provides hosting, administrative tools, analytics and commercial support for CouchDB and BigCouch. Cloudant is often…
$1
per month per GB of storage above the included 20 GB
Pricing
Amazon KeyspacesIBM Cloudant
Editions & Modules
No answers on this topic
Standard
$1
per month per GB of storage above the included 20 GB
Standard
$75
per month 100 reads/second ; 50 writes/second ; 5 global queries/second
Lite
Free
20 reads/second ; 10 writes/second ; 5 global queries / second ; 1 GB of storage capacity
Standard
Included
per month 20 GB of storage
Offerings
Pricing Offerings
Amazon KeyspacesIBM Cloudant
Free Trial
NoYes
Free/Freemium Version
NoYes
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
Amazon KeyspacesIBM Cloudant
Considered Both Products
Amazon Keyspaces

No answer on this topic

IBM Cloudant
Chose IBM Cloudant
IBM cloudant documentation is very easy to understand and because of that the implementation is also very easy. We found some difficulties in case of aws documents implementation. Performance of the cloudant database is also high as compare to the other databases. Indexing and …
Chose IBM Cloudant
I like [the] ease of use of Cloudant. Redis and Fauna have time to live features so for caching and temp data that is what I use along with messaging queues.
Chose IBM Cloudant
MongoDB Atlas and Azure Cosmos DB are the closest competitors we found with Cloudant, especially in terms of fixed pricing and having a GUI for easy viewing and quick edits of data. Cloudant's pricing model flat out beats MongoDB Atlas' in terms of how easy it would be to …
Chose IBM Cloudant
IBM Cloudant is great for quick deployment and configs of a database service, especially when it comes to rapid prototyping. In a research capacity, we need to spin up web services and run experiments quickly. IBM Cloudant is a fuss-free database service [that] aids in this …
Chose IBM Cloudant
IBM Cloudant wins in all aspects, from cost, ease of deployment, features, global availability and much more.
Chose IBM Cloudant
The gap that we wanted to cover was to deploy a self-managed CouchDB environment, which would allow us the bidirectional replication of Databases through several physical locations of the same client. IBM Cloudant was the best choice after evaluating some other platforms with …
Chose IBM Cloudant
MS SQl is more specific to relational data. Overall, it is more mature with a more feature-filled interface, user access management, and tools to manage data.
Chose IBM Cloudant
None, since we are a dedicated IBM Gold Business Partner as well as a respected IBM development and design partner, we stick with IBM products.
Chose IBM Cloudant
The feature-set, including security, is very comparable. Overall, IBM's services added to the product are mature and stable, although product support and engineers could be a little better. Global availability is improving, and Disaster Recover Capabilities are great. Overall, …
Chose IBM Cloudant
In our case, it was a no-brainer since we were using IBM Cloud. In comparison to DB2 the ease of use and JSON support was the key.
Chose IBM Cloudant
As its documentation and help are always available, it's easier to manage than any other database mentioned.
Chose IBM Cloudant
As I mentioned Redis was the first option for this implementation, IBM Cloudant excels the data center sync.
Chose IBM Cloudant
I have mainly used Cloudant as I work with IBM Cloud in my role and therefore it was easiest (and cheapest) to set up for the small scale prototypes we are building. (Which do however sometimes lead to scaled implementation)
Chose IBM Cloudant
In our case it was a no-brainer since we were using IBM Cloud. In comparison to DB2 the ease of use and JSON support was the key.
Chose IBM Cloudant
Infinitely better in every part. Except handling SQL
Chose IBM Cloudant
IBM Cloudant DB is backed by CouchDB and that too hosted on IBM Cloud is the key. Concurrency and durability is the key here. In-memory capabilities are non-existent on the IBM Cloudant DB.
Chose IBM Cloudant
We chose Cloudant because it was fully managed and used in the marketplace, unlike MongoDB was at the time, and it supported JSON which SQL Server 2016 didn't.
Chose IBM Cloudant
It's easier to use than Dynamo, more open than Firebase, and has better documentation that CouchDB... it might not be fair to compare Modulus, Modulus obviously suffers from some scalability issues and might not be in the same class... but its a hosted DB service we had some …
Chose IBM Cloudant
All other NoSQL document-centric DB must be installed on premise on in the cloud as complicated clusters. The "as a service" formula and the open source origin were the same reasons for Cloudant choice, freeing us of all system and administration tasks!
Chose IBM Cloudant
Cloudant is a database as a service with a strong support team. The feature set is comparable to other solutions but not all are managed services, or have easy scalability, or can demonstrate production level reliability and performance.
Chose IBM Cloudant
We used to host CouchDB ourselves, but moved to BigCouch at first for scalability and then to Cloudant to reduce the maintenance overheads.
We use Elasticsearch alongside Cloudant these days, since _changes streams make it easy to feed data from Cloudant into Elasticsearch. …
Chose IBM Cloudant
Cloudant blows all of the other competitors out of the water. The robust UI, the scalability, the management console, these are all reasons why Cloudant is a superior product to any of these "competitors". Cloudant is head and shoulders above the rest. It was a pleasure to …
Chose IBM Cloudant
I've even worked with Cassandra, but I found Cloudant to be much simpler, easier, neat and efficient. Cassandra was not highly scalable but Cloudant was much efficient in it. Even the Monitoring and other scripts were pre-built which made it much time efficient for us.
Chose IBM Cloudant
I chose Cloudant because they had the best low end traffic prices while still providing room for pay as you need it scalability. I had an Amazon EC2 instance for a few years and I had to pay so much for it even though it hardly had any traffic. Being connected to IBM helped me …
Features
Amazon KeyspacesIBM Cloudant
NoSQL Databases
Comparison of NoSQL Databases features of Product A and Product B
Amazon Keyspaces
-
Ratings
IBM Cloudant
9.1
Ratings
2% above category average
Performance00 Ratings9.70 Ratings
Availability00 Ratings8.30 Ratings
Concurrency00 Ratings9.80 Ratings
Security00 Ratings8.20 Ratings
Scalability00 Ratings9.00 Ratings
Data model flexibility00 Ratings9.80 Ratings
Deployment model flexibility00 Ratings9.00 Ratings
Best Alternatives
Amazon KeyspacesIBM Cloudant
Small Businesses
IBM Cloudant
IBM Cloudant
Score 7.4 out of 10
Redis Software
Redis Software
Score 8.8 out of 10
Medium-sized Companies
IBM Cloudant
IBM Cloudant
Score 7.4 out of 10
Redis Software
Redis Software
Score 8.8 out of 10
Enterprises
IBM Cloudant
IBM Cloudant
Score 7.4 out of 10
Redis Software
Redis Software
Score 8.8 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Amazon KeyspacesIBM Cloudant
Likelihood to Recommend
-
(0 ratings)
7.0
(0 ratings)
Likelihood to Renew
-
(0 ratings)
7.3
(0 ratings)
Usability
-
(0 ratings)
7.7
(0 ratings)
Availability
-
(0 ratings)
8.2
(0 ratings)
Performance
-
(0 ratings)
8.2
(0 ratings)
Support Rating
-
(0 ratings)
8.6
(0 ratings)
Online Training
-
(0 ratings)
7.3
(0 ratings)
Implementation Rating
-
(0 ratings)
8.2
(0 ratings)
Configurability
-
(0 ratings)
8.5
(0 ratings)
Product Scalability
-
(0 ratings)
9.6
(0 ratings)
Vendor pre-sale
-
(0 ratings)
9.1
(0 ratings)
User Testimonials
Amazon KeyspacesIBM Cloudant
Likelihood to Recommend
No answers on this topic
IBM Cloudant is the best implementation of CouchDB, or any NoSQL database that you could use if you are looking for a database that can handle extremely rapid writes to a database without having to worry about transactional integrity. IBM Cloudant also abstracts out CouchDB's replication/multi-node requirements and ensures high availability on its own. It also allows map-reduce based indexing which will allow massive databases to be aggregated and queried very quickly. It should not be used in cases where you require structured data which is organized according to a schema, or if you want to maintain ACID database properties.
Read full review
Pros
No answers on this topic
  • We had a small data mart project that required the storage of some rather highly connected data that also had a relatively small footprint. This made IBM Cloudant an obvious choice because we could store the data in a data structure that met our project need al while using a platform that our web development team understood and was comfortable with.
  • We had a bunch of geospatial data that we needed for analysis. Having GeoJSON being natively supported by Cloudant made it an easy choice.
  • Cloudant was cloud-based and didn't require a DBA support it, this allowed the project to move ahead without pushback from the infrastructure team.
Read full review
Cons
No answers on this topic
  • To have a sort of LUW - Logical Unit Work when many documents are involved into a single update process. The changing of one document is related to its status information but it must be synchronized with all the other documents involved in the process.
Read full review
Likelihood to Renew
No answers on this topic
the flexibility of NoSQL allow us to modify and upgrade our apps very fast and in a convenient way. Having the solution hosted by IBM is also giving us the chance to focus on features and the improvement of our apps. It's one thing less to be worried about
Read full review
Usability
No answers on this topic
It's mostly just a straight forward API to a data store. I knock one off for the full text search thing, but I don't need it much anyways. Also, the dashboard UI they give is pretty nice to use. It provides syntax-highlighting for writing views and queries are easy to test. I wish other DBs had a UI like this.
Read full review
Reliability and Availability
No answers on this topic
it is a highly available solution in the IBM cloud portfolio and hence we have never had any issues with the data base being available - we also do continuous replication to be on the safer side just in case some thing goes awry. We also perform twice a year disaster recovery tests.
Read full review
Performance
No answers on this topic
very easy to get started and is very developer friendly given that it uses couchDB analytics. It is a cloud based solution and hence there is no hardware investment in a server and staging the server to get started and the associated delays/bureaucracy involved to get started. Good documentation is also available.
Read full review
Support Rating
No answers on this topic
Very happy by the commitment given by the team which has been really good over the last 7 years of usage.
Read full review
Online Training
No answers on this topic
online resources are good enough to understand but there is nothing like testing. In our case, we discovered some not documented behavior that we take in count now. Also, the experience in NodeJs is critical. Also, take in count that most of the "good practices" with cloudant are not in online courses but in blogs and pages from independent developers
Read full review
Implementation Rating
No answers on this topic
  • Test the architecture on CouchDB helped us to address initial design flaws.
  • The migration to Cloudant as such was very painless.
  • We have migrate our replication system to Cloudant Android Sync for mobile devices.
  • We have regular informal contact with the Cloudant leadership to discuss our use cases and implementation strategies.
Read full review
Alternatives Considered
No answers on this topic
MongoDB Atlas and Azure Cosmos DB are the closest competitors we found with Cloudant, especially in terms of fixed pricing and having a GUI for easy viewing and quick edits of data. Cloudant's pricing model flat out beats MongoDB Atlas' in terms of how easy it would be to predict costs. Cosmos DB is a much closer competitor, as it integrates well with Azure's stack similarly to Cloudant and the rest of the IBM Cloud stack; similar [throughout]-based pricing and replication options; and even the GUI and ease of query using SQL, which my team and I were more familiar with. Where Cloudant beats out Cosmos DB is again having a more simple pricing model (ops/sec vs Cosmos' "request units" voodoo) and being based on open-source software assuaging fears of vendor lock-in.
Read full review
Scalability
No answers on this topic
The service scales incredibly well. As you would expect from CloudDB and IBM combination. The only reason I wouldn't score it a 10 is the fact that document trees can get nested and nested very quickly if you are attempting to do very complex datasets. Which makes your code that much more complex to deal. Its very possible we could find a solution to this problem with better database planning to begin with, but one of the reasons we chose a service over a self-hosted solution was so we could set it up quick and forget about it. So we weren't going to dedicate a team to architecture optimization.
Read full review
Return on Investment
No answers on this topic
  • Saving in-terms of cost of procuring and maintaining hardware, which will be realized over the next 5 years.
  • Positive ROI in terms of the number of FTEs involved in maintaining our databases; our DBAs can now focus on other important and business critical applications.
  • Best ROI in terms of our organization's vision - they are no longer anxious / nervous to move to the cloud. We are already on the CLOUD.
Read full review
ScreenShots