README.md

Interactive Consistency Models

Demo

Disclaimer: this project is not yet production ready. Please avoid sharing it broadly, since there are still bugs and pedagogical shortcomings in the website that might confuse more than clarify.

You can watch a video of how to use the website here.

Pedagogical Motivation

This project aims to bring understanding to consistency models through interactive timeline diagrams. Through personal experience, I have found that consistency models are hard to teach* for the following reasons:

1. Most individuals new to distributed computing aren't familiar with reasoning about arbitrary interleavings of events (consistency models really are just about specifying what subset of event interleavings are acceptable).
2. Different models have exceptionally subtle differences, which leads learners to questions of the form: "so... how is model X any different from model Y?" and "why does this serialization satisfy model M but not model N"?
3. There are a lot of consistency models, and most of their names don't do a great job of remininding you what they really mean.

I think that the following ideas may help with these issues:

1. Letting people drag around events (within serializations) in their browser invites users into the world of arbitrarily complicated event interleavings, but allows them to explore interleavings at their own pace. An automated consistency-model checker can determine (and explain!) which models are satisfied.
2. We plan on creating a consistency model matrix, where element [i, j] satisfies model i but not does not satisfy some model j. Such a matrix would help answer questions of the form "how does M differ from N?", and I believe this type of matrix would be novel.
3. When consistency models are presented linearly (i.e. "weak" to "strong"), they can be hard to keep track of. But when models are thought of as a tree, it's possible to build up what some model guarantees by considering the guarantees of its children.

Additionally, to help understand what models are the most confusing (and perhaps why), we'll have quizzes as we walk through various consistency models. With user consent, we'll collect (anonymized) results, which we can later use to improve our work. The quizzes will likely be of the form:

• Using history H, create a serialization that satisfies this model M
• Using history H, create a serialization that satisfies M but not N

Making the System Model Visual

Existing System Model

In recent surveys of formal consistency models [Burkhardt, VV], consistency models are defined using the following system model:

• There are several sequential clients, each of which is called a "session"
• Clients issue "operations" to some shared data structure (like reads/writes to a shared variable)
• Operations can have associated metadata; most notably, a read operation also include what was read
• The set of operations issued by all clients is called a history
• A consistency model constrains what histories are allowed

Existing Consistency Models

Histories and constraints on histories don't tell us the entire story, though. They don't explain why a particular history ended up the way that it did. Take the following example, with two clients:

1: ---------------------------[R:3]---
2: --[W:3]---------[W:2]--------------

In this example, why is it the case that client 1 reads 3 even though 2 was the most recent write? In concrete terms, we can explain why this happened with the following reason:

1. Client 2's first write returned before it ever made it to client 1 (maybe it crashed?)
2. The network reordered the writes, so client 1 received write 3 after write 2

This concrete explanation is helpful, but something more general might help us reason about other situations. Generally, what we've just done is capture and express the uncertainty of distributed systems, where nodes can crash at any time and the network can drop packets, reorder them, delay them, etc. To capture the uncertainties of distributed systems, Burkhardt proposed the following relations:

1. Visibility: is an acyclic relation where (a, b) means that the effects of operation a are visible to operation b. In a message-passing system, this would mean that a write a issued by some client is visible to the client that issued b, before b was issued.
2. Arbitration: is a total ordering that specifies how write conflicts are resolved (it assumes sytem convergence).

These abstract executions are very helpful for reasoning about certain consistency models. For example, we can express monotonic writes very concisely:

$$ (a, b) \in so \longrightarrow (a, b) \in ar $$

The issue with abstract executions is that, because they're relations, they're not easily visualizable. We can't just look at a timeline diagram of a history and understand how the uncertainties of the underlying distributed system manifested: to do that, we'd also need to include the abstract executions.

Formalizing a Serialization

