A bit about me: I started playing with programming languages when I was a kid in the early 90s.
I'm still on a journey to learn as many different ways to build (and break) things as possible. [1/2]
#techtwitter#buildinpublic#100daysofcode
@SrihariVernekar There's definitely less idiots than here, but it's simple to use. Bluesky currently requires an invitation, Mastodon generally doesn't.
@charafmrah Yeah, I have projects in nim where I was fetching the data from the index in memory, rendering and returning the response in <1ms. Just "SELECT 1" from MySQL would take way more than that :)
@charafmrah Compression was a separate issue, MySQL scaling was a much bigger issue - it wasn't only sluggish, the site was completely dead most of the time, and users have starting to give up on it.
For my own projects, I tend to go with something more low-level (like lmdb) [1/2]
@charafmrah Yeah, it's a tricky position. Ideally, if you're working on something that has a potential for getting big, you'd think about scaling right from the start and implement adequate architecture. On the other hand, there's a good chance that the project will fail and it won't matter.
@charafmrah Yes, I understand. But it's also important to understand that scaling MySQL is a nightmare. You mentioned YouTube... I don't know if you remember the early days, but it wasn't pretty - not being able to scale MySQL almost killed it. Sharding requires [1/2]