BPM for SOA+ESB+API and cloud

#BPM for #SOA+#ESB+#API and #cloud (#PaaS and #SaaS)

A. Samarin

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

http://improving-bpm-systems.blogspot.com/2013/04/bpm-for-developers-improve-agility-of.html

http://improving-bpm-systems.blogspot.com/2013/04/addressing-security-concerns-through-bpm.html

http://improving-bpm-systems.blogspot.com/2013/04/addressing-security-concerns-through-bpm.html

https://www.linkedin.com/pulse/article/20140427193910-4749526-ideas-for-bpmshift-delenda-est-vendor-centric-bpm-how-to-modernise-a-legacy-erp

https://www.linkedin.com/redirect?url=https://www.linkedin.com/pulse/article/20140812140157-4749526--bpm-for-software-architects-from-monolith-applications-to-explicit-and-executable-coordination-of-microservices-architecture&urlhash=gHaH&_t=tracking_disc

Service

Legacy application

In-houseApplication

flow of controlflow of data mixed flow

No clouds, everything is in-house

Service

Legacy application

AppInternet

In-houseApplication

SaaS in Cloud

API


Cloud services and external client

Service

Legacy application

App

SOA+ESB+API

APIAPI

Container Container

Internet

In-houseApplication

SaaS in Cloud

API


Put order in-house by SOA+ESB+API

Service

Legacy application

App

SOA+ESB+API

APIAPI

Container Container

Internet

In-houseApplication

API

Container

Compoundservice

SaaS in Cloud

API


Use compound services to simplify applications

Service

Legacy application

BPMSmanagement as a service

SOA+ESB+API

APIAPIAPI

Container ContainerBPMS container

Process instance as a service

API

BPMS container

Human activity

as aservice

API

BPMS container

Internet

In-houseProcess-centric solution (internal, B2E, B2B)

API

Container

Compoundservice

App

Application

SaaS in Cloud


SaaS in Cloud

API

Adding process-centric solutions

ServiceProcess

instance as a compound

service Legacy

application

App


Human activity

as aservice

SOA+ESB+API

APIAPIAPIAPIAPI

Container ContainerBPMS containerBPMS containerBPMS container

Internet

In-houseProcess-centric solution

(internal, B2C, B2B)

API

Container

Compoundservice


SaaS in Cloud

API

Replacing compound services by mini-processes

ServiceProcess


service Legacy

application

App


Human activity

as aservice

SOA+ESB+API

APIAPIAPIAPIAPI

Container ContainerBPMS containerBPMS containerBPMS container

Internet

In-houseProcess-centric solution


API SaaS in Cloud


More order in-house

ServiceProcess


service Legacy

application

App


SOA+ESB+API

APIAPIAPIAPI

Container ContainerBPMS containerBPMS container

Internet

In-house

ServiceProcess instance as a service


Human activity

as aservice

SOA+ESB+API

APIAPIAPIAPI

ContainerBPMS containerBPMS containerBPMS container

PaaS in CloudProcess-centric solution


API SaaS in Cloud


Use BPM PaaS product but keep the flow of data in-house

ServiceProcess


service Legacy

application

App


SOA+ESB+API

APIAPIAPIAPI

Container ContainerBPMS containerBPMS container

Internet

In-house



Human activity

as aservice

SOA+ESB+API

APIAPIAPIAPI




API SaaS in Cloud


App

Redirect all external applications to PaaS product

Process instance as a

compound service

Legacy application

App


SOA+ESB+API

APIAPIAPI

ContainerBPMS containerBPMS container

Internet

In-house



Human activity

as aservice

SOA+ESB+API

APIAPIAPIAPI




API SaaS in Cloud


App

Moving more services to PaaS product

Legacy application

SOA+ESB+API

API

Container

Internet

In-house



Human activity

as aservice

SOA+ESB+API

APIAPIAPIAPI


Process-centric solution (internal, B2C, B2B)

App

PaaS in Cloud


API SaaS in Cloud

Legacy will be SaaS in cloud at one time

SaaS in CloudOTS

products

Internet

In-house



Human activity

as aservice

SOA+ESB+API

APIAPIAPIAPI



App

PaaS in Cloud


API SaaS in Cloud

Nice and clean in-house

API

SaaS in CloudOTS

products

Internet

In-house



Human activity

as aservice

SOA+ESB+API

APIAPIAPIAPI



App

PaaS in Cloud


API SaaS in Cloud

Some COTS products become also PaaS products

API

Service

API

ContainerAnother PaaS in Cloud

Service

API

Container

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)

16© A. Samarin 2014 #BPM for #SOA+#ESB+#API and #cloud (#PaaS and #SaaS) v2

• 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)


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


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-services6. Use interpretive programming languages for micro-

services7. Think about integration and automation platform

Again


• “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 servicesimplement the application back end. Together these apps and services support a particular business domain.”


20

Apps and services view – which initiated 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

• QUESTIONS?

• Personal website: http://www.samarin.biz

• Blog http://improving-bpm-systems.blogspot.com

• LinkedIn: http://www.linkedin.com/in/alexandersamarin

• E-mail: [email protected]

• Twitter: @samarin

• Mobile: +41 76 573 40 61

• Book: www.samarin.biz/book

Thanks

21© A. Samarin 2014

http://www.samarin.biz/

http://improving-bpm-systems.blogspot.com/

http://www.linkedin.com/in/alexandersamarin

mailto:[email protected]

http://www.twitter.com/samarin

http://www.samarin.biz/book

Date post:	13-Jul-2015
Category:	Technology
Upload:	alexander-samarin
View:	1,680 times
Download:	2 times

BPM for SOA+ESB+API and cloud

Technology