In this tool, we use serializations to explore consistency models. The histories tell us what the clients observed, and the serializations tell us why they observed what they did. In effect, the serializations help us visually express abstract executions in the form of timeline diagrams. This, of course, has been done before: The Art of Multiprocessor Programming (Herlihy, Shavit) use serialiations to teach consistency models, but just a few of the most important ones. Viotti and Vucolic's work have dozens of consistency models, but they don't formally define what a serialization is. Here, we do that.

Now, we sketch a definition for a serialization, and later formalize it. Here's the intuition:

• A serialization $i$ has all the operations from client $i$, as well as all the writes from the history
• All properties of the operations remain the same except for the start and end times, which are subject to some well-formedness constraints below

The constraints are as follow:

1. the writes coming from the other clients might move around, but they must not overlap with each other, since serializations are sequential. This is called the "non-overlapping property".
2. No operation can appear in a serialization earlier than it appears in the history. This is called the "no backwards movement property":

The formal definition of a serialization is now ready to be written out:

$$ \forall i \in [0, n), \forall h \in H, \exists s \in S_i \space s.t. \\ (h.proc = i \implies \text{Eq}(h, s)) \wedge \\ (h.proc \neq i \wedge h.op = wr) \implies \text{UntimedEq}(h, s) \wedge \text{FowardsMotion}(h, s) $$

The sub-predicates used are explained below:

• Eq(a, b) says that the two operations have exactly the same properties
• UntimedEq(a, b) says whether two operations, ignoring their start and end times, have the same properties
• ForwardMotion(a, b) says that b.stime > a.etime, meaning that b must move foward relative to a.

There are two final well-formedness predicate that we need. First, the non-overlapping property:

$$ \forall a \in S_i, \space \nexists b \in S_i \space | \space (a.stime <= b.etime) \wedge (b.stime <= a.etime) $$

And second, we just have to make sure that serializations don't have any more elements than what we want:

$$ \#S_i = \# { H|_{wr} \cup {op \in H : op.proc = i } } $$

Abstract Executions

Our end goal is to capture the abstract executions within serializations, so let's do that now.

First, we tackle the vis relation for some operations $a$ and $b$ where $a \xrightarrow{vis} b$:

• If $a$ and $b$ are both writes, then in all serializations, $a.etime &lt; b.stime$
• If $a$ is a write and $b$ is a read, then in serialization ${b.proc}$, $a.etime &lt; b.stime$.
• If $a$ is a read, then it's not visible to anything in the future, so we don't need to anything in these cases.

Next, we tackle the ar relation for some operations $a$ and $b$ where $a \xrightarrow{ar} b$. Since ar specifies a total ordering on writes as defined by the conflict resolution strategy, we can simply say that for all serializations, $a.stime &lt; b.stime$.

Animation Requirements

• Sliding: we should be able to smoothly transition an element from one location to another (as the crow flies), where a location can be a new start/end time, or another operation itself

• Individual element fade-ins and fade-outs: we should be able to fade-in an individual operation on a particular history/serialization

• Slide: we should be able to slide an element from one position to another

• Fade-outs: we should be able to fade out an entire history/serialization pair, and then fade-in another history/serialization

• Control over what text is rendered: each "slide" of the tutorial can have description text.

• These animations should be chainable: with one user input, we should be able to trigger a series of animations. The Google Slides options probably work for us: On Click, With Previous, After Previous.

• Animations should be reversable so that readers can replay confusing concepts

Outstanding Functional Improvements

To make the UI reflect the previous discussion, here are the improvements that we should make:

• For $S_i$, all operations in the history belonging to process $i$ should not be anchored in place. This is to say, all of the original operations should stay in place, and the operations that show up as a result of message passing should be the only ones that are moveable.
• Well-formedness predicates should not be expressed within the predicate tree: the UI should prevent any non well-formed serialiations from being rendered. If you try to move a messaging passing operation to the left of its "original" operation, the UI shouldn't let you do that (maybe a red line should appear).
• Message passing operations should appear moveable in the serialization, and the original ones should appear as fixed (maybe lower opacity?)
• Add explainability to the predicate checker
• Unit tests to GitHub actions
• Create a "model M but not model N" matrix of consistency models for quick reference