Standalone vs Embedded Camunda usage

Camunda 7 Topics Discussion & Questions
1

Hi,

From the point of view of our architectural team, standalone version of camunda suits better for our system but I also want to learn more about pros and cons of standalone version and spring boot embedded version. With standalone version there are some problems that I am struggling in solving like timeout setting problem with http-connector, getting task list with task variables together with one rest call etc. I really want to learn what will I miss I continue with standalone version instead of spring boot embedded version and vice versa. I hope that someone will help me :slight_smile:

Best regards

2

Maybe take a look at this blog post i wrote recently.
It will probably help you make good choices
https://blog.camunda.com/post/2020/04/how-to-choose-the-right-camunda-architecture/

3

Hi Niall,

Thanks for your reply. It was very helpful. We will reevaluate our architectural decisions with respect to your post.
I also want to ask one thing. If we choose to continue with camunda tomcat distribution, what is the best-practice to handle timeout setting problem with http-connector? One solution maybe creating wrapper services handling timeout itself and calling this wrapper service with http-connector, but this will result in more development effort.

4

I would suggest not using http-connectors at all. The External Task pattern is much easier to control, version and manage.

5

Thank you very much, Niall. Your answers are very helpful. We will evaluate this with respect to your suggestions.