Nick | OneThingWell.dev

4.7K posts

Nick | OneThingWell.dev

Nick | OneThingWell.dev

@onethingwelldev

30+ years in software development, mostly posting on topics related to: #tech #programming #webdev #foss #linux #devops #infosec #privacy https://t.co/X9JJPmiHUf

🇪🇺 加入时间 Mayıs 2021
1.2K 关注1.2K 粉丝
Charly@CSDevAr
Charly@CSDevAr@CSDevAr·
@betterways_dev Of course! Well *work* is too much of a word perhaps 😅 Glad to see you in the circus though, Nick!
English
1
0
1
44
Nick | OneThingWell.dev
Nick | OneThingWell.dev@onethingwelldev·
@SrihariVernekar There's definitely less idiots than here, but it's simple to use. Bluesky currently requires an invitation, Mastodon generally doesn't.
English
0
0
2
18
Nick | OneThingWell.dev
Nick | OneThingWell.dev@onethingwelldev·
@dgut_ At this point, Twitter is a lost cause, and the sooner we accept that, the better.
English
0
0
0
191
David Gut
David Gut@dgut_·
Don't know about you guys, but I'm genuinely sad Twitter is going this way. I don't mind the lack of content moderation, in fact, it's a good thing. But making Twitter a more restrictive platform, in developers' minds, is the platform's death. Some will say "It's temporary". What is not temporary is the direction Twitter is going.
English
8
1
24
6.2K
Nick | OneThingWell.dev
Nick | OneThingWell.dev@onethingwelldev·
@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 :)
English
1
0
1
20
charaf
charaf@charafmrah·
@betterways_dev In memory 😳 that’s an interesting approach for sure!
English
1
0
1
18
charaf
charaf@charafmrah·
- But they used X technology to make it work - So it’s still MySQL ⁉️ - But YouTube moved to another database back in 2019 - So they used MySQL to serve billions before that ⁉️ - It’s not 1 DB instance - So it’s still MySQL, just several instances ⁉️ MySQL doesn’t scale :(
charaf@charafmrah

WordPress: 810 million websites using it ➡️ runs on MySQL YouTube: 2.1 billion monthly active users ➡️ runs on MySQL Clearly MySQL doesn't scale :(

English
3
0
7
1.2K
Nick | OneThingWell.dev
Nick | OneThingWell.dev@onethingwelldev·
@charafmrah and keep hot data in memory. For freelancing, at this point I'm okay with pretty much anything I come across :)
English
1
0
1
18
Nick | OneThingWell.dev
Nick | OneThingWell.dev@onethingwelldev·
@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]
English
2
0
2
27
Nick | OneThingWell.dev
Nick | OneThingWell.dev@onethingwelldev·
@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.
English
1
0
1
14
charaf
charaf@charafmrah·
@betterways_dev But depending on your database & type of data you’re storing, the challenge can be more costly depending on the initial database you chose (e.g Discord moving from MongoDB)
English
1
0
1
25
Nick | OneThingWell.dev
Nick | OneThingWell.dev@onethingwelldev·
@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]
English
1
0
1
16