Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

BPM for SOA+ESB+API and cloud

3,671 views

Published on

#BPM #SOA #ESB #API #PaaS # SaaS #cloud together

Published in: Technology
  • Be the first to comment

  • Be the first to like this

BPM for SOA+ESB+API and cloud

  1. 1. #BPM for #SOA+#ESB+#API and #cloud (#PaaS and #SaaS) A. Samarin
  2. 2. 1. #bpm for developers: improve #agility of implementations http://improving-bpm-systems.blogspot.com/2013/04/bpm-for-developers- improve-agility-of.html 2. Addressing #security concerns through #BPM at http://improving-bpm-systems.blogspot.com/2013/04/addressing-security- concerns-through-bpm.html 3. https://www.linkedin.com/pulse/article/20140427193910-4749526- ideas-for-bpmshift-delenda-est-vendor-centric-bpm-how-to-modernise- a-legacy-erp 4. https://www.linkedin.com/pulse/article/20140812140157-4749526-- bpm-for-software-architects-from-monolith-applications-to-explicit-and- executable-coordination-of-microservices-architecture © A. Samarin 2014 #BPM for #SOA+#ESB+#API and #cloud (#PaaS and #SaaS) v2 2 Related articles
  3. 3. flow of data flow of control mixed flow Application In-house Service Legacy application No clouds, everything is in-house
  4. 4. SaaS in Cloud Service flow of data flow of control mixed flow Legacy application App Internet API Cloud services and external client Application In-house
  5. 5. SaaS in Cloud API flow of data flow of control mixed flow API API Service Legacy application App SOA+ESB+API Container Container Internet Put order in-house by SOA+ESB+API Application In-house
  6. 6. API API Service Legacy application App SOA+ESB+API Container Container Internet SaaS in Cloud API Application In-house API Container Compound service flow of data flow of control mixed flow Use compound services to simplify applications
  7. 7. API API API BPMS container Container Container Service Legacy application SOA+ESB+API BPMS management as a service API BPMS container Process instance as a service API BPMS container Human activity as a service Internet In-house Process-centric solution (internal, B2E, B2B) API Container Compound service App Application SaaS in Cloud flow of data flow of control mixed flow SaaS in Cloud API Adding process-centric solutions
  8. 8. API API API API API Service Process instance as a compound service Legacy application App BPMS management as a service Human activity as a service SOA+ESB+API BPMS container BPMS container BPMS container Container Container Internet Process-centric solution (internal, B2C, B2B) In-house API Container Compound service flow of data flow of control mixed flow SaaS in Cloud API Replacing compound services by mini-processes
  9. 9. API API API API API Service Process instance as a compound service Legacy application App BPMS management as a service Human activity as a service SOA+ESB+API BPMS container BPMS container BPMS container Container Container Internet Process-centric solution (internal, B2C, B2B) In-house API SaaS in Cloud flow of data flow of control mixed flow More order in-house
  10. 10. PaaS in Cloud Process-centric solution (internal, B2C, B2B) API API API API BPMS API API API API BPMS container BPMS container Container Container Service Process instance as a compound service Legacy application App SOA+ESB+API BPMS management as a service Internet In-house Process Service instance as management a service as a service Human activity as a service SOA+ESB+API BPMS container BPMS container BPMS container Container API SaaS in Cloud flow of data flow of control mixed flow Use BPM PaaS product but keep the flow of data in-house
  11. 11. PaaS in Cloud Process-centric solution (internal, B2C, B2B) API API API API BPMS API API API API BPMS container BPMS container Container Container Service Process instance as a compound service Legacy application App SOA+ESB+API BPMS management as a service Internet In-house Process Service instance as management a service as a service Human activity as a service SOA+ESB+API BPMS container BPMS container BPMS container Container API SaaS in Cloud flow of data flow of control mixed flow App Redirect all external applications to PaaS product
  12. 12. PaaS in Cloud Process-centric solution (internal, B2C, B2B) API API API API BPMS API API API BPMS container BPMS container Container Process instance as a compound service Legacy application App SOA+ESB+API BPMS management as a service Internet In-house Process Service instance as management a service as a service Human activity as a service SOA+ESB+API BPMS container BPMS container BPMS container Container API SaaS in Cloud flow of data flow of control mixed flow App Moving more services to PaaS product
  13. 13. flow of data flow of control mixed flow Legacy Process-centric solution (internal, B2C, B2B) API API API API application SOA+ESB+API API Container Internet Legacy will be SaaS in cloud at one time In-house BPMS Process Service instance as management a service as a service Human activity as a service SOA+ESB+API BPMS container BPMS container BPMS container Container App PaaS in Cloud API SaaS in Cloud
  14. 14. Nice and clean in-house SaaS in Cloud OTS products Internet In-house flow of data flow of control mixed flow Process-centric solution (internal, B2C, B2B) API API API API BPMS Process Service instance as management a service as a service Human activity as a service SOA+ESB+API BPMS container BPMS container BPMS container Container App PaaS in Cloud API SaaS in Cloud API
  15. 15. Some COTS products become also PaaS products SaaS in Cloud OTS products Internet In-house flow of data flow of control mixed flow Process-centric solution (internal, B2C, B2B) API API API API BPMS Process Service instance as management a service as a service Human activity as a service SOA+ESB+API BPMS container BPMS container BPMS container Container App PaaS in Cloud API SaaS in Cloud API API API Container Container Another PaaS Service in Cloud Service
  16. 16. Advantages of cloud (1) • SaaS is good for OTS products (system of records) – not be changed by us (i.e. customised) – protect well their data • BPM PaaS product is necessary for integration and provisioning of micro-services (system of differentiation) – without customising the platform (itself – with the use of only non-exotic features – core for a corporate integration and automation platform or business execution platform – quick deployment, versioning, scaling out (for peak load periods) • Collaboration with a BPM PaaS product vendor to improve our services and solutions (system of innovations) © A. Samarin 2014 #BPM for #SOA+#ESB+#API and #cloud (#PaaS and 16 #SaaS) v2
  17. 17. • Several SaaS and PaaS products may be used simultaneously • But, keep an eye on them – changing of SaaS or PaaS product should be easy • Potentially, all currently installed in-house products will be in cloud • Financial effect should be estimated if there is “pay-as-you- go” option 17 Advantages of cloud (2) © A. Samarin 2014 #BPM for #SOA+#ESB+#API and #cloud (#PaaS and #SaaS) v2
  18. 18. How to move from in-house to cloud • Step-by-step • Total (or ruthless) digitalisation • Different business domains may have different pace • Keep everyone happy concerning their “touch-points” • Especially security issues – making the flow of data explicit to take an informed solution • Make everything explicit • Maintain discipline, make design simple, strive for balance, and keep is stable • Architecture, architecture, architecture © A. Samarin 2014 #BPM for #SOA+#ESB+#API and #cloud (#PaaS and 18 #SaaS) v2
  19. 19. Again 1. Think about micro-services (atomic and compound) 2. Know how to implement your-business-specific-common functionality as micro-services 3. Know not to implement automation for your-unique-business- processes-specific as composite (compound) micro-services with the use of micro-services from the item #2 4. Know how to implement your-unique-business-processes as composite (compound) micro-services with the use of the item #3 5. Use DSLs for compound micro-services 6. Use interpretive programming languages for micro-services 7. Think about integration and automation platform © A. Samarin 2014 #BPM for #SOA+#ESB+#API and #cloud (#PaaS and 19 #SaaS) v2
  20. 20. Apps and services view – which initiated • “A relevant application architecture trend is the shift away from monolithic and tightly coupled n-tier applications to decomposed applications. A modern application is a functional ecosystem comprising a loose association of apps and services. Apps implement the application front end, and services implement the application back end. Together these apps and services support a particular business domain.” © A. Samarin 2014 #BPM for #SOA+#ESB+#API and #cloud (#PaaS and #SaaS) v2 20 this presentation 1. Business process-specific functionality (to be used only in a particular process) 2. Business domain-specific functionality (common within a particular domain and to be used by services from the item 1) 3. Cross-domain functionality (to be used by services from the item 2) # compound vs atomic micro-service or service OTS vs in-house 1 explicit compound micro-service in-house 2 explicit compound or atomic any any 3 implicit compound or atomic any OTS
  21. 21. • QUESTIONS? • Personal website: http://www.samarin.biz • Blog http://improving-bpm-systems.blogspot.com • LinkedIn: http://www.linkedin.com/in/alexandersamarin • E-mail: alexandre.samarine@gmail.com • Twitter: @samarin • Mobile: +41 76 573 40 61 • Book: www.samarin.biz/book Thanks © A. Samarin 2014 21

×