Designing a Concurrent Application | Learn You Some Erlang for Great Good!
Writing a short concurrent application with Erlang primitives: processes, links, monitors, hot code loading and message passing are revisited. A primer before OTP.
Designing a Concurrent Application | Learn You Some Erlang for Great Good! Learn you some Erlang for great good! Home FAQ RSS Code Designing a Concurrent Application All fine and dandy. You understand the concepts, but then again, all we've had since the beginning of the book were toy examples: calculators, trees, Heathrow to London, etc. It's time for something more fun and more educational. We'll write a small application in concurrent Erlang. The application's going to be small and line-based, but still useful and moderately extensible. I'm a somewhat unorganized person. I'm lost with homew
Explore this link on the map →saved by
related reading
- The Hitchhiker's Guide to Concurrency | Learn You Some Erlang for Great Good!learnyousomeerlang.com
- More On Multiprocessing | Learn You Some Erlang for Great Good!learnyousomeerlang.com
- Understanding actor concurrency, Part 1: Actors in Erlang | InfoWorldinfoworld.com
- Elixir, A Little Beyond The Basics - Part 6: processesopenmymind.net
- Building data-centric apps with a reactive relational databaseriffle.systems
- Reading 18: Message-Passing and Networkingweb.mit.edu
- Time, Clocks, and the Ordering of Events in a Distributed Systemlamport.azurewebsites.net
- Simple Explanation for the "Reactor Pattern" with its Applications - Stack Overflowstackoverflow.com
- Server Sent Events are still not production ready after a decade. A lesson for me, a warning for you! - DEV Communitydev.to
- What Server-Sent Events is - and how and when to implement it | Ably Realtimeably.com
- TypeScript Structured Concurrencythecandidstartup.org
- Reading 14: Concurrencyweb.mit.edu