Untangling the API Spaghetti With BPMN Diagrams
summary
Argues that BPMN diagrams become the executable definition that untangles microservice sprawl, using a concrete key-value store with history and translation example where set/get flows spawn parallel consumers and an expiring-key timer moved to orchestration to avoid duplicated timers and data-coupling. Replaces ad hoc Kafka pipelines with a BPMN control bus that supports waits, forks, joins and conditionals; diagrams compile to XML and run on orchestration engines so the diagram is the live blueprint, not stale documentation.
AI-written summary · about
chapters (7)
- 0:00Welcome
- 1:10Monoliths to microservices
- 4:45Adding features in fragments
- 8:57Why fragments are hard
- 12:48Modeling workflows
- 16:34What is BPMN and how it solves the problem
- 18:40BPMN benefits
related talks
51mBe proactive about state in a reactive system
40mDecoupling your Springboot microservices live coded using workflow automation
21mObject Centric Processes: Combining Process Modelling with OOP
59mHustle and Flow
58mWelcome to the (state) machine
51mDiagrams as code 2.0
28mThe Hidden Unity of APIs and Event Streams
49mEvent Driven Collaboration