currently, the job addon is based in REST to communicate with job-service, so to create, get/ delete a job it does HTTP calls, and to receive a callback to trigger the timer node in the runtime, it exposes an endpoint to receive a request from job-service.

The idea is to do the same communication-based in messaging through kafka.

Some scenarios should be considered, like how to handle failures, timeouts that with HTTP call are synchronous.