stefan
@kokope11i.bsky.social
amateur watchmaker (as in making more work for actual watchmakers), keeper of rabbits, gamer, dad, outdoorsy, jam bands, meditation, sober
I used to play with relatively large Oracle DBs. The concept that BlueSky uses one DB instance PER USER is wild.
Own hardware, bandwidth, caching, load balancing, and lots of cores. Yes, yes, and yes. Triggers fond memories of operating enterprise software. Also nightmares and fires drills.
Own hardware, bandwidth, caching, load balancing, and lots of cores. Yes, yes, and yes. Triggers fond memories of operating enterprise software. Also nightmares and fires drills.
An unordered / non-exhaustive list of things that helped scale Bluesky's infra efficiently:
+ Exiting the cloud (colocation)
+ HAProxy w/many Node backends
+ Go w/clever code
+ ScyllaDB
+ SQLite w/per user databases
+ Redis w/many instances
+ AMD servers w/many cores
+ Purchasing bandwidth directly
+ Exiting the cloud (colocation)
+ HAProxy w/many Node backends
+ Go w/clever code
+ ScyllaDB
+ SQLite w/per user databases
+ Redis w/many instances
+ AMD servers w/many cores
+ Purchasing bandwidth directly
November 18, 2024 at 2:36 PM
I used to play with relatively large Oracle DBs. The concept that BlueSky uses one DB instance PER USER is wild.
Own hardware, bandwidth, caching, load balancing, and lots of cores. Yes, yes, and yes. Triggers fond memories of operating enterprise software. Also nightmares and fires drills.
Own hardware, bandwidth, caching, load balancing, and lots of cores. Yes, yes, and yes. Triggers fond memories of operating enterprise software. Also nightmares and fires drills.
As someone getting into watchmaking. There is now something special about a watch I haven't opened yet. I haven't had a chance to damage anything, and I know the hands are on straight.
November 15, 2024 at 4:30 PM
As someone getting into watchmaking. There is now something special about a watch I haven't opened yet. I haven't had a chance to damage anything, and I know the hands are on straight.