This is cool to see! Looks like a compete against pg_mooncake which Databricks acquired. But how is this different from pg_duckdb?

That's a very big difference which makes this hard to believe. I would expect them to be within 20% of each other. I think I know the trick they used. The 48 core Aurora is the worst, it performs just as well as the 32 core one. If they picked and other hardware the numbers would be realistic. Also pg_vaccum is turned off, which is interesting.

Also the article has this note > This is a sponsored report. Google chose the competitors and the test. GigaOm chose the most compatible configurations and ran the testing workloads. Choosing compatible configurations is subject to judgment. We have attempted to describe our decisions fully in this report.

Seems like a perfect use case for a distributed database like YugabyteDB. Have you looked into it?

YugabyteDB a distributed postgres database.

Think of it as a true drop in replacement for postgres that runs on multiple nodes. It internally does replication, sharding and leader election. Just add more nodes and you get to increase both read and write scale.

I personally am working on a few things like online major upgrades, async replication for DR, enhanced backup/restore/pitr/clone capabilities, and more recently supporting DocumentDB extension which provides a true Mongodb API.

Being a startup I also get to talk with large customers, help with marketing content, and participate in database conferences.

This is a fully open source MongoDB alternative that offers high availability and horizontal scalability. It's a joint collaboration between YugabyteDB, FerretDB and the Microsoft DocumentDB teams.

Anyone who has had to do a Postgres major upgrade can relate to this