Formal specifications for Microservices -
summary
Claims a practical pipeline that turns EventStorming post‑its into executable formal models, translating commands/events/entities into a Petri nets representation, checking liveness and invariants, and producing persisted state and deployment artifacts. Notes TLA+ is useful but too low‑level for teams, so a prototype called the Chime engine is built to validate workshop designs, run automatic checks, and deploy a minimal service in real time — the prototype works for the demos shown.
AI-written summary · about
chapters (7)
- 0:00Introduction and background
- 2:13Formal methods for microservices
- 4:03TLA+ and system behavior
- 6:50Challenges with state machines
- 8:11DDD and formalizing behavior
- 11:07Petri nets as a foundation
- 13:10Chime project and summary
related talks
16mMicroservices Paradise: is it possible to achieve?
54mMicro-Mind Services: Building Complex Behavioral Systems
40mMeasuring Micro-services
55mEvent Storming - how to shorten the distance between IT and Business
39mEvent Design with AsyncAPI, DDD, and AI
28mPractical Microservices, Practical Whiskey
34mA LINGUISTIC APPROACH TO MICROSERVICES
52mTools to Slay the Fire Breathing Monoliths in Your Enterprise - Kelapure, Anderson, Szodfridt