webinar best practices to deal with frequent model changes of long running processes

Best Practices to deal with frequent model changes of long running processes

Webinar, 21st of March 2017

[email protected] | [email protected]

mailto:[email protected]

mailto:[email protected]

Todays speakersBernd Rücker

Co-Founder camunda

@[email protected]

Halil Hancioglu

Senior Consultant@ Opitz Consulting Deutschland

GmbH

@[email protected]

The basic challenge with long running processes

Change

Long running flow

t

Versioning in Camunda

Version: 47Version tag: „1.1.0“Process definition id: 456-271-345

Version: 54Version Tag: „1.2.0“Process definition id: 911-081-577

ProcessInstanceId ProcessDefinitionId

123-456-789 456-271-345

123-456-790 456-271-345

123-456-791 911-081-577

Two basic options in real-life

Run in parallel Migrate to version

A look into our best practices

Agile development

https://www.linkedin.com/pulse/principles-agile-methods-used-business-management-graham-wood

Typicallyshortiterations

Every iterationmightcontainchanges

Andpropablyset live

https://www.linkedin.com/pulse/principles-agile-methods-used-business-management-graham-wood

What do your ops think? If you run hundreds of version in

parallel,calling even multiple different

subprocess versions each,I will kill you.

OK – great. We appreciate clear

messages.So let‘s migrate ☺

Migration

CockpitThe migration plan can be

executed in batch or downloaded as JSON.

Now let‘s getserious!

© OPITZ CONSULTING 2017 Seite 13

Challenges in real-life project

Automate it

Identify Changes

Do not miss any change

Not mixing migration and production code

Challenges of instance migration

Best Practices to deal with frequent model changes

© OPITZ CONSULTING 2017

Rücksprache mit Mktg.


“question” (CC-BY) by Mario Mancuso

Why do we need automation?


möglich


Automate it

Manual effort

1 Process

1 Change per Process

3 Environments

3 manual process migrations


möglich


Automate it

Manual effort

5 Process

2 Change per Process

4 Environments

40 manual process migrations




“CHANGE” (CC-BY-NC-ND) by Martin Deutsch

How do we identify process changes?


möglich, Hauptinh. r. + Sekundärinhalt l.


Identify Changes

For Example 1 Environment

2 Process Changes

Engine detectschanges

Create a new ProcessDefinition version

Deploymentsequence

Semantical version

Camunda ProcessDefinition version

1 v1 v1

2 v2 v2




Identify Changes

And if we re-deploy? Detects only changes to

previous versionon each deployment

Can’t guarantee the semantical uniqueness of a version across multiple environments

Deploymentsequence

Semantical version Camunda ProcessDefinition version

1 v1 v1

2 v2 v2

3 v1 v3

4 v2 v4

v1 v1=


möglich


Identify Changes

Use Camunda VersionTag In Modeler „Properties Panel“

Idea! (CC-BY-ND) by Cristian Carrara




Identify Changes

Independent fromDefinition Version

Semantic NamingConvention necessary E.g. Release & Sprint

Number, Git Hash, GitTag, Maven Version

Change only on relevant commit in Master Branch




How do we ensure that we don't miss any Change?

„IMG_7181“ (CC-BY-NC-ND) by Dora Wu




Don’t miss any Change

For Example 1 Team

2 changes in a process

During 1 Sprint

Start with v1

Change v1 to v2

PDCA (CC-BY) by Jurgen Appelo





Change v2 to v3






Document Change sequence

Changes must be archived

Migrate iterativelyevery change



möglich



What if anotherTeams modifyanother processesin same sprint?

How can wecentralizeall changesduring a sprint?

Team A Invoice Process

Order ProcessTeam B


möglich



Archive changed modelin zip file(local or remote)

Create Migration Plan for each change & add Version Tag

Link each archive andmigration plan in centralchangelog file




How do we ensure that migration is not mixed with productive code?

“Think of a number.....” (CC-BY-NC-ND) by Mister G.C.


möglich


Not mixing migration and production codeP = Production CodeM = Migration Code

Alwaysrunning

Runs only once on Deployor on Rlease




"310/366 - Fortbewegungsmittel / Vehicles" (CC-BY) by Boris Thaser

And More…

Camunda REST API is not delivered and therefore also no

migration API via REST

Execution withoutApplication Server

Administrators intervention only in exceptional cases

Central logging (e.g., no mailing

of log files)

Containerizablewith Docker


möglich


Not mixing migration and production code

Setup a Migration Toolwith Spring Boot

Parallel to the productive code

Dockerized

Automate execution with CI/CD flow

Central Logging

Interacts

or




“Signage 55 speed limit” (CC-BY) by David Lofink



möglich



Process needs further data for new features Process variables must also be modified

Instances could not be migrated only with Camunda Migration API E.g. Modify an Event to a Task

Use Camunda Modification API

“Restrictions” (CC-BY) by Davidlohr Bueso


möglich



Add “return points” temporary as process variable Can be defined

in so-called modification plans

Modify & Migrateto re-runnew addedvalidation(Example)




Demo




Demo

Approve Order

Deploy Archive Local & Remote

Logging in PaperTrail

Start with v1

Change v1 to v2 Extend to reopen

rejected orders

Notify only when reopened




Demo

Change v2 to v3 Extend to validate

incoming orders

© OPITZ CONSULTING 2017 Seite 38

Conclusion

Extendable Process Engine Flexible & well documented APIs

Base for continuous improvement Automated Migration

Benefit You don’t have to version the Sourcecode, because you’re

always on the latest process definition version

@Camunda Extend Migration API and Modification API with

VersionTag and ProcessDefinitionKey





That’s it….Many Thanks!

Applause (CC-BY-NC-ND) by Kevin Labianco

© OPITZ CONSULTING 2017 Seite 40Best Practices to deal with frequent model changes

Q & A

You have Questions…

…We have Answers


möglich


Todays speakers

Bernd Rücker

Co-Founder camunda

@[email protected] Hancioglu

Senior Consultant@ Opitz Consulting Deutschland

GmbH

@[email protected]

webinar best practices to deal with frequent model changes of long running processes

Technology