Amazon DynamoDB vs Amazon RDS for PostgreSQL: What are the differences?
Developers describe Amazon DynamoDB as "Fully managed NoSQL database service". All data items are stored on Solid State Drives (SSDs), and are replicated across 3 Availability Zones for high availability and durability. With DynamoDB, you can offload the administrative burden of operating and scaling a highly available distributed database cluster, while paying a low price for only what you use. On the other hand, Amazon RDS for PostgreSQL is detailed as "* Set up, operate, and scale PostgreSQL deployments in the cloud*". Amazon RDS manages complex and time-consuming administrative tasks such as PostgreSQL software installation and upgrades, storage management, replication for high availability and back-ups for disaster recovery. With just a few clicks in the AWS Management Console, you can deploy a PostgreSQL database with automatically configured database parameters for optimal performance. Amazon RDS for PostgreSQL database instances can be provisioned with either standard storage or Provisioned IOPS storage. Once provisioned, you can scale from 10GB to 3TB of storage and from 1,000 IOPS to 30,000 IOPS.
Amazon DynamoDB can be classified as a tool in the "NoSQL Database as a Service" category, while Amazon RDS for PostgreSQL is grouped under "PostgreSQL as a Service".
Some of the features offered by Amazon DynamoDB are:
- Automated Storage Scaling – There is no limit to the amount of data you can store in a DynamoDB table, and the service automatically allocates more storage, as you store more data using the DynamoDB write APIs.
- Provisioned Throughput – When creating a table, simply specify how much request capacity you require. DynamoDB allocates dedicated resources to your table to meet your performance requirements, and automatically partitions data over a sufficient number of servers to meet your request capacity. If your throughput requirements change, simply update your table's request capacity using the AWS Management Console or the Amazon DynamoDB APIs. You are still able to achieve your prior throughput levels while scaling is underway.
- Fully Distributed, Shared Nothing Architecture – Amazon DynamoDB scales horizontally and can seamlessly scale a single table over hundreds of servers.
On the other hand, Amazon RDS for PostgreSQL provides the following key features:
- Monitoring and Metrics –Amazon RDS provides Amazon CloudWatch metrics for you DB Instance deployments at no additional charge.
- DB Event Notifications –Amazon RDS provides Amazon SNS notifications via email or SMS for your DB Instance deployments.
- Automatic Software Patching – Amazon RDS will make sure that the PostgreSQL software powering your deployment stays up-to-date with the latest patches.
"Predictable performance and cost" is the top reason why over 53 developers like Amazon DynamoDB, while over 22 developers mention "Easy setup, backup, monitoring" as the leading cause for choosing Amazon RDS for PostgreSQL.
Lyft, New Relic, and Sellsuki are some of the popular companies that use Amazon DynamoDB, whereas Amazon RDS for PostgreSQL is used by Instacart, Tictail, and DSTLD. Amazon DynamoDB has a broader approval, being mentioned in 429 company stacks & 173 developers stacks; compared to Amazon RDS for PostgreSQL, which is listed in 164 company stacks and 27 developer stacks.
What is Amazon DynamoDB?
What is Amazon RDS for PostgreSQL?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Amazon RDS for PostgreSQL?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
We use Amazon RDS for PostgreSQL because RDS and Amazon DynamoDB are two distinct database systems. DynamoDB is NoSQL DB whereas RDS is a relational database on the cloud. The pricing will mainly differ in the type of application you are using and your requirements. For some applications, both DynamoDB and RDS, can serve well, for some it might not. I do not think DynamoDB is cheaper. Right now we are helping Companies in Silicon Valley and in Southern California go SERVERLESS - drastically lowering costs if you are interested in hearing how we go about it.
Amazon RDS for PostgreSQL or Amazon DynamoDB? If you need to follow RDBS concepts choose Amazon RDS (PostgreSQL). This choice will guarantee a stable relational database with a great support for years from PostgreSQL Global Development Group. But, you need a great scalable NoSQL database. You can use Amazon DynamoDB. The most important thing about this is that you can use RESTful HTTP API to access data.
I use Amazon DynamoDB because it integrates seamlessly with other AWS SaaS solutions and if cost is the primary concern early on, then this will be a better choice when compared to AWS RDS or any other solution that requires the creation of a HA cluster of IaaS components that will cost money just for being there, the costs not being influenced primarily by usage.
I could spin up an Amazon EC2 instance and install PostgreSQL myself, review latest configuration best practices, sort Amazon EBS storage for data, set up a snapshot process etc.
Alternatively I could use Amazon RDS, Amazon RDS for PostgreSQL or Heroku Postgres and have most of that work handled for me, by a team of world experts...
For most of the stuff we use MySQL. We just use Amazon RDS. But for some stuff we use Amazon DynamoDB. We love DynamoDB. It's amazing. We store usage data in there, for example. I think we have close to seven or eight hundred million records in there and it's scaled like you don't even notice it. You never notice any performance degradation whatsoever. It's insane, and the last time I checked we were paying $150 bucks for that.
zerotoherojs.com ’s userbase, and course details are stored in DynamoDB tables.
The good thing about AWS DynamoDB is: For the amount of traffic that I have, it is free. It is highly-scalable, it is managed by Amazon, and it is pretty fast.
It is, again, one less thing to worry about (when compared to managing your own MongoDB elsewhere).
We store customer metadata in DynamoDB. We decided to use Amazon DynamoDB because it was a fully managed, highly available solution. We didn't want to operate our own SQL server and we wanted to ensure that we built CloudRepo on high availability components so that we could pass that benefit back to our customers.
몇몇 로그는 현재 AWS DynamoDB 에 기록되고 있습니다. 개선을 통해 mongodb 로 옮길 계획을 하고 있습니다. 아주 간단한 데이터를 쌓는 용도로는 나쁘지 않습니다. 다만, 쿼리가 아주 제한적입니다. 사용하기 전에 반드시 DynamoDB 의 스펙을 확인할 필요가 있습니다.
To store device health records as it allows super fast writes and range queries.
Using PostGIS to serve GeoJSON data for the Leaflet front-end.