🟪 => 🌎
After almost 8 years at Heroku, time for a new adventure PlanetScale.
No eye, no ear, no nose, no tongue, no body, no mind, no shape.
Erstwhile SRE, database person, human.
| Blog | https://matt.blwt.io/ |
| Bluesky | https://bsky.app/profile/matt.blwt.io |
🟪 => 🌎
After almost 8 years at Heroku, time for a new adventure PlanetScale.
Genuinely great paper out from Meta on Scribe, from VLDB: https://www.vldb.org/pvldb/vol18/p4817-karpathiotakis.pdf
It's an excellent breakdown on how to design such systems with explicit goals around write availability.
https://matt.blwt.io/post/overengineering-sleep/
After seeing this and the complaints about the implementation, let's dig into re-implementing "sleep" for Linux-likes and BSD-likes in Zig.
You probably have an app/service that performs operations against a Postgres database.
Do you change the transaction isolation level from the default?
https://krebsonsecurity.com/2024/12/how-to-lose-a-fortune-with-just-one-bad-click/
Please, I beg you, do not co-locate your MFA with one account. Do not screenshot your secrets. Do not put them in notes docs, text files etc.
Yes, I feel the same way with 1Password TOTP.