Replacing SAS Products with BPMS (jBPM)
summary
Describes replacing SAS campaign components (RTDM, Viya, ID) with a BPMS-based stack, specifically choosing jBPM as an alternative to provide low-code business logic, high-load execution, and 99.99% availability for x-sell personalization. Covers the architecture of the jBPM solution, reasons for selecting jBPM over other BPMS options, and concrete operational bugs encountered plus the fixes and methods used to achieve required scaling and reliability (including topics like PostgreSQL, metrics, and logs).
AI-written summary · about
chapters (6)
- 0:00Introduction
- 3:11Goals and plan
- 14:14jBPM demo: process creation
- 26:51Load testing results
- 36:28Summary and recommendations
- 40:43Q&A
related talks
01h 00mBPM(N,S, engine) — Do We Need It or Not?
39mOpen Source BPM Comparison
50mProcess-oriented system integration
41mCode your logic, not your infrastructure
28mWhy You Shouldn't Run Business Applications with a Build Tool
24mHow AKKA helped me to build an almost successful cloud for telco services
45mConfiguration management for SaaS/BPaaS solutions
47mTPS first: A Blueprint for Smarter Delivery