A distributed systems reliability glossary

Home | cse223b

CSE 223B is a 4-unit graduate subject with lectures, paper discussions, a midterm, and technical report exercise, and a major term research project culminating in writing a research paper of your own. It will present abstractions and implementation techniques that facilitate the design of distributed systems–including both operating systems and sophisticated Internet servers–that can deal with the demands of real-world workloads. Topics will include efficient operating system primitives, high-performance network servers, load shedding, storage systems, security, and fault tolerance.

Fly.io Distributed Systems Challenge

Documentation and guides from the team at Fly.io.

Software Should Work

An independent conference on software reliability in Columbia, MO on July 16-17, 2026

Atproto for distributed systems engineers - AT Protocol

In this article we're going to explore atproto from the perspective of distributed backend engineering.

A Critique of the CAP Theorem

The CAP Theorem is a frequently cited impossibility result in distributed systems, especially among NoSQL distributed databases. In this paper we survey some of the confusion about the meaning of CAP, including inconsistencies and ambiguities in its definitions, and we highlight some problems in its formalization. CAP is often interpreted as proof that eventually consistent databases have better availability properties than strongly consistent databases; although there is some truth in this, we show that more careful reasoning is required. These problems cast doubt on the utility of CAP as a tool for reasoning about trade-offs in practical systems. As alternative to CAP, we propose a "delay-sensitivity" framework, which analyzes the sensitivity of operation latency to network delay, and which may help practitioners reason about the trade-offs between consistency guarantees and tolerance of network faults.

Cloud native Go: building reliable services in unreliable environments

What do Docker, Kubernetes, and Prometheus have in comm…

Notes on software quality

“The absence of problems” is the best definition I can come up with for quality.

Dynamical Systems Group | Complex Systems, Engineered

Systems engineering firm that operationalizes emerging technology for high-reliability organizations. Scientific Computing, MBSE, Systems Integration.

How we use HashiCorp Nomad

A walkthrough on how we are improving the reliability of our management services running in each data center by using Nomad for dynamic task scheduling.

Declarative Server with NixOS: A Reproducible Infrastructure | Mustafa Erbay

A technical guide exploring how to create a declarative server configuration with NixOS, covering reproducibility and rollback processes.

Dynamo | Proceedings of twenty-first ACM SIGOPS symposium on Operating systems principles

Reliability at massive scale is one of the biggest challenges we face at Amazon.com, one of the largest e-commerce operations in the world; even the slightest outage has significant financial consequences and impacts customer trust. The Amazon.com ...

unfoldml/propsim

Property-based testing for distributed protocols

Drawing a map of distributed data systems — Martin Kleppmann’s blog

How we created an illustrated guide to help you find your way through the data landscape.

Cambria | Proceedings of the 8th Workshop on Principles and Practice of Consistency for Distributed Data

This summary was generated using automated tools and was not authored or reviewed by the article's author(s). It is provided to support discovery, help readers assess relevance, and assist readers from adjacent research areas in understanding the work. It is intended to complement the author-supplied abstract, which remains the primary summary of the paper. The full article remains the authoritative version of record. Click here to learn more.