Need advice about which tool to choose?Ask the StackShare community!
Amazon RDS vs Amazon S3: What are the differences?
What is Amazon RDS? Set up, operate, and scale a relational database in the cloud. Amazon RDS gives you access to the capabilities of a familiar MySQL, Oracle or Microsoft SQL Server database engine. This means that the code, applications, and tools you already use today with your existing databases can be used with Amazon RDS. Amazon RDS automatically patches the database software and backs up your database, storing the backups for a user-defined retention period and enabling point-in-time recovery. You benefit from the flexibility of being able to scale the compute resources or storage capacity associated with your Database Instance (DB Instance) via a single API call.
What is Amazon S3? Store and retrieve any amount of data, at any time, from anywhere on the web. Amazon Simple Storage Service provides a fully redundant data storage infrastructure for storing and retrieving any amount of data, at any time, from anywhere on the web.
Amazon RDS belongs to "SQL Database as a Service" category of the tech stack, while Amazon S3 can be primarily classified under "Cloud Storage".
Some of the features offered by Amazon RDS are:
- Pre-configured Parameters
- Monitoring and Metrics
- Automatic Software Patching
On the other hand, Amazon S3 provides the following key features:
- Write, read, and delete objects containing from 1 byte to 5 terabytes of data each. The number of objects you can store is unlimited.
- Each object is stored in a bucket and retrieved via a unique, developer-assigned key.
- A bucket can be stored in one of several Regions. You can choose a Region to optimize for latency, minimize costs, or address regulatory requirements. Amazon S3 is currently available in the US Standard, US West (Oregon), US West (Northern California), EU (Ireland), Asia Pacific (Singapore), Asia Pacific (Tokyo), Asia Pacific (Sydney), South America (Sao Paulo), and GovCloud (US) Regions. The US Standard Region automatically routes requests to facilities in Northern Virginia or the Pacific Northwest using network maps.
"Reliable failovers", "Automated backups" and "Backed by amazon" are the key factors why developers consider Amazon RDS; whereas "Reliable", "Scalable" and "Cheap" are the primary reasons why Amazon S3 is favored.
According to the StackShare community, Amazon S3 has a broader approval, being mentioned in 3235 company stacks & 1616 developers stacks; compared to Amazon RDS, which is listed in 1437 company stacks and 526 developer stacks.
We offer our customer HIPAA compliant storage. After analyzing the market, we decided to go with Google Storage. The Nodejs API is ok, still not ES6 and can be very confusing to use. For each new customer, we created a different bucket so they can have individual data and not have to worry about data loss. After 1000+ customers we started seeing many problems with the creation of new buckets, with saving or retrieving a new file. Many false positive: the Promise returned ok, but in reality, it failed.
That's why we switched to S3 that just works.
Pros of Amazon RDS
- Reliable failovers164
- Automated backups155
- Backed by amazon130
- Db snapshots92
- Multi-availability87
- Control iops, fast restore to point of time30
- Security28
- Elastic24
- Automatic software patching20
- Push-button scaling20
- Replication4
- Reliable3
- Isolation2
Pros of Amazon S3
- Reliable592
- Scalable493
- Cheap458
- Simple & easy329
- Many sdks83
- Logical30
- Easy Setup13
- 1000+ POPs11
- REST API11
- Secure6
- Easy4
- Plug and play4
- Web UI for uploading files3
- Flexible2
- Faster on response2
- GDPR ready2
- Easy integration with CloudFront1
- Easy to use1
- Plug-gable1
Sign up to add or upvote prosMake informed product decisions
Cons of Amazon RDS
Cons of Amazon S3
- Permissions take some time to get right7
- Takes time/work to organize buckets & folders properly6
- Requires a credit card5
- Complex to set up3