Message Passing - Documentation
aeron.io · 299 words · saved by 2 readers
Guide to Aeron Transport, Aeron Archive and Aeron Cluster with samples and usage guidance
Message Passing Distributed systems tend to be built either with synchronous remote procedure calls or using fully asynchronous message passing. The message passing approach offers a number of benefits: systems can be more cleanly composed; it is simpler to construct a system out of loosely coupled components which operate asynchronously than it is to build a system in which every component must be running and responsive for the system to function correctly. message passing based designs can offer location transparency. If the primary component for processing a message fails, then a backup com
saved by
related reading
- Notes on Distributed Systems for Young Bloods – Something Similarsomethingsimilar.com
- A Distributed Systems Reading Listferd.ca
- Building Venice with Apache Helixlinkedin.com
- An Overview of Distributed PostgreSQL... | Crunchy Data Blogcrunchydata.com
- The Distributed Computing Manifesto | All Things Distributedallthingsdistributed.com
- Aeron Transport - The Aeron® Filestheaeronfiles.com
- The Hitchhiker's Guide to Concurrency | Learn You Some Erlang for Great Good!learnyousomeerlang.com
- Distributed systems for fun and profitbook.mixu.net
- GitHub - donnemartin/system-design-primer: Learn how to design large-scale systems. Prep for the system design interview. Includes Anki flashcards.github.com
- Let’s take a crack at understanding distributed consensuspreethikasireddy.com
- Reading 18: Message-Passing and Networkingweb.mit.edu
- metapatterns/IntroductionToSoftwareArchitectureWithActors/Part1/README.md at main · denyspoltorak/metapatterns · GitHubgithub.com