Building Actor Systems in Rust
summary
Rust implementation of an actor library called rabble underpins a coordination KV store named Herot and uses view stamped replication to run entirely in memory without disk logs. The runtime is a single-threaded FIFO executor with lightweight reactive processes plus heavyweight service threads, deterministic testing via property-based generators and replayable message schedules, and a reversible debugger prototype. It currently works for tens of nodes (full‑mesh), lacks a write‑ahead log and needs a partial‑membership plan to scale to thousands.
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:33Haret Protocol
- 1:20Haret Backend
- 4:59Rabble
- 8:00Naming
- 8:31Messages
- 10:36Envelopes
- 11:27Processes
- 13:29Echo Server
- 16:49Property Based Testing
- 18:19Test Scheduling
- 19:37Test Assertions
- 20:35Failing Tests
- 20:53Debugging
- 22:25Cluster Server
- 22:59Membership
- 23:55Services
- 26:13Takeaway
related talks
32mDistributed Actor System in Rust
21m"Actors and Factories in Rust"
29mRust & Rig: Building for Stability in a Rapidly Changing AI Landscape
15mTowards Safe HPC: Productivity and Performance via Rust Interfaces for a Distribu...
36mTaking Rust to Production: Lessons Learned From the Habitat Project
40mWhy Rust?
28mRust and Scala, Sitting in a Tree….
22mUsing Rust in Metal Fabrication