Postmortems are underrated
You can read every diagram in the world, but nothing teaches you distributed systems faster than seeing exactly how Cloudflare or Discord took down their own system.
Here are 5 postmoderns you should read:
1. https://t.co/OxEN8F6kr6
Postmortem of database outage of January 31 (A great example of transparency, detailed timeline, and clear lessons learned)
2. https://t.co/ev7vEWOThx
Slack’s Incident on 2-22-22 (A strong example of how cascading failures happen in complex systems)
3. https://t.co/yVWHoXLogs
Meta - More details about the October 4 outage (A useful postmortem for understanding network failures at scale)
4. https://t.co/CZGQyP2Iyy
Post mortem on the Cloudflare Control Plane and Analytics outage (A good example of connecting outage cause, recovery, and follow-up fixes)
5. https://t.co/4hKtXrqjw4
AWS Post-Event Summaries (A solid resource for studying how large platforms document incidents consistently)
This is where your thinking starts to mature.
You stop asking only how the system should work and start asking how it fails.
If you have another good share here.
Just built a system that rewrites and improves Jira issue descriptions using AI. Our documentation finally reads like it was written by humans — not by engineers in a hurry 😄
🚀 Introducing drawDB! 🚀
Free, open source, simple, and intuitive data modeler and SQL generator. With drawDB, you can build ER diagrams, export SQL scripts, and more in a simple and intuitive editor—all right in your browser.
#database#sql#web
https://t.co/Kvw7wtJxxH
@gitbutler
Nice and cross platform solution with virtual branches and ai commits. Free for personal usage but have a plans to chart team members.
Hi @willemschots! I noticed you haven’t been writing on your blog https://t.co/PIe6MS6A8a lately. Your articles are really good, and I recommend them to everyone in my company who wants to work with Go. Would love to see more content from you!
@pvldb Follow‑up: GC pauses are an ever‑present source of latency - even at steady loads (e.g., in Go). Does your D3 "dynamic delay" bucket model these runtime stalls as well, or is it limited to network jitter? Curious how Cabinet handles inherent GC latency.