Amazon DynamoDB is a cloud-native, NoSQL, serverless database service.
$0
capacity unit per hour
Apache Solr
Score 8.7 out of 10
N/A
Apache Solr is an open-source enterprise search server.
N/A
Azure Cosmos DB
Score 8.9 out of 10
N/A
Microsoft Azure Cosmos DB is Microsoft's Big Data analysis platform. It is a NoSQL database service and is a replacement for the earlier DocumentDB NoSQL database.
N/A
Pricing
Amazon DynamoDB
Apache Solr
Azure Cosmos DB
Editions & Modules
Provisioned - Read Operation
$0.00013
capacity unit per hour
Provisioned - Write Operation
$0.00065
capacity unit per hour
Provisioned - Global Tables
$0.000975
per Read Capacity
On-Demand Streams
$0.02
per 100,000 read operations
Provisioned - Streams
$0.02
per 100,000 read operations
On-Demand Data Requests Outside AWS Regions
$0.09
per GB
Provisioned - Data Requests Outside AWS Regions
$0.09
per GB
On-Demand Snapshot
$0.10
per GB per month
Provisioned - Snapshot
$0.10
per GB per month
On-Demand Restoring a Backup
$0.15
per GB
Provisioned - Restoring a Backup
$0.15
per GB
On-Demand Point-in-Time Recovery
$0.20
per GB per month
Provisioned - Point-in-Time Recovery
$0.20
per GB per month
On-Demand Read Operation
$0.25
per million requests
On-Demand Data Stored
$0.25
per GB per month
Provisioned - Data Stored
$0.25
per GB per month
On-Demand - Write Operation
$1.25
per million requests
On-Demand Global Tables
$1.875
per million write operations replicated
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Amazon DynamoDB
Apache Solr
Azure Cosmos DB
Free Trial
No
No
No
Free/Freemium Version
No
No
No
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
—
—
—
More Pricing Information
Community Pulse
Amazon DynamoDB
Apache Solr
Azure Cosmos DB
Considered Multiple Products
Amazon DynamoDB
Verified User
Analyst
Chose Amazon DynamoDB
MongoDB is mostly document store while Amazon DynamoDB supports both key/value and document store making it more versatile. Azure Cosmos DB is multi-modal like Amazon DynamoDB and it makes more sense when you have data already in Azure Cloud. If you are mostly using AWS then …
MongoDB vs. Amazon DynamoDB:• MongoDB requires more human management than DynamoDB, which is a fully managed service.• DynamoDB's scalability is automatic, whereas MongoDB's horizontal scaling may require more work.• When compared to DynamoDB, MongoDB offers more extensive data …
Teams at our company briefly looking into other cloud services and we even have a feature using Azure, but Amazon DynamoDB ultimately was selected as it was easier for our company to just work with one suite of web services.
When you compare database systems it's easy to have an apples to apples comparison. However, when comparing two No-SQL systems it isn't as easy because they are built with different purposes in mind. DynamoDB has been easier to implement because it comes as a Service from …
When we were selecting for a server-less NoSQL solution, we had two option either to go with Cosmos or with Dynamo. Cosmos has a few great features, but in Cosmos, we need to provision at least 400 RU (request unit), which will make a single table cost at least 24$/month. While …
Because we often use Microsoft products for large corporate projects and other customer projects, and compatibility and integration are important to us, we used this platform, which in addition to very high security, has a very good response speed, also, building modern …
It’s great for server less and real-time applications. It would be great for gaming and mobile apps. However, if you need relational database and have fixed budget, do not use it. While budget can be managed, you need to be careful. Also this is not a tool for storing big data, there are other wide-column database types you could use for it ins the ad
Solr spins up nicely and works effectively for small enterprise environments providing helpful mechanisms for fuzzy searches and facetted searching. For larger enterprises with complex business solutions you'll find the need to hire an expert Solr engineer to optimize the powerful platform to your needs. Internationalization is tricky with Solr and many hosting solutions may limit you to a latin character set.
Like any NoSQL database, whether it's MongoDB or not, it's best suited for unstructured data. It's also well suited for storing raw data before processing it and performing any type of ETL on the data.
Easy to get started with Apache Solr. Whether it is tackling a setup issue or trying to learn some of the more advanced features, there are plenty of resources to help you out and get you going.
Performance. Apache Solr allows for a lot of custom tuning (if needed) and provides great out of the box performance for searching on large data sets.
Maintenance. After setting up Solr in a production environment there are plenty of tools provided to help you maintain and update your application. Apache Solr comes with great fault tolerance built in and has proven to be very reliable.
Scalable Instantly and automatically serverless database for any large scale business.
Quick access and response to data queries due to high speed in reading and writing data
Create a powerful digital experience for your customers with real-time offers and agile access to DB with super-fast analysis and comparison for best recommendation
These examples are due to the way we use Apache Solr. I think we have had the same problems with other NoSQL databases (but perhaps not the same solution). High data volumes of data and a lot of users were the causes.
We have lot of classifications and lot of data for each classification. This gave us several problems:
First: We couldn't keep all our data in Solr. Then we have all data in our MySQL DB and searching data in Solr. So we need to be sure to update and match the 2 databases in the same time.
Second: We needed several load balanced Solr databases.
Third: We needed to update all the databases and keep old data status.
If I don't speak about problems due to our lack of experience, the main Solr problem came from frequency of updates vs validation of several database. We encountered several locks due to this (our ops team didn't want to use real clustering, so all DB weren't updated). Problem messages were not always clear and we several days to understand the problems.
We had a thought time migrating from traditional DBs to Cosmos. Azure should provide a seamless platform for the migration of data from on-premises to cloud.
It's core to our business, we couldn't survive without it. We use it to drive everything from FTP logins to processing stories and delivering them to clients. It's reliable and easy to query from all of our pipeline services. Integration with things like AWS Lambda makes it easy to trigger events and run code whenever something changes in the database.
It's efficient, easy to scale, and works. We do have to do a bit of administration, but less now than when we started with this a couple of years ago. Microsoft continues to improve its self-management capability.
Functionally, DynamoDB has the features needed to use it. The interface is not as easy to use, which impacts its usability. Being familiar with AWS in general is helpful in understanding the interface, however it would be better if the interface more closely aligned with traditional tools for managing datastores.
It takes some time to deploy and currectly maintein it. And also, to learn how to use and integrate in the enviroment as well. Once you get theses steps done, it usability is very simple, and almost of the time it don't require no further attention on it. Even for maintence, if you deploy it on a cluster mode, it is very reliable and easy to take one host down.
It has very good compatibility and adaptability with other APIs and developers can safely create new apps because it is compatible with various tools and can be easily managed and run under the cloud, and in terms of security, it is one of the best of its kind, which is very powerful and excellent.
It works very well across all the regions and response time is also very quick due to AWS's internal data transfer. Plus if your product requires HIPPA or some other regulations needs to be followed, you can easily replicate the DB into multiple regions and they manage all by it's own.
Microsoft is the best when it comes to after-sales support. They have a well-structured training and knowledge base portal that anyone can use. They are usually quick to respond to cases and are on point for on-call support. I have no complaints from a support standpoint. Pretty happy with the support.
The only thing that can be compared to DynamoDB from the selected services can be Aurora. It is just that we use Aurora for High-Performance requirements as it can be 6 times faster than normal RDS DB. Both of them have served as well in the required scenario and we are very happy with most of the AWS services.
We tried to use both Elasticsearch and Swiftype with Drupal 8 but there are currently no good modules that integrate Drupal with those solutions. So Solr was really the only option for a Drupal 8 web site. It's not as easy to learn or use as Swiftype, but in the end I think it will be a little less expensive and offer more customization and flexibility.
Cosmos DB is unique in the industry as a true multi-model, cloud-native database engine that comes with solutions for geo-redundancy, multi-master writes, (globally!) low latency, and cost-effective hosting built in. I've yet to see anything else that even comes close to the power that Cosmos DB packs into its solution. The simplicity and tooling support are nice bonus features as well.
I have taken one point away due to its size limits. In case the application requires queries, it becomes really complicated to read and write data. When it comes to extremely large data sets such as the case in my company, a third-party logistics company, where huge amount of data is generated on a daily basis, even though the scalability is good, it becomes difficult to manage all the data due to limits.
Some developers see DynamoDB and try to fit problems to it, instead of picking the best solution for a given problem. This is true of any newer tool that people are trying to adopt.
It has allowed us to add more scalability to some of our systems.
As with any new technology there was a ramp up/rework phase as we learned best practices.