Amazon RDS vs PostgREST: What are the differences?
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; PostgREST: Automatic REST API for Any Postgres Database. PostgREST serves a fully RESTful API from any existing PostgreSQL database. It provides a cleaner, more standards-compliant, faster API than you are likely to write from scratch.
Amazon RDS and PostgREST are primarily classified as "SQL Database as a Service" and "Database" tools respectively.
PostgREST is an open source tool with 12.5K GitHub stars and 585 GitHub forks. Here's a link to PostgREST's open source repository on GitHub.
What is Amazon RDS?
What is PostgREST?
Want advice about which of these 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?
What are the cons of using PostgREST?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with PostgREST?
Sign up to get full access to all the tool integrationsMake informed product decisions
While we initially started off running our own Postgres cluster, we evaluated RDS and found it to be an excellent fit for us.
The failovers, manual scaling, replication, Postgres upgrades, and pretty much everything else has been super smooth and reliable.
We'll probably need something a little more complex in the future, but RDS performs admirably for now.
We are using RDS for managing PostgreSQL and legacy MSSQL databases.
Unfortunately while RDS works great for managing the PostgreSQL systems, MSSQL is very much a second class citizen and they don't offer very much capability. Infact, in order to upgrade instance storage for MSSQL we actually have to spin up a new cluster and migrate the data over.
Our PostgreSQL servers, where we keep the bulk of Wirkn data, are hosted on the fantastically easy and reliable AWS RDS platform.
We use Aurora for our OLTP database, it provides significant speed increases on top of MySQL without the need to manage it
RDS allows us to replicate the development databases locally as well as making it available to CircleCI.