Can a process application subscribe workers to two different Camunda engines, either self-managed or SaaS?
The use case is this: I have a process application connected to a Camunda 8.5 Self Managed. This application deals with multiple long running processes (6 month-long). We have plans to move to SaaS and we would like to have the application to be able to continue processing process instances on 8.5 until they drain out, and at the same time start and work process instances from SaaS. Is this possible?
Hey @pedro.arroyo - yes you can, and it’s one pattern we recommend for migrations. You do need two different task worker definitions, and you probably can’t use the Spring annotations for both (because it will assume one client implementation). But you can manually register job workers with an alternate client configured to point to the other cluster, and then you can point both job workers to same logic in your code.
These docs discuss the concept a bit. Though it is focused on C7->C8 migration, the same concepts apply.
Hope that helps!
1 Like
This is great info @nathan.loding I’ll dive into this and come back if I have more questions 