Distributed Systems — Spring 2024

Instructor Aurojit Panda (E-mail)
Help? CampusWire (use code 5577 to join)
When? Wednesday 4:55pm to 6:55pm
Where? Warren Weaver Hall Room 101
Hours Monday 1-2pm and Wednesday 3-4pm (or by appointment)
Hours 60 Fifth Ave 405
Consensus visualized poorly

This course is a graduate introductory course on distributed systems.


This class requires (contributions to the final grade are in parenthesis):

  • Reading between 2 and 3 research papers each week, analyzing their content and participating in discussions during lectures. (5% of final grade)
  • Work on four programming assignments or labs. Details below. (40% of final grade)
  • Work on a more open ended final project, details of which are below. (15% of final grade)
  • A midterm on October 19, 2022 covering all the material taught until that date. (15% of final grade)
  • A final exam (date TBD) covering all of the material in the class. (25% of final grade)

The late policy and collaboration policy are below. Make sure you have read and understood both.


This is tentative and subject to change

Date Topic & Readings Other
01/24 Introduction, no reading Notes
Whiteboard PDF
01/31 Clocks and times in distributed systems
Lamport '78
Alpern and Schneider' 85
Chandy '85
Lab 1 Out (Due Feb 14)
Pre-class notes
Whiteboard PDF
02/07 Remote Procedure Calls
Nelson '81 (read chapter 1 and 2, pages 1 -- 31)
Birrel '84
Herlihy and Wing '90
Pre-class notes
Whiteboard PDF
02/14 Linearizability and CAP
Sela, Herlihy, Petranak '21
Lee, et al '15
Gilbert and Lynch '02
Lab 1 due
Notes (for lectures 3 and 4)
Pre-class notes
Whiteboard PDF
02/21 Replicated State Machines
Schneider '90
Lamport '78
Lab 2 and 3 out (Lab 2 due 03/06, Lab 3 due 03/20)
Pre-class notes
Whiteboard PDF
02/28 Raft
Ongaro and Ousterhout '14
Pre-class notes
Final project suggestions
Whiteboard PDF
03/06 Paxos
Chandra, Griesmer, Redstone'07
(Optional) Lamport'98
Whiteboard PDF
Lab 2 due
Final project proposals due.
03/20 Spring Break Lab 3 due
Final project proposals due.
03/27 Randomized Consensus
Ben-Or '83
Pan et al '21
Errata for Pan et al'21
Optional: Aguilera and Toueg'10
Lab 4 out
Whiteboard PDF
04/03 Consensus and FLP
Fischer, Lynch and Paterson '85
Dwork, Lynch and Stockmeyer '88
Pre-Lecture Notes
04/10 Byzantine Fault Tolerance
Lamport, Shostak and Pease '82
Castro and Liskov '99
Lab 4 due
Pre-Lecture Notes
04/17 Failure Detectors
Chandra and Toueg '96
Optional: Chandra, Hadzilacos and Toueg '95
Leners, Gupta, Aguilera and Walfish '13
04/24 BFT Failure detectors
Clement et al'12
Levin et al'09
Dissecting BFT Consensus
Papers not covered Halpern et al'00
Herlihy and Shavits'99
05/01 Poster Session

Labs and Final Project

All but the final lab are to be done in Elixir a functional language that implements the actor model and must use our emulation layer. Lab 1 and a couple of additional sections will introduce you to the programming environment.

  • Lab 1 is an introduction to the classes programming environment, and is meant to bring you up to speed with the use of recursion and teach you enough Elixir to work on the rest of the projects.
  • Lab 2 and Lab 3 both aim to implement a consensus protocol.

The class diverges for the final project:

  • If you are a PhD student or are interested in independent research you can use a research project you are already working on, or propose a new one for your final project. You will then make a poster (details forthcoming) that we can make available to other students in the class, and submit a short report.
  • For everyone else we will provide a list of open ended labs, and you can work on one of them.

In both cases you need to submit a proposal (by Oct 14), make a poster (details forthcoming) and submit a write up. In both cases the proposal should explain what you are planning on doing, and how you plan to test your work. For the research project you should also provide motivation and preliminary related work.

Final projects should ideally be done in groups of 2, but we can accommodate cases where you want to work alone. Please get in touch with Panda as early as possible.

Late Policy

You have 5 late days that you can use across all labs. Late days incur no penalty, but you are responsible for recording any late days you use in a README file handed in with the lab. Any additional late days will incur a 10% deduction. Any lab submitted more than 5 days late will receive a 0.

Collaboration Policy

You are allowed (and in fact encouraged) to discuss readings, and the reading questions with others (including people who might not be in this class). However, all answers you submit must be written by you and should not be copied from anyone else. Additionally, you must understand your answer, we reserve the right to interview you and quiz you about your answers. Additionally, you must cite all sources (people, websites, papers, etc.) that you consult as a part of your work.

You are allowed to discuss labs with others in the class. You may not however share code with anyone else in class. This means you may not show your code to anyone else, and you may not copy code from anyone else. Additionally, similar to above: (a) you must understand the functioning of all code you submit; and (b) you must cite any sources you consulted while working on the lab. We reserve the right to both talk to you about details of your code and to use automatic tools to detect cases where code is copied.

We will investigate any suspected academic misconduct, and will report it to the department as required by GSAS policies.

A word about citing: as you can see we require you to cite any external sources you use for the class. External sources here include but are not limited to previously published articles, blog posts, Stackoverflow or similar sites, conversations with other people, etc. This policy is not meant to discourage the use of external sources, instead it just codifies a standard academic practice. You should be generous with your citations.

Finally, by taking this class you agree to never post any solutions for the labs publicly.