Amazon DynamoDB is a cloud-native, NoSQL, serverless database service.
$0
capacity unit per hour
MongoDB
Score 8.9 out of 10
N/A
MongoDB is an open source document-oriented database system. It is part of the NoSQL family of database systems. Instead of storing data in tables as is done in a "classical" relational database, MongoDB stores structured data as JSON-like documents with dynamic schemas (MongoDB calls the format BSON), making the integration of data in certain types of applications easier and faster.
$0.10
million reads
MySQL
Score 8.3 out of 10
N/A
MySQL is a popular open-source relational and embedded database, now owned by Oracle.
N/A
Pricing
Amazon DynamoDB
MongoDB
MySQL
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
Shared
$0
per month
Serverless
$0.10million reads
million reads
Dedicated
$57
per month
No answers on this topic
Offerings
Pricing Offerings
Amazon DynamoDB
MongoDB
MySQL
Free Trial
No
Yes
No
Free/Freemium Version
No
Yes
No
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
—
Fully managed, global cloud database on AWS, Azure, and GCP
—
More Pricing Information
Community Pulse
Amazon DynamoDB
MongoDB
MySQL
Considered Multiple Products
Amazon DynamoDB
Verified User
Director
Chose Amazon DynamoDB
More flexible and easier to get started with than RDS, but, in my opinion, much worse monitoring/cost and query/modeling complexity than MongoDB
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 …
DynamoDB provided an easy to use, schema-less, out of the box solution that can be used to spin up a full working implementation very easily. It doesn't require extra knowledge such as MongoDB query functions
Lesser flexibility but better performance, and more predictable development support are the key points where Amazon DynamoDB comes out on top, when compared to MongoDB.
We are always assembling our solutions on AWS and DynamoDB is a better fit for us because of its simplicity. DynamoDB has its ow sets of triggers that make this an integrated solution on AWS. Besides, we wanted to use a key-value solution for our simple edge DB, and we didn't …
DynamoDB's scalability is more automated and effortless, making it easier to handle rapid growth. Other tools require more manual configuration while DynamoDB simplifies database administration. Also, DynamoDB provides strong consistency while other tools like MongoDB and Apache…
MongoDB has some performance issues and can get corrupted from time to time and has needed to be rebuilt. We have not had that experience while using DynamoDB.
For our use case, we needed a noSQL that would work with AWS Lambdas of specific parts of the internal web applications. We optimized billing and uses , diversified databases for various parts; so it’s not very expensive.
Verified User
Engineer
Chose Amazon DynamoDB
i think both depends on usuability and app requirement
Other all SQL Databases are based on the traditional Schema Structure and Amazon DynamoDB is NoSQL so you don't need to generate the SQL Schemas. You can store the data whatever you want, whenever you want. You can store data in structured or non-structured any way you want. If …
Performance at high scales is better and the cost at high scales is less. If one has a ton of data generated and has to work their way through it, I think Amazon DynamoDB should the go-to database. There are no compromises when it comes to performance at a huge scale. With any …
The Amazon Web Services managed Amazon DynamoDB has excellent features which makes it stand out from all the others in market right now. The management ease it offers is far superior than its competitors and on top of that the on-demand pricing model is an advantage which works …
DynamoDB offers strong consistency, more fine-grained control over read and write capacities, and integrates seamlessly with other AWS services. DynamoDB is designed for horizontal scalability and high throughput, making it a better choice for applications with rapidly changing …
The automation is much more subtle and it performs way better for internet-scale applications. No matter the number of connections, the performance doesn't dip even a bit.
Mongo services are outside of our Vpc and are on a different network. Since most of our infra is on AWS, dynamo by AWS was a natural choice. Most of our engineers are familiar with AWS sdk and the console so that brought in a much smaller learning curve for our engineering team
It seamlessly integrates with Lambda, simplifying the deployment and management of serverless architecture. Both Lambda and DynamoDB are designed are highly scalable. Lambda functions can be triggered by various AWS services and events, such as changes in DynamoDB tables which …
MySQL is a great for querying related data, but it's unable to store structured data and has a fixed schema. Also SQL can be non-intuitive. DynamoDB, CouchDB and Redis all make querying the data quite difficult and lack important features. The problem CouchDB tries to solve is …
Verified User
Engineer
Chose MongoDB
I love MySQL, but again, it's a totally different use-case. For something with so much varied data in no particular form or structure that needs to be pooled together in a "data lake," a NoSQL solution like MongoDB is an easy choice. It makes it so much easier not having to …
MongoDB is the best NoSQL database out there. There are others, but Mongo has the largest community, is very easy to set up, and is extremely performant. Compared to a relational DB (like MySQL or Postgres) is like comparing apples and oranges. One isn't better or worse than …
In our early development days we weighed NoSQL databases like MongoDB with RDBMS solutions like MySQL. We were more familiar with MySQL from past experience but also were wary of painful data migrations that slowed down development iterations and increased the risk of outages …
The environment I work in is somewhat unique in that we use both MySQL and MongoDB. However, each is used for specific purposes that the other is not well suited for. MongoDB is not a relational database like MySQL, so it serves as the perfect place to dump key bits of data for …
We have [measured] the speed in reading/write operations in high load and finally select the winner = MongoDBWe have [not] too much data but in case there will be 10 [times] more we need Cassandra. Cassandra's storage engine provides constant-time writes no matter how big your …
The flexible structure underlying MongoDB's construction is not found in other competitors; the ability to easily change the structure without affecting other stored documents. It is very ideal for projects that you cannot predict that the structure will change this way. Of …
It's very fast and easiest to use. Many companies are using this nowadays. It's helped to complete many software products very quickly so the year income has increased compared with last years. Many programmers are now leaning this tool as back end developers so that we changed …
MongoDB is our go-to database solution for any project, and the more we work with it the more we love it. Some say that NoSQL is pointless... Our developers wholeheartedly disagree, because they love working with it. Though both NoSQL and SQL have their purposes, in most …
Your default choice should not be MongoDB in my opinion. Most user-facing systems are relational by nature so a well known and reliable SQL database would be easier to maintain and simpler to develop long term. If you highly value speed of development go with Firebase. If you …
It does not belong to certain cloud platforms. MongoDB is an independent program that works with any cloud platform including Amazon Web Services and the Google Cloud Platform. For companies who want to maintain a cloud agnostic structure, MongoDB is a great choice for NoSQL …
We tend to choose MongoDB when we're faced with a particular situation: we know that we need a NoSQL database in general, and want an open-source implementation that allows us to prevent against platform lock-in. Amazon's new DocumentDB product even allows us to choose to use …
MongoDB is the most complete database of NoSQL type. In my opinion, it has all the tools for a good development of a database. I have not had problems when using the application.
You can use MongoDB with the same use cases you use other relational databases, the difference is that with MongoDB you can do the same but easier and faster.
MongoDB was the most full-featured NoSQL database we evaluated - that offered atomic transactions at a document level, built-in HA & DR, open source, robust queries, and enterprise level support.
Other platforms had specific parts of what we were looking for - MongoDB had it all.
From the beginning, we thought we would have a large volume of data, so MongoDB was a natural choice. Next we started the project and found MongoDB is also developing new features that are more like SQL which was very nice for us. As data volume is growing with time, no need to …
Relational DB are not efficient when storing data structure like JSON. Different data structure can be stored without defining the schema. Most relational db might store data like Json as blobs. One single entry would store the entire JSON as blob and you can't query the …
The main argument of this decision was by popularity. At the time (2010), MySQL was the most popular open source database. Between 2010 and today, we evaluated different databases and PostgreSQL is a great competitor. SQL Server is good for windows applications but it's not …
Comparing MongoDB vs MySQL performance is difficult, since both management systems are extremely useful and the core differences underly their basic operations and initial approach. However, MongoDB vs MySQL is a hot argument that has been going on for a while now: mature …
MySQL is a standard across many industries and is familiar to most developers as a result. When comparing to something like MongoDB, most developers are more familiar and comfortable with MySQL. When comparing to something like Oracle, MySQL clearly wins in the expense …
If you are looking for a relational database (depending on your app), MySQL is a good place to start. MongoDB and Cassandra are NoSQL options (very powerful). I am more inclined towards PostgreSQL as it's more scalable over time. MySQL was bought by Oracle and the community …
It would be hard to make a case for the use of Microsoft Access for any but the most simple of internal business applications at this stage, not because it is a bad product but it falls well short of the power and scalability of MySQL and almost any other databse solution out …
I've been using MySQL for so long that it's my go-to RDBMS. I really like MySQL Workbench in conjunction with MySQL. I've experimented with Amazon DynamoDB in my personal time.
MongoDB is an application oriented solution with unstructured data. Percona Server for MySQL is a good solution when looking for performance peaks and the amount of data grows continuously over time. MySQL is the ideal solution when we have a data schema defined and we do not …
MongoDB has a dynamic schema for how data is stored in 'documents' whereas MySQL is more structured with tables, columns, and rows. MongoDB was built for high availability whereas MySQL can be a challenge when it comes to replication of the data and making everything redundant …
The primary reason we use MySQL instead of MongoDB is because we are in a large, legacy enterprise environment. MySQL works well and has all the necessary integrations with the various other software tools in our company's suite. Additionally, MySQL is a relational database …
Is not a drop-in replacement for any of the things listed above. MySQL has it's purpose and use-cases, same as those. It's a low-cost solution for high read/low write applications and works very well when used in the right circumstances. Support can be purchased from various …
MySQL was the first option due to the existing knowledge, and after using other databases, it also appeared to be the most predictable in terms of costs
Each of the products has its own merits and demerits. however since MySQL is a very good documentation and global community its easy to learn and apply in different stages for analytics work. compare to other data bases its simple for setup and work on it. MySQL is cost …
We let go SQL server as We don't want to use Windows server and bare the cost of Windows licensing.
Verified User
Engineer
Chose MySQL
Having used both PostgreSQL and Microsoft SQL Server, I can tell that MySQL performs admirably in a Linux setting. When compared to Microsoft SQL Server, the extra benefit is the minimal or nonexistent licence fee. We find that MySQL's programming interface is particularly …
A bit on the more complex side, but definitely one of the more popular solutions between our customers. As a stable alternative to the sometimes really pricy Oracle DB, it performed well for most of our not-database-heavy projects. It was a bit slower than no-SQL solutions on …
It is one of the tools that we had stopped using some time ago and in the last year we amplified its use thanks to its benefits and new functionalities.
Of course compare to no SQL databases it's slower but there is a completely different use case for them... In my opinion it is better than PostgreSQL, it's easier to configure and has the same performance, or approximately the same. Of course Oracle Database is a way bigger …
MySQL is a most generic implementation of a database of a sort that is coherent with major designs of web engines and frameworks. As it works in cross-platform environments and easy to deploy it seems to be a competitive choice and prospective solution for integration into web …
We have used Oracle as our clinical databases that stores patient records. In this project we didn't used Oracle but separately built MySQL based data infrastructure as this is an independent scientific research project. Oracle is great overall, with most of functionalities …
MySQL has it's pros / cons. The best things about MySQL are that it is open-source/free and has such a vast community of users. If you want a free database MySQL is the quickest to use, but if you're trying to build a strong foundation for your company, I prefer Postgres. If …
I have the most experience with MySQL so I feel most comfortable using and implementing it. I like it over MSSQL just because I'm not a fan of some of the features MSSQL has. My Mongo and Hadoop experience was for a very specific purpose and they better matches the project …
MySQL provides a feature to easily move to another technology. As we know, most of the users like to use MySQL in the backend because it reduces the overall business cost. No need to pay additional charges. Regularly updated.
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
If asked by a colleague I would highly recommend MongoDB. MongoDB provides incredible flexibility and is quick and easy to set up. It also provides extensive documentation which is very useful for someone new to the tool. Though I've used it for years and still referenced the docs often. From my experience and the use cases I've worked on, I'd suggest using it anywhere that needs a fast, efficient storage space for non-relational data. If a relational database is needed then another tool would be more apt.
MySQL is best suited for applications on platform like high-traffic content-driven websites, small-scale web apps, data warehouses which regards light analytical workloads. However its less suited for areas like enterprise data warehouse, OLAP cubes, large-scale reporting, applications requiring flexible or semi-structured data like event logging systems, product configurations, dynamic forms.
Being a JSON language optimizes the response time of a query, you can directly build a query logic from the same service
You can install a local, database-based environment rather than the non-relational real-time bases such a firebase does not allow, the local environment is paramount since you can work without relying on the internet.
Forming collections in Mango is relatively simple, you do not need to know of query to work with it, since it has a simple graphic environment that allows you to manage databases for those who are not experts in console management.
An aggregate pipeline can be a bit overwhelming as a newcomer.
There's still no real concept of joins with references/foreign keys, although the aggregate framework has a feature that is close.
Database management/dev ops can still be time-consuming if rolling your own deployments. (Thankfully there are plenty of providers like Compose or even MongoDB's own Atlas that helps take care of the nitty-gritty.
Learning curve: is big. Newbies will face problems in understanding the platform initially. However, with plenty of online resources, one can easily find solutions to problems and learn on the go.
Backup and restore: MySQL is not very seamless. Although the data is never ruptured or missed, the process involved is not very much user-friendly. Maybe, a new command-line interface for only the backup-restore functionality shall be set up again to make this very important step much easier to perform and maintain.
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.
I am looking forward to increasing our SaaS subscriptions such that I get to experience global replica sets, working in reads from secondaries, and what not. Can't wait to be able to exploit some of the power that the "Big Boys" use MongoDB for.
For teaching Databases and SQL, I would definitely continue to use MySQL. It provides a good, solid foundation to learn about databases. Also to learn about the SQL language and how it works with the creation, insertion, deletion, updating, and manipulation of data, tables, and databases. This SQL language is a foundation and can be used to learn many other database related concepts.
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.
NoSQL database systems such as MongoDB lack graphical interfaces by default and therefore to improve usability it is necessary to install third-party applications to see more visually the schemas and stored documents. In addition, these tools also allow us to visualize the commands to be executed for each operation.
I give MySQL a 9/10 overall because I really like it but I feel like there are a lot of tech people who would hate it if I gave it a 10/10. I've never had any problems with it or reached any of its limitations but I know a few people who have so I can't give it a 10/10 based on those complaints.
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.
Finding support from local companies can be difficult. There were times when the local company could not find a solution and we reached a solution by getting support globally. If a good local company is found, it will overcome all your problems with its global support.
We have never contacted MySQL enterprise support team for any issues related to MySQL. This is because we have been using primarily the MySQL Server community edition and have been using the MySQL support forums for any questions and practical guidance that we needed before and during the technical implementations. Overall, the support community has been very helpful and allowed us to make the most out of the community edition.
While the setup and configuration of MongoDB is pretty straight forward, having a vendor that performs automatic backups and scales the cluster automatically is very convenient. If you do not have a system administrator or DBA familiar with MongoDB on hand, it's a very good idea to use a 3rd party vendor that specializes in MongoDB hosting. The value is very well worth it over hosting it yourself since the cost is often reasonable among providers.
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 have [measured] the speed in reading/write operations in high load and finally select the winner = MongoDBWe have [not] too much data but in case there will be 10 [times] more we need Cassandra. Cassandra's storage engine provides constant-time writes no matter how big your data set grows. For analytics, MongoDB provides a custom map/reduce implementation; Cassandra provides native Hadoop support.
MongoDB has a dynamic schema for how data is stored in 'documents' whereas MySQL is more structured with tables, columns, and rows. MongoDB was built for high availability whereas MySQL can be a challenge when it comes to replication of the data and making everything redundant in the event of a DR or outage.
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.
Open Source w/ reasonable support costs have a direct, positive impact on the ROI (we moved away from large, monolithic, locked in licensing models)
You do have to balance the necessary level of HA & DR with the number of servers required to scale up and scale out. Servers cost money - so DR & HR doesn't come for free (even though it's built into the architecture of MongoDB