Scaling Out To 226K TPS | Scaling Postgres 422
About this episode
This episode discusses scaling application writes to achieve 226K TPS and best practices for disaster recovery in Postgres.
In this episode of Scaling Postgres, we discuss scaling out application writes to achieve 226K TPS, try to avoid delete, disaster recovery is a process and avoid NULL in your NOT IN. To get the show notes as well as get notified of new episodes, visit: https://www.scalingpostgres.com/episodes/422-scaling-out-to-226k-tps/ Want to learn more about Postgres performance? Join my FREE training called Postgres Performance Demystified here: https://www.scalingpostgres.com/courses/postgres-performance-demystified/
More episodes of Scaling Postgres
- pgrust Faster Than Postgres? | Scaling Postgres 426
- Novel Partition Exclusion | Scaling Postgres 425
- Too Many Table Danger | Scaling Postgres 424
- New Backup Tool | Scaling Postgres 423
- Scale Out Funding | Scaling Postgres 421
Explore listener stats, chart rankings, contacts and more on the Scaling Postgres podcast page.