# BugBash '26 Notes: Peter Alvaro on Robust Distributed Systems

DevFeed: [BugBash '26 Notes: Peter Alvaro on Robust Distributed Systems](<https://devfeed.tech/articles/bugbash-26-morning-of-day-1-41836.md>)

Original publisher: [Read original article](<https://muratbuffalo.blogspot.com/2026/04/bugbash26-morning-of-day-1.html>)

Author: Murat (noreply@blogger.com)

Published: 2026-04-25T15:45:00Z

Content type: article

Language: en

Sources: [Metadata](<https://devfeed.tech/sources/metadata.md>)

Topics: [distributed-systems](<https://devfeed.tech/topics/distributed-systems.md>), [consistency](<https://devfeed.tech/topics/consistency.md>), [Latency](<https://devfeed.tech/topics/latency.md>), [Chaos Engineering](<https://devfeed.tech/topics/chaos-engineering.md>), [Availability](<https://devfeed.tech/topics/availability.md>), [Deadlock](<https://devfeed.tech/topics/deadlock.md>), [Software Testing](<https://devfeed.tech/topics/software-testing.md>), [observability](<https://devfeed.tech/topics/observability.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [automated-reasoning](<https://devfeed.tech/tags/automated-reasoning.md>), [availability](<https://devfeed.tech/tags/availability.md>), [consistency](<https://devfeed.tech/tags/consistency.md>), [deadlock](<https://devfeed.tech/tags/deadlock.md>), [distributed-systems](<https://devfeed.tech/tags/distributed-systems.md>), [fault-tolerance](<https://devfeed.tech/tags/fault-tolerance.md>), [formal-methods](<https://devfeed.tech/tags/formal-methods.md>), [instrumentation](<https://devfeed.tech/tags/instrumentation.md>), [latency](<https://devfeed.tech/tags/latency.md>), [observability](<https://devfeed.tech/tags/observability.md>), [testing](<https://devfeed.tech/tags/testing.md>), [trip-report](<https://devfeed.tech/tags/trip-report.md>)

## AI overview

Notes from a BugBash '26 talk by Peter Alvaro review approaches to robust distributed systems, including coordination avoidance, the CALM theorem, deadlock detection, garbage collection, and lineage-driven fault injection. The notes also discuss tradeoffs involving latency, availability, observability, instrumentation, and redundancy.

## Source excerpt

Continuing with notes from the BugBash talks. Yes, all of this goodness, including Will Wilson's keynote was before lunch the first day. Where all the ladders start Peter Alvaro, Associate Professor of Computer Science @ UC Santa Cruz In this talk, Peter reflects back on his 20 years of distributing systems work. The cover image is Don Quixote (which is Peter) attacking the windmill (robust distributed systems) with a spear (which is some singular solution often borrowed from databases). The first attack was through the use of arcane algebras. This is a purist approach of getting it right the first time. This was during Peter's PhD at UC Berkeley, where Neil Conway was also a peer and collaborator. In his own admission, this was incited by a naive framing around what makes distributed systems difficult? The target was uncertainty regarding order and timing, which cause distributed consistency problems, and require coordination. But distributed coordination comes at the cost of latency, performance variability, decreased availability. Peter said, they were influenced by James Hamilton (LADIS'08 talk), and Pat Helland's work around avoiding coordination. Peter then talked about two similarly sounding problems, deadlock detection versus garbage collection, in a partitioned replicated distributed system. While these have similar formulations around strongly connected components, the first one is a monotonic problem, and the second not! When new information arrives, the first is positive, and second is the negative direction-seeking. They had formulated the CALM theorem to capture how monotonicity composes to properties on programs. This sounds grand and very promising, but not even close to reaching the target, solving the robust distributed systems problem. The first problem is that disorder is not the whole story! The partial failure problem, rather than just binary failures, throws a wrench in the works. The second problem is that nobody wants to buy declarative lang