#database #devops #pattern #reading-list
🔗 Squeeze the hell out of the system you have
About a year ago, I raised a red flag with colleagues and managers about Postgres performance. Our database was struggling to keep up with the load generated by our monolithic SaaS application. CPU utilization was riding between 60 and 80%, and at least once it spiked to 100%, causing a brief outage.
Now, we had been kicking the can down the road with respect to Postgres capacity for a long time. When the database looked too busy, we'd replace it with a bigger instance and move on. This saved us a lot of time and allowed us to focus on other things, like building features, which was great.
But this time, it wasn't possible to scale the DB server vertically: we were already on the biggest instance. And we were about to overload that instance.
⚠️ This post links to an external website. ⚠️
If this post was enjoyable or useful for you, please share it! If you have comments, questions, or feedback, you can email my personal email. To get new posts, subscribe use the RSS feed.