Side-by-Side Process Versioning in Kogito 10.1.0

[Florian Dias]

Hello,

I am currently using Kogito 10.1.0 with Spring Boot and I have a question regarding process versioning.

I have observed that when I deploy a new version of my BPMN (bumped drools:version), all running instances on the previous version become orphaned, the engine filters them out by process_version and returns 404 for any operation on those instances.
I confirmed this behaviour through testing and verified it directly in the process_instances PostgreSQL table.

I am wondering whether Kogito provides a way to run multiple versions of the same process concurrently within a single application, so that in-flight instances on v1 can complete normally while new instances are created on v2, without requiring a migration.

Is there a supported approach for side-by-side versioning in 10.1.0, or is this planned for an upcoming release? 

Thank you for your help.

Best regards,
Florian

[Alex Porcelli]

Florian,

You are probably running this SpringBoot in a distributed mode, not the Compact Architecture mode; Compact Architecture (which is recommended and has been hardened) is not available for  SB on 10.1 - 10.2 (being voted on now) will introduce support for SB.

The simplified way to use Kogito is to version processes like you version public REST APIs: you keep them, but you prefix the endpoints: /v1/,/v2/, etc. Once you have this in place, all original v1 will continue to work with v1. If you don't want to get new instances with v1, you can tweak the code to reject new instances, forcing the use of the latest version.

Hope this helps 

--
You received this message because you are subscribed to the Google Groups "Kogito development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kogito-developm...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/kogito-development/5a5daa92-e2bc-42be-81ad-e348469657fan%40googlegroups.com.