Pro-Code vs Low-Code in Microservice Orchestration
summary
Shows why orchestration belongs to a stateful engine using BPMN executable diagrams with parallel gateways, boundary error events and a timer event; demos a real Java Spring Boot worker called Spring Boot "Who's 50" worker that registers with the engine, runs against a deployed process version, and returns an age variable; contrasts a vendor-hosted SendGrid connector low‑code flow (fast, reusable, prone to vendor lock‑in and limited testing) with pro‑code control, and illustrates a hybrid JSON panel that exposes inputs while hiding correlation keys.
AI-written summary · about
chapters (10)
- 0:00Introduction and audience poll
- 0:47Microservice orchestration basics
- 5:20BPMN process orchestration demo
- 11:24Pro-code vs low-code integration
- 19:54Pro-code integration demo
- 24:15Low-code integration demo
- 30:33Pro-code vs low-code comparison
- 40:51Hybrid integration model
- 42:16When to use each approach
- 44:21Q&A session
related talks
40mDecoupling your Springboot microservices live coded using workflow automation
52mLoosely or lousily coupled? Understanding communication patterns
33mAutomating Processes in Modern Architectures
49mThe Benefits of Orchestration in Distributed Systems
44mSurviving the hyperautomation low code bubble
01h 13mOrchestration vs. Choreography in Microservices
39mWhy You Should Look Into Low Code
40mCommunication between (micro-)services