BPM(N,S, engine) — Do We Need It or Not?
summary
The talk examines Business Process Management tools—BPM, BPMN, BPM-S, and engines—in the context of enterprise Java development, using Tinkoff as a case study. It discusses when these technologies help or create technical debt, outlines good and bad practices for automating business processes, and demonstrates practical ways to speed up process automation now.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 1:24What is BPM and BPMN
- 3:51BPMN as notation and standard
- 7:02BPMN in business practice
- 9:31Business process example
- 12:23State change challenges
- 14:49Petri nets and their role
- 16:37BPM history at Tinkoff
- 19:49Ditching monolithic BPM
- 21:56Custom state-based solution
- 24:01Current process architecture
- 27:19BPMN notation symbols
- 28:24Complex BPMN logic example
- 31:21Developer onboarding threshold
- 34:10BPMN as career tool
- 35:56BPMN misconceptions
- 39:26When BPMN is truly needed
- 41:54BPMN change linearity
- 43:00Camunda technical aspects
- 47:14Camunda external workers
- 50:46Camunda database issues
- 53:20Conclusion and recommendations
related talks
47mReplacing SAS Products with BPMS (jBPM)
39mOpen Source BPM Comparison
41mCode your logic, not your infrastructure
50mProcess-oriented system integration
28mWhy You Shouldn't Run Business Applications with a Build Tool
20mSeamless Business Processes: How to Achieve Excellent Digitalization with Tools
40mCombining Stream and Batch Processes in Camunda BPM
12mStreamlining Business Workflows with Kogito: Automation Made Easy