News for hackers. Stuff that matters.
Re:The Startup CTO's Handbook by rco8786 on Wednesday March 12, 2025 @06:49PM (#43348523)
Ah yea the old “web scale” phase. I think everyone’s more or less accepted that very, very few startup-level (or even SMB-level) workloads need more scalability then Postgres/mysql gives.

My favorite example is that Twitter used mysql for all tweets, writing ~5k/s 24/7/365, until about 2016ish. Well into being a public company with billions in revenue and 300mm+ MAUs.

Re:The Startup CTO's Handbook by reducesuffering on Wednesday March 12, 2025 @10:27PM (#43349825)
Has everyone accepted that?

3/4 companies in the Bay Area senior software engineer interviews require a System Design interview where they will tell you "what if you had 10m users" and expect a distributed write-heavy sharding answer

Re:The Startup CTO's Handbook by rco8786 on Wednesday March 12, 2025 @11:13PM (#43350066)
You’re not wrong in the literal sense. But the “inside baseball” of that question is just that it’s a prompt to talk about how you would horizontally scale a system should the need arise. It’s not a prompt to start questioning whether 10mm or 200mm is the specific limit.
Re:The Startup CTO's Handbook by femiagbabiaka on Thursday March 13, 2025 @01:41PM (#43355601)
Well that's the thing. You don't need a NoSQL database to design a data tier that scales to accommodate distributed write-heavy workloads.
Re:The Startup CTO's Handbook by closeparen on Friday March 14, 2025 @02:12PM (#43365452)
Lots of people were mad that my employer developed a new distributed NoSQL database engine, but it was literally just an API to encapsulate what an application doing "sharded MySQL" would do in its own data tier. A lot of this is a question of framing and storytelling.