Which one would you pick for production workloads and why? I am asking the question from the perspective of performance, cost, support for Postgres extensions - which makes Postgres so powerful. Would like to get perspectives from folks who are currently using/have used them in production.

One of my client wanted 5000IOPS for peak hours but at the cheaper costs. We tried RDS Provisioning for 5000IOPS but the costs had skyrocketed. After researching I found this medium link I got to know RDS+1TB storage gives better performance than Aurora at 3000IOPS and that too at cheaper costs. Although I'm still stuck at 3000IOPS, I am going to propose this to client. If there is any other option please let me know

Difference between RDS and Aurora, when hosting Java application with PostgreSQL database.

Here i have my estimated pricing for using RDS. I suppose this is a separate server for actually hosting the database (hence the price) I found this alternative Aurora, which seemed a little bit better in regards to pricing.

This is much cheaper and also allows for almost the same amount of data (and up 1 million requests).

Can anyone explain to me the major differences in regards to these two services?

Building a multi-tenant service. We're expecting ~100s of gb of embeddings per tenant.

I've never used Aurora so wanted to see peoples thoughts on price/performance of vector searches.

I'll be building a MVP using React (S3+CloudFront), Nodejs with GraphQL (Lambda) and a Postgres db.

I'm not sure whether the dB should go on RDS or Aurora? I don't really want to be managing it myself if I can help it as I'm no db expert. I understand how to build tables, normal form, triggers, indexes, relationships etc but the maintenance and provisioning of connections really worries me due to issues we had at my current startup last year. Basically all the connections were used and users were waiting for queries to resolve...

How does RDS/Aurora manage db connections? Is it a case of I can deploy it and not need to worry about the connection pooling/management etc?

Thanks all!

Hi all,

What are the main things to take into consideration when choosing between RDS and Aurora ? Is the price difference between having a completely managed service in Aurora versus managing your RDS yourself worth it ? It's been years since I've had to discuss relational databases so I need a bit of insight ... Thanks !

Here's the scenario:

• Primary Choice: I’m considering Amazon RDS PostgreSQL vs. Aurora Serverless PostgreSQL, with a preference for Aurora.

• Deployment: We need multi-AZ support (but not multi-region due to compliance issues). The plan is to use AZs A and B for active/live data, and AZ C for a disaster recovery (DR) setup ( different aws account ).

• DR Plan: The DR setup will be in a different AWS account.

My key question are : 1. Cross-Account DR: How can I effectively set up live data synchronization from the primary account to the DR setup in another AWS account? What are the recommended approaches for this scenario ( both rds and rds aurora) ?

2, Failover and Failback: What are the best practices for handling failover and failback between the primary and DR environments? How can we ensure minimal downtime and data consistency during these processes?

I'm working on a project for school and it involves using an ASP.Net stack. I've opted for ASP.Net Core so I can run it in Linux, which I'm familiar with. Part of the stack requires a database.

What is the difference between Aurora and RDS and which should I use to store a very basic SQL database for our project?

We’re currently running our game bac-kend REST API on Aurora MySQL (considering Server-less v2 as well).

Our main question is around resource consumption and performance:

• Which engine (Aurora MySQL vs Aurora PostgreSQL) tends to consume more RAM or CPU for similar workloads?

• Are their read/write throughput and latency roughly equal, or does one engine outperform the other for high-concurrency transactional workloads (e.g., a game API with lots of small queries)?

Questions:

1. If you’ve tested both Aurora MySQL and Aurora PostgreSQL, which one runs “leaner” in terms of resource usage?

2. Have you seen significant performance differences for REST API-type workloads?

3. Any unexpected issues (e.g., performance tuning or fail-over behavior) between the two engines?

We don’t rely heavily on MySQL-specific features, so we’re open to switching if PostgreSQL is more efficient or faster.

• load spikes at certain times but almost never active in weeks. is aurora better or is it going to be more expensive even on idle time

