Presentation: What Came First: The Ordering of Events in Systems
Abstract
Your favorite distributed system and the concurrent program you wrote last week are built on the same foundational principle for ordering events across the system. This talk will explore the beautifully simple happens-before principle that lies behind these complex systems. We will delve into how happens-before is tracked in a distributed database like Riak, and how it’s implicitly maintained by the concurrency primitives provided in languages like Go. We will touch upon other sophisticated uses of happens-before like consensus protocols and data race detection.
Similar Talks
Psychologically Safe Process Evolution in a Flat Structure
Director of Software Development @Hunter_Ind
Christopher Lucian
Not Sold Yet, GraphQL: A Humble Tale From Skeptic to Enthusiast
Software Engineer @Netflix
Garrett Heinlen
Let's talk locks!
Software Engineer @Samsara
Kavya Joshi
PID Loops and the Art of Keeping Systems Stable
Senior Principal Engineer @awscloud
Colm MacCárthaigh
How Did Things Go Right? Learning More From Incidents
Site Reliability Engineering @Netflix
Ryan Kitchens
Graceful Degradation as a Feature
Director of Product @GremlinInc
Lorne Kligerman
A Dive Into Streams @LinkedIn With Brooklin
Data Infrastructure @LinkedIn
Celia Kung
Liberating Structures @CapitalOne
Agile Coach, Engineering @CapitalOne
Greg Myers
Making 'npm install' Safe
Software Engineer @agoric