5 tips on how to deliver software effectively by aligning coding and business best practices
summary
Claims that making business rules executable removes the last wall between business and devs, shown by five concrete practices: externalize rules, use ubiquitous language, decouple logic, monitor business KPIs, and package specs with CI/CD. Live demo runs a cloud‑native rescue app built with BPMN/DMN executable specs, jBPM + Kafka orchestration, Spring Boot, Vert.x, Keycloak, Infinispan, Prometheus/Grafana and OpenShift. Demo starts with 210 incidents and 9 responders, scales to 34 responders and reports ~3,000 rescues across 2,000+ process instances; code and deployable repos are available.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 4:27What is software creation
- 7:23What do customers want
- 8:08Tech trends
- 10:40Adopt an effective culture
- 14:04Ubiquitous language usage
- 19:40Decouple business logic
- 22:28Data that matters
- 23:58No silver bullet solution
- 25:50Demo
- 39:28Key takeaways
- 41:01Questions
- 48:28Emergency Response Demo
- 49:43Runtimes
- 50:16Advice
- 51:06Business Automation
- 52:33Outro
related talks
51m5 Tips to Make Your Java Apps More Awesome!
18mDesign Patterns For Efficient DevOps Processes
24mBizDevOps
22mLeading software teams with context (visibility)
44mSurviving the hyperautomation low code bubble
36mDeveloper Experience : From Hype to Reality
45mPro-Code vs Low-Code in Microservice Orchestration
51mImproving Software Flow