Driven Design: Business Transaction && Consistency
summary
Explains the concept of a business use-case and how to model it, then defines a business transaction and contrasts it with system consistency. Shows how to identify a business transaction inside a use-case and plan consistency for other system elements, examines how transactions and consistency are implemented in their PHP monolith, and briefly discusses using sagas to coordinate critical parts of the system.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 3:20Talk goals and structure
- 5:30Business transaction concept
- 10:29Project architecture and implementation
- 14:24Data consistency problem
- 20:30Consistency types
- 24:45Event-driven solution
- 27:56Long-running transactions
- 35:24Eventual consistency and sagas
- 44:41Summary and recommendations
- 47:38Q&A
related talks
50mThe Anatomy of Business Conditions
47mDomain-Driven Design: A Complete Example
55mDomain-Driven Design: back to the roots
11mUse Case Driven Development
01h 07mThe courage to business logic - Business Driven Architecture
50mMoving away from CRUD: DDD + CQRS
44mStrategic Domain-Driven Design for dummies
51mWorking with Database Transactions the Right Way