If you want to implement a more distributed architecture. Take a look at this post for more details.
You can also see this video to find out how it works.
The difference between the two JS clients is that @nikku’s one was made first and existed before we created a camunda supported one. So best to use the one form Camunda.
Workit use Typescript and this is a big plus (at least for us) during maintenance and developments. Besides, instead of depending directly from a Camunda client, this project provides an abstraction layer. This way it’s easier to change the client or to make your own.
Behind the scene, Workit use https://github.com/camunda/camunda-external-task-client-js by default for Camunda BPM engine.
With Workit you can experiment and choose the Camunda platform you want without rewritting the business logic. It’s also built-in with OpenTelemetry.
Hi @Olivier_Albertini thanks for the detailed explanation. Does this provide an abstraction over the engine REST API too, or just helps to develop the worker? Maybe it will be more apparent if I try both out!