otplike – Erlang/OTP processes and behaviours for Clojure
summary
A small Clojure library built on core.async and core.match implements key Erlang/OTP patterns: lightweight processes (spawn, spawn-link), process linking and monitors, trap-exit semantics, a generic-server API with handle-call/initialise, and supervisors with one_for_one / one_for_all / rest_for_one restart policies. otplike runs in production (automotive and engineering projects, a Berlin fintech proof), ships several hundred tests, and plans ClojureScript support plus a richer process registry similar to gproc.
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:35core.async recap
- 1:53core.async pitfalls
- 3:53Erlang/OTP recap
- 7:28otplike / process - Example
- 9:54otplike / process - Linking
- 13:00otplike/process. Trap Exit
- 15:14otplike / gen server introduction
- 16:57otplike / gen server behaviour
- 18:02otplike / gen server example
- 26:56otplike / Supervision tree - Example
- 28:53Conclusion
- 33:46Links and Information
related talks
32mOTP Process Abstractions with proc lib
42mConcurrency Oriented Software
01h 15mEffective Programs - 10 Years of Clojure
51mThe Erlang VM or How I Started Loving Parallel Progamming
36mKlor: Choreographic Programming in Clojure
43mConcurrency Oriented Programming in a Modern World
37mOnyx: Distributed Computing for Clojure
52mConcurrency Oriented Programming in a Modern World