9. Monolithic BPMS as a BAP
• Small to mid-sized company
or department
• Commodity core processes in
COTS system (e.g., ERP)
• Not “in the software business”
Copyright Kemsley Design Ltd., 2019 9
10. Who wants you to use a monolithic BAP?
“An iBPMS is a type of
high-productivity
(low-code/no-code)
application development
platform.”
Gartner MQ for iBPMS, 2019
Copyright Kemsley Design Ltd., 2019 10
11. Multi-vendor microservices BAP
• Large company or tech startup
• Core processes are a
competitive differentiator
• Robust development team
Copyright Kemsley Design Ltd., 2019 11
12. Monolithic iBPMS versus microservices BAP:
points to consider
•Application architecture
•Development tooling
•Extensibility and flexibility
•Scalability
•Cost (tools and scaling)
•Lock-in
Copyright Kemsley Design Ltd., 2019 12
13. Getting to the BAP that you need
•Decide which application architecture
patterns to support
•Identify and isolate the monoliths
•Don’t get attached to a specific service
•Expect unexpected scalability
Copyright Kemsley Design Ltd., 2019 13