What is Amazon RDS for PostgreSQL and what are its top alternatives?
Top Alternatives to Amazon RDS for PostgreSQL
Heroku Postgres provides a SQL database-as-a-service that lets you focus on building your application instead of messing around with database management. ...
Google Cloud SQL for PostgreSQL
Cloud SQL offers high performance, scalability, and convenience. Hosted on Google Cloud Platform, Cloud SQL provides a database infrastructure for applications running anywhere. ...
Azure Database for PostgreSQL
Azure Database for PostgreSQL provides a managed database service for app development and deployment that allows you to stand up a PostgreSQL database in minutes and scale on the fly – on the cloud you trust most. ...
ElephantSQL hosts PostgreSQL on Amazon EC2 in multiple regions and availability zones. The servers are continuously transferring the Write-Ahead-Log (the transaction log) to S3 for maximum reliability. ...
We manage an optimized Postgres image. You focus on your core app, not on becoming a database administrator. ...
It is a fully-managed database as a service. It takes care of backups, high availability, monitoring. Additionally, it is multi-cloud supporting AWS and Azure and comes with PL/Python3u and PL/R for more powerful work. ...
PaaS DB PostgreSQL
A simple product to get an operational database without any pain about server management, security settings and upgrading. We provide resources to instanciate your database (PostgreSQL 9.4). Our goal is to propose this service with an hourly billing. ...
Amazon RDS for PostgreSQL alternatives & related posts
- Easy to setup29
- Follower databases3
- Dataclips for sharing queries3
- Extremely reliable3
- Super expensive2
related Heroku Postgres posts
PostgreSQL Heroku Heroku Postgres Node.js Knex.js
Last week we rolled out a simple patch that decimated the response time of a Postgres query crucial to Checkly. It quite literally went from an average of ~100ms with peaks to 1 second to a steady 1ms to 10ms.
However, that patch was just the last step of a longer journey:
I looked at what API endpoints were using which queries and how their response time grew over time. Specifically the customer facing API endpoints that are directly responsible for rendering the first dashboard page of the product are crucial.
I looked at the Heroku metrics such as those reported by
heroku pg:outlierand cross references that with "slowest response time" statistics.
I reproduced the production situation as best as possible on a local development machine and test my hypothesis that an composite index on a
uuidfield and a
timestampzfield would reduce response times.
This method secured the victory and we rolled out a new index last week. Response times plummeted. Read the full story in the blog post.
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...
related Google Cloud SQL for PostgreSQL posts
related Azure Database for PostgreSQL posts
- They suck7
- Geospatial support1
- Easy setup1
- Easy backup1
related ElephantSQL posts
- Superb customer service, and ready to go out of the box1
- Fastest, most effective support desk I've ever seen1