Playtrip: a CQRS/ES Architecture in Erlang
summary
A mobile app backend was built in Erlang using a CQRS (Command-Query Responsibility Segregation) and Event Sourcing architecture. The talk explains why this approach worked well and how CQRS/ES leverages Erlang-specific features—the Actor Model, lightweight processes, and built-in distributed capabilities—to implement the solution.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 2:15Playtrip project overview
- 8:43Erlang origins and features
- 13:46Elixir introduction and differences
- 19:20BEAM VM and processes
- 24:22Actor model and concurrency
- 27:36Moore’s law and Erlang need
- 29:45CQRS and Event Sourcing basics
- 32:36Playtrip CQRS/ES architecture
- 36:31Practical CQRS/ES in Elixir
- 43:27Aggregates projections supervision
- 46:36Erlang and Elixir resources
- 48:30Q&A
related talks
43mFunctional and Reactive Event Sourced Applications
45mThe Practical Road towards CQRS and Event Sourcing
56mDeveloping Event-driven Microservices w/Event Sourcing and CQRS
47mCQRS / ES: Our Heuristics After Several Years in Production
54mTeaching Your Team CQRS/ES 2.0
47mCQRS and Event Sourcing on Steroids: Lessons Learned with Spring & Axon
40m7 Reasons why your microservices should use Event Sourcing & CQRS
35mDiving into Erlang is a one-way ticket
