Comment by cultofmetatron
5 hours ago
we have a pretty intensively used postgres backed app handling thousands of users concurrently. After 6 years and thousands of paying custoners, we are only now approaching to the limits of what it can support on the horizon. TLDR: when you get there, you can hire some people to help you break things off as needed. if you're still trying to prove your business model and carve yoruself a segment of the market, just use postgres
Thanks for sharing! Big part of the reason why I decided on postgres, everything I've read about people using it in prod tells me that most organizations never really grow beyond requiring anything more than what it offers.
Most of the time just re-casting what you want in a horizontally shardable way is the "right" way to do it with any rdbms (if you scale) but at this point you can get boxes on AWS with 32TiB of ram, and most organizations don't have that much total data across their entire suite of stuff (many do, most don't.)