The Circle of Lifecycle Events
summary
Lists concrete rules and tradeoffs for handling create/update/delete: prefer callbacks modify only their model, use ActiveRecord DB transactions for all‑or‑nothing multi‑model changes, and extract complex flows into service objects or pure procedures for versioning and testability. For cross‑app work prefer publish/subscribe (RabbitMQ; consider Kafka) to decouple systems, noting MX runs messaging at trillions of transactions and that distributed setups still risk orphans, race conditions, and a distributed monolith.
AI-written summary · about
chapters (7)
- 0:00Start
- 1:22Whats a lifecycle events?
- 3:21Why a talk on lifecycle events?
- 12:48Callbacks pro tip
- 13:21How your application views your models
- 24:20Versioning?
- 34:36Review
related talks
48mThe Circle Of Lifecycle Events
52mSo You Want to Build An Event Driven System?
25mNo Return: Moving beyond transactions in software and in life
51mComplex Event Flows in Distributed Systems
56mEvents on the outside, on the inside and at the core
47mComplex event flows in distributed systems
52mSo You Want to Build An Event Driven System?
50mMoving away from CRUD: DDD + CQRS