• if i pick rds but lets say i spike 100-500 users in 1-5 hours what would be the best rds instance then?

• additional question is it possible to increase iops in rds without provision iops?

Hi,

just here to through out some fairly general questions mostly regarding RDS Postgres / Aurora postgres.

We're a small company that uses Odoo - current setup is a t2.medium EC2 instance for the application / web server, and a t2.medium RDS Postgres instance (9.6.11) for the DB.

This works OK and has been running smoothly for approximately a year, but we find some tasks take longer than we'd like so looking to beef up the servers we currently have (plus we're currently on demand pricing and looking to move to 1 year RIs). Busy hours are only really during the day when staff are online, so I've tested the following :

1. Aurora Postgres Serverless : Sounded like a great idea - would scale up during busy hours, scale down during other hours. Did some testing and it was just dropping DB connections when scaling and overall really slow. Actually worked out not so cheap , as 2 x ACU is the minimum required. But because of the issues mentioned won't be using this anyway.

2. Aurora Postgres (R5.Large, Pg 10.7) - Best performance based on my tests - RI for a year would come to $0.21 / hour

3. RDS Postgres (R5.Large) - With PG 9.6 worse performance than Aurora RDS, with latest PG 11.1 it's on par with Aurora Postgres . RI for a year = $0.18 / hour

So my questions here are :

1. Is it worth paying the extra for Aurora Postgres - or is it better to wait for this product to be more mature (in a year's time assuming we decide to purchase RI for a year)

2. Any issues with simply upgrading to latest PG version? I just used the web interface to do this - there was an upgrade log but this seems to have disappeared. I assume when these versions are added to RDS Amazon has already done their own testing beforehand.

Apologies if these questions seem stupid, it's not something I'm very experienced with. So far what's setup "works" but a bit of extra performance is never a bad thing (if it doesn't break anything that is)

I have an app in production running on RDS postgresql db.r5.xlarge , the traffic is normal peaking during the day and almost sleeps during the night without any clear spikes.
I have a read replica that is used for reporting queries, this one is problematic, it has spikes whenever the users enter the google data studio reports, and even db.r5.2xlarge doesn't do the job fairly well.
I started thinking about evaluating Aurora Serverless v2 as an option, do you think using serverless will decrease the costs? what sorts of problems using serverless might cause or you have experience with?

Thanks everyone

Hey I’m a newly graduated student, who started a SaaS, which is now at $5-6k MRR.

When is the right time to move from DynamoDB to a more structured database like Aurora or RDS?

When I was building the MVP I was basically rushing and put everything into DynamoDB in an unstructured way (UserTable, things like tracking affiliate codes, etc).

It all functions perfectly and costs me under $2 per month for everything. The fact of this is really attractive to me - I have around 100-125 paid users and over the year have stored around 2000-3000 user records in dynamoDB. — it doesn’t make sense to just got to a $170 Aurora monthly cost.

However I’ve recently learned about SQL and have been looking at Aurora but I also think at the same time it is still a bit overkill to move my back end databases to SQL from NoSQL.

If I stay with DynamoDB, are there best practices I should implement to make my data structure more maintainable?

This is really a question on semantics and infrastructure - the dynamoDB does not have any performance and I really like the simplicity, but I feel it might be causing some more trouble?

The main things I care about is dynamic nature and where I can easily change things such as attribute names, as I add a lot of new features each month and we are still in the “searching” phase of the startup so lots of things to change - the plan, is to not really have a plan, and just follow customer feedback.

Hello, I’m new to AWS and cloud in general and I want to have a db for my app (‘till now I only used free tiers from neondb(aws-wrapper, I know)). I’m looking for a solution to have a postgresql database on aws, but when I try to create one RDS Postgresql it comes down to ~$50/month. Isn’t any way to make this cheaper? I heard about spinning it up on a EC2 instance, but that wouldn’t make it significantly slower? Any tips? thanks in advance!