Hi everyone,
I successfully run a job worker with spring boot on my laptop with VS Code and it get well link with a process of my docker self managed Camunda 8.
But I cannot understand how can I make the job worker autonomous so it can always turn on and listen without me executing the java file locally each time.
I have seen maybe I need to dockerize the spring boot job worker. If so how can I do it, please?
Hi @kamilleB, welcome to the forums! How you package your application with the job worker depends on where you plan on hosting it. Where are you planning on deploying it?
Hi @nathan.loding, I don’t really know what is recommended as I’m not familiar with self-managed concepts, but as Camunda is in docker, I would like to deploy job worker in docker too.
@kamilleB - there isn’t a firm recommendation because it depends on your application and infrastructure. If you want to bundle it with Docker you certain can. There is nothing Camunda specific about doing so, meaning you can follow any tutorial online to create a Dockerized Spring application and run it. You just need to make sure that the Docker networking is configured so that the application can communicate with Camunda.
@nathan.loding Thanks for your reply.
I am currently learning Camunda Self-Managed so that’s why I don’t have specific architecture.
I just took the job worker from camunda github, make it work by linking it to my Camunda host in Docker through configuration.
Now I just wanted to host the job worker somewhere else than my laptop. The problem is that I don’t see anything regarding hosting job worker on Camunda Academy.
If it depends on my application and infrastructure, how to know what application and infrastucture lead to which job worker hosting?
@kamilleB - the job worker sits outside of Camunda within your application infrastructure. It’s not part of Camunda Self Managed; the very same job worker, by only changing the address it’s connecting to, will work with Camunda SaaS. You can deploy and run the job worker anywhere that you can deploy and run Spring applications (private cloud, on-prem, AWS, Azure, Google Cloud, a virtual machine, a VPS, doesn’t matter)!
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.