Best of breed: creating your own business automation platform with a microservices architecture
Download as PPTX, PDF0 likes1,224 views
Businesses need agility to innovate and scalability to survive, but monolithic architecture is the enemy of both. The document discusses different business automation architecture patterns including monolith, SOA, iBPMS, and microservices. A microservices-based business automation platform using loosely coupled services with bounded contexts is best for large companies where core processes are a competitive differentiator and they have robust development teams, while a monolithic iBPMS may be better for small-to-mid sized companies with commodity processes and less development resources. The key is deciding which architecture patterns to support based on business needs and isolating monoliths for flexibility and scalability.
Best of breed: creating your own business automation platform with a microservices architecture
- 1. Best of Breed The Case for Building a Business Automation Platform Using BPMS and Microservices Copyright Kemsley Design Ltd., 2019 1
- 2. Businesses need agility (to innovate) Copyright Kemsley Design Ltd., 2019 2
- 3. Businesses need scalability (to survive) Copyright Kemsley Design Ltd., 2019 3
- 4. Monolithic architecture is the enemy of agility and scalability Copyright Kemsley Design Ltd., 2019 4
- 5. Business automation architecture patterns: from monolith to microservices Copyright Kemsley Design Ltd., 2019 5 Monolith SOA iBPMS Microservices
- 6. Microservices definition, in short “Loosely coupled service oriented architecture with bounded contexts” - Adrian Cockcroft, AWS VP cloud architecture strategy (formerly Netflix cloud architect) Copyright Kemsley Design Ltd., 2019 6
- 7. What’s in a business automation platform? Copyright Kemsley Design Ltd., 2019 7 BPMN CMMNDMN
- 8. Who uses a BAP? Technical developers • Orchestration • APIs • Embeddable engines • Devops Citizen developers • Low-code/no-code applications • Prototypes • Models Copyright Kemsley Design Ltd., 2019 8
- 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
- 14. Thanks! Sandy Kemsley sandy@kemsleydesign.com Read my blog at column2.com Find me on Twitter @skemsley Copyright Kemsley Design Ltd., 2019 14