distributed systems man. why do we do this to ourselves
November 24, 2024 at 4:05 AM
distributed systems man. why do we do this to ourselves
never ask a distributed systems engineer what time it is
February 15, 2025 at 11:54 PM
never ask a distributed systems engineer what time it is
Seems like a safe bet that object storage as a foundation of data systems architecture is here to stay blog.colinbreck.com/predicting-t...
Predicting the Future of Distributed Systems
There are significant changes happening in distributed systems.
blog.colinbreck.com
November 30, 2024 at 4:31 PM
Seems like a safe bet that object storage as a foundation of data systems architecture is here to stay blog.colinbreck.com/predicting-t...
It's funny that the most challenging distributed systems problems are not, like, consensus algorithms, but much less flashy things like versioning and upgrades
September 26, 2026 at 5:29 PM
It's funny that the most challenging distributed systems problems are not, like, consensus algorithms, but much less flashy things like versioning and upgrades
Hello, Bluesky users!
I curate and maintain list of resources on testing distributed systems. You might have seen it before. It's a good one, if I may say so myself.
asatarin.github.io/testing-dist...
I curate and maintain list of resources on testing distributed systems. You might have seen it before. It's a good one, if I may say so myself.
asatarin.github.io/testing-dist...
Testing Distributed Systems
Curated list of resources on testing distributed systems
asatarin.github.io
November 19, 2024 at 5:26 AM
Hello, Bluesky users!
I curate and maintain list of resources on testing distributed systems. You might have seen it before. It's a good one, if I may say so myself.
asatarin.github.io/testing-dist...
I curate and maintain list of resources on testing distributed systems. You might have seen it before. It's a good one, if I may say so myself.
asatarin.github.io/testing-dist...
Three basic suggestions for getting into distributed systems
- Read DDIA
- Follow MIT 6.5840
- Do fly dot io distributed systems challenge
(no particular order)
- Read DDIA
- Follow MIT 6.5840
- Do fly dot io distributed systems challenge
(no particular order)
November 18, 2024 at 10:36 PM
Three basic suggestions for getting into distributed systems
- Read DDIA
- Follow MIT 6.5840
- Do fly dot io distributed systems challenge
(no particular order)
- Read DDIA
- Follow MIT 6.5840
- Do fly dot io distributed systems challenge
(no particular order)
high-paid distributed systems engineers be like "I invented a clock"
January 25, 2024 at 1:24 AM
high-paid distributed systems engineers be like "I invented a clock"
Interviewer: Can you explain this gap in your resume?
Distributed systems engineer: Eventually.
Distributed systems engineer: Eventually.
Interviewer: Can you explain this gap in your resume?
Cryptography engineer: That part is cleared to make operations over my CV fit in the output register without carries.
Cryptography engineer: That part is cleared to make operations over my CV fit in the output register without carries.
Interviewer: Can you explain this gap in your resume?
Game dev: ah yeah I had fucked up a transformation matrix, so that section of my life was rendered outside the camera's field of view
Game dev: ah yeah I had fucked up a transformation matrix, so that section of my life was rendered outside the camera's field of view
December 22, 2024 at 2:57 AM
Interviewer: Can you explain this gap in your resume?
Distributed systems engineer: Eventually.
Distributed systems engineer: Eventually.
I use an equivalent for distributed systems: they're *all* eventually consistent at a geologic time scale.
July 20, 2025 at 4:14 PM
I use an equivalent for distributed systems: they're *all* eventually consistent at a geologic time scale.
just worth linking this again
ATProto for distributed systems engineers - AT Protocol
AT Protocol is the tech developed at Bluesky for open social networking. In this article we're going to explore AT Proto from the perspective of distributed backend engineering.
atproto.com
April 26, 2025 at 12:27 AM
just worth linking this again
First rule of distributed systems: don’t build a distributed system if you can avoid it
Second rule of distributed systems: you probably can’t avoid it
Second rule of distributed systems: you probably can’t avoid it
August 6, 2025 at 1:22 AM
First rule of distributed systems: don’t build a distributed system if you can avoid it
Second rule of distributed systems: you probably can’t avoid it
Second rule of distributed systems: you probably can’t avoid it
basketball fans 🤝 distributed systems engineers
This is a niche concern but the "gather step" is a crime against humanity.
August 19, 2026 at 2:59 PM
basketball fans 🤝 distributed systems engineers
distributed systems in theory: we run our code across several networked machines so that a failure of one doesn’t break the system as a whole
distributed systems in practice, apparently: hey it’s probably fine to put all our eggs in the us-east-1 basket right?
distributed systems in practice, apparently: hey it’s probably fine to put all our eggs in the us-east-1 basket right?
October 20, 2025 at 10:57 AM
distributed systems in theory: we run our code across several networked machines so that a failure of one doesn’t break the system as a whole
distributed systems in practice, apparently: hey it’s probably fine to put all our eggs in the us-east-1 basket right?
distributed systems in practice, apparently: hey it’s probably fine to put all our eggs in the us-east-1 basket right?
Rule #1 of distributed systems. Don't build a distributed system if you can help it.
Rule #2 of distributed systems. Can you make the distributed bits someone else's problem? Do that instead.
Rule #2 of distributed systems. Can you make the distributed bits someone else's problem? Do that instead.
November 21, 2024 at 4:16 PM
Rule #1 of distributed systems. Don't build a distributed system if you can help it.
Rule #2 of distributed systems. Can you make the distributed bits someone else's problem? Do that instead.
Rule #2 of distributed systems. Can you make the distributed bits someone else's problem? Do that instead.
Distributed systems classes do matter!
Alito's argument – that counting ballots after Election Day means "the electorate’s choice does not occur on election day, and the federal election-day statutes are violated" – is some of the dumbest reasoning I have ever seen. The "choice" doesn't occur at the time of counting!
June 29, 2026 at 3:13 PM
Distributed systems classes do matter!
Resilient ad-hoc distributed systems designs for rebel cruisers.
What’s your fake starwars academic paper
September 23, 2026 at 1:51 AM
Resilient ad-hoc distributed systems designs for rebel cruisers.
modern CPUs are just very small distributed systems
July 3, 2023 at 9:42 PM
modern CPUs are just very small distributed systems
I love that after all these years the most important workhorse of most distributed systems is still the relational database
August 29, 2026 at 10:23 PM
I love that after all these years the most important workhorse of most distributed systems is still the relational database
hello systems distributed!
July 25, 2026 at 5:11 PM
hello systems distributed!
I can have hobbies
Aggregate effects of processing load in a distributed physics simulation
Describing general relativity as a quirk of distributed computation is satisfying to me as a distributed systems engineer.
pfrazee.leaflet.pub
October 23, 2025 at 12:08 AM
I can have hobbies
There's surprisingly many people on this website who know better how one should build very complex distributed systems than the people in the room who are building very complex distributed systems…
April 19, 2026 at 11:31 PM
There's surprisingly many people on this website who know better how one should build very complex distributed systems than the people in the room who are building very complex distributed systems…
📺 "Distributed Systems 6.2: Raft"
Enjoyed this intro to the Raft consensus algorithm, part of a larger DistSys lecture series by @martin.kleppmann.com. The pseudo-code makes it actually digestible really well. Great watch!
www.youtube.com/watch?v=uXEY...
Enjoyed this intro to the Raft consensus algorithm, part of a larger DistSys lecture series by @martin.kleppmann.com. The pseudo-code makes it actually digestible really well. Great watch!
www.youtube.com/watch?v=uXEY...
Distributed Systems 6.2: Raft
YouTube video by Martin Kleppmann
www.youtube.com
November 22, 2025 at 9:56 PM
📺 "Distributed Systems 6.2: Raft"
Enjoyed this intro to the Raft consensus algorithm, part of a larger DistSys lecture series by @martin.kleppmann.com. The pseudo-code makes it actually digestible really well. Great watch!
www.youtube.com/watch?v=uXEY...
Enjoyed this intro to the Raft consensus algorithm, part of a larger DistSys lecture series by @martin.kleppmann.com. The pseudo-code makes it actually digestible really well. Great watch!
www.youtube.com/watch?v=uXEY...
Someone asked for some resources to learn more about distributed systems today and my knee-jerk was to go to Jeff Dean's Google Research page and read the distributed systems papers there starting w/ the oldest and skipping the ML stuff.
MapReduce, BigTable, Spanner, Tail at Scale, all excellent.
MapReduce, BigTable, Spanner, Tail at Scale, all excellent.
Jeffrey Dean
research.google
November 1, 2024 at 4:29 AM
Someone asked for some resources to learn more about distributed systems today and my knee-jerk was to go to Jeff Dean's Google Research page and read the distributed systems papers there starting w/ the oldest and skipping the ML stuff.
MapReduce, BigTable, Spanner, Tail at Scale, all excellent.
MapReduce, BigTable, Spanner, Tail at Scale, all excellent.
Who (else) up obsessing over distributed systems
October 26, 2025 at 9:28 AM
Who (else) up obsessing over distributed systems
the long arc of history tends toward distributed systems
graze.leaflet.pub/3m4yjmbnyec2... it's nuts how much better we're going to be able to make things
knowledge, context, detail will *always* live at edges. An architecture that ignores this, and assumes a singular organization (or "agent" lmao) can "figure it out" is gonna get its ass kicked
knowledge, context, detail will *always* live at edges. An architecture that ignores this, and assumes a singular organization (or "agent" lmao) can "figure it out" is gonna get its ass kicked
About The Other Night... - Graze Newsletter
How Graze is defining the next era of a decentralized, open social attention economy.
graze.leaflet.pub
November 7, 2025 at 5:06 AM
the long arc of history tends toward distributed systems