java.util.concurrent for Distributed Coordination
summary
Explains how Hazelcast implements distributed versions of java.util.concurrent primitives (locks, semaphores and similar) by building them on the Raft consensus algorithm. Shows code examples and discusses using these Java concurrency APIs for coordination tasks (leader election, locking, synchronized actions) in distributed environments that include partial failures.
AI-written summary · about
chapters (5)
- 0:00Start
- 3:08Distributed Coordination Leader election Synchronization Group membership Configuration and metadata management
- 11:55Concurrency Nondeterminism Partial failures
- 19:02Replicated State Machines A leader is elected among the nodes. The leader replicates ops to the followers All nodes run the ops in the same order
- 44:20Recap Avoid writing your own implementations for coordination High-level APIs minimise guesswork and development effort java.util.concurrent.. FTW Operational simplicity matters. Dynamic clustering
related talks
45mjava.util.concurrent for Distributed Coordination
41mWhat can go wrong with the distributed system - the Hazelcast exp...
46mWhat can go wrong in a distributed system - experience from...
48mHow to build distributed concurrency primitives
30mDistributed Computing with Hazelcast
59mDistributed applications using Hazelcast
55mHazelcast - Hitchhiker’s Guide. Grzegorz Piwowarek. Java Fest 2020 Online
51mDo Not Reimplement Distributed Consensus Algorithms
