December 20, 2025
Who's on-call at 3AM? Not it
Go ahead, self-host Postgres
Dev says DIY Postgres beats pricey cloud; commenters split between 'own it' and 'outsourced sleep'
TLDR: One engineer says self-hosting Postgres matched cloud performance and saved money, challenging the need for AWS RDS. Comments split: veterans celebrate DIY reliability, startup voices warn of lost time, and many mock 3AM heroics—raising real questions about cost, focus, and sleep in database choices.
Should you host your own database? The internet is yelling “yes” and “are you out of your mind?” after one dev said self-hosted Postgres powered thousands of users with only 30 minutes of stress, while pricey AWS RDS is just the same engine with fancy wrappers. Old-school admins waved receipts: “20 years self-hosted—rock solid.” Startup folks shot back: saving $50/month isn’t worth burning a week on setup and forever on maintenance, arguing the cloud buys focus and someone else’s pager.
Then the 3AM pager drama exploded. One commenter confessed only one job ever truly needed middle-of-the-night fixes, roasting macho uptime culture and asking, “does anyone actually need to wake up for overnight traffic?” Meanwhile, the DIY crowd flexed: PostgREST turns your database into a plug-and-play API—“make a view and boom, you’ve got GET; add a function, now you’ve got POST.” The meme of the day: “Put it on Postgres”—even metrics, because why not?
Between cloud “tax” and control freak bliss, the crowd split: pay for managed ops or own your destiny, your tuning knobs, and your sleep. The only thing everyone agreed on? Whether it’s your server or theirs, you’ll pay—in dollars, time, or midnight coffee. Either way, choose wisely.
Key Points
- •The author has self-hosted Postgres for two years, serving thousands of users and tens of millions of queries daily, with minimal issues and lower costs.
- •Managed services like AWS RDS largely run standard open-source Postgres with added operational tooling (monitoring, backups, failover, pooling).
- •AWS RDS pricing example: db.r6g.xlarge (4 vCPUs, 32GB RAM) is listed at $328/month before storage, backups, or multi-AZ.
- •Historical context: pre-cloud era commonly involved running databases locally; AWS RDS launched in 2009 and became widely adopted as cloud use grew around 2015.
- •A migration from RDS to self-hosted using pg_dump yielded identical or better performance due to the ability to tune parameters.