@DistribSystems

I tweet/retweet interesting stuff about #DistributedSystems and #compsci. Suggest links/papers/conversations via DM! Tag for retweets. Run by @federico_ponzi

Joined January 2017
  • Tweets0
  • Following0
  • Followers0
0Media
Big List of 20 Common Bottlenecks highscalability.com/big-list… In Zen And The Art Of Scaling, Sullivan offered an interesting conjecture: there are 20 classic bottlenecks. In practice we all know bottlenecks come in infinite flavors, all tasting of sour and ash.
11
81
4,122
Life Beyond Distributed Transactions queue.acm.org/doi/10.1145/30… Practical approaches used in the implementation of large-scale mission-critical applications in a world that rejects distributed transactions.
2
43
2,672
[new blog post] Jetpack: Consensus Made Generally Fast (OSDI '26) muratbuffalo.blogspot.com/20…
8
1
58
5,585
Distributed Bytes retweeted
Marc Brooker@MarcJBrooker
Aug 31
Did you know that Aurora DSQL now supports foreign key constraints? The team's done a great job here: FKCs that scale well, especially for your read-heavy workloads. Check it out here: docs.aws.amazon.com/aurora-d… Quick thread on how FKCs in DSQL work...
5
15
2
89
9,918
Distributed Bytes retweeted
Colin Breck
@breckcs
Aug 19
The trend of using S3 for databases is continuing, if not gaining momentum. I've seen three or four new examples in the past week with Cursor Origin being the headline yesterday. I wrote about why I thought this would happen a couple of year ago: blog.colinbreck.com/predicti…

Predicting the Future of Distributed Systems

There are significant changes happening in distributed systems.

blog.colinbreck.com
8
26
2
225
13,760
Git at any scale cursor.com/blog/git-at-any-s… Twenty years after Linus Torvalds created it, Git has become an industry standard. The average company rely on a centralized host. And hosting a Git repository, it turns out, is an incredibly hard thing to do.
7
841
On building scalable control planes allthingsdistributed.com/202… On the surface, the control plane looks quite boring: it records what should exist and reconciles that with what actually does.
11
111
4,475
Making 768 servers look like 1 planetscale.com/blog/making-… A single database server cannot handle such demand, so we must spread the queries and data out across many servers with database sharding.
13
117
6,534
Client-Side Load Balancing at a Million Requests Per Second engineering.zalando.com/post…
3
49
3,585
Aurora DSQL: Scalable, Multi-Region OLTP brooker.co.za/blog/2026/07/1… Paper: arxiv.org/abs/2607.13276
1
21
1,848
How TLA+ Caught a Silent Data Divergence Bug in Postgres’s pg_rewind multigres.com/blog/tla-pg-re…
4
1
34
4,248
Queues Don't Fix Overload ferd.ca/queues-don-t-fix-ove… To oversimplify things, most of the projects I end up working on can be visualized as a very large bathroom sink. User and data input are flowing from the faucet, down 'till the output of the system[..]
1
8
104
7,950
Distributed Bytes retweeted
Marc Brooker@MarcJBrooker
May 19
Remy's blog post is good, but I think it severely overstates the simplicity of WSI when compared to traditional SI. What we would agree on: SSI is a little weird, and I see it mostly as a pragmatic historical artifact that the 'right solution'.
Distributed Bytes@DistribSystems
May 19
Simple and Correct Snapshot Isolation remy.wang/blog/si.html Snapshot isolation (SI) is a popular approach to concurrency control in databases systems. It avoids many forms of anomalies, yet provides a high degree of concurrency, especially for read-heavy workloads.
3
4
83
13,508
Simple and Correct Snapshot Isolation remy.wang/blog/si.html Snapshot isolation (SI) is a popular approach to concurrency control in databases systems. It avoids many forms of anomalies, yet provides a high degree of concurrency, especially for read-heavy workloads.
1
3
1
28
14,785
Notes on Paxos matklad.github.io/2020/11/01…
3
41
2,066
Hypothesis, Antithesis, synthesis antithesis.com/blog/2026/heg… Hegel is an attempt to bring the quality of property-based testing found in Hypothesis to every language.
17
1,168
Testing for DR Failover Testing usenix.org/conference/srecon… A simplified scenario is recovery from a full data centre failure. The Zendesk Chat backend infrastructure operates in a single data centre. The way to be sure that DR works is to perform a real failover.
1
14
986
Top Five Scalability Patterns f5.com/company/blog/top-five…
8
55
2,853
Building A Billion User Load Balancer usenix.org/conference/srecon…
37
1
461
17,298
What Is Coordination, Really? jhellerstein.github.io/blog/…
56
2,556
Load more