Aeron Cluster - The Aeron Files

Documentation for Aeron based on the underlying files

Aeron Cluster Traditional Service ¶ We all recognise a 'traditional' service that looks something like this: Clients send in messages. The service processes them, builds up some internal state and sends response messages. Any modifications to the state are also written to a database, so if the service crashes, the state isn't lost. This is fine for moderate loads, but the database is a source of contention, so it becomes a bottleneck as the load increases. This kind of architecture will never be able to process 100,000's of messages per second with consistent, 99.999% latency measured in

related reading

• Message Passing - Documentationaeron.io
• Building a BFT JSON CRDTjzhao.xyz
• Students' Guide to Raft :: Jon Gjengsetthesquareplanet.com
• A Distributed Systems Reading Listferd.ca
• 6.5840 Lab 3: Raftpdos.csail.mit.edu
• Raft Consensus Algorithmraft.github.io
• Aeron Transport - The Aeron® Filestheaeronfiles.com
• Let’s take a crack at understanding distributed consensuspreethikasireddy.com
• An Understandable Consensus Algorithmpdos.csail.mit.edu
• Chain Replication for Supporting High Throughput and Availabilitycs.cornell.edu
• The Distributed Computing Manifesto | All Things Distributedallthingsdistributed.com
• GitHub - aphyr/distsys-class: Class materials for a distributed systems lecture seriesgithub.com