Skip to Main Content
Cumulocity IoT Feedback Portal
Status Likely to support/improve
Created by Tristan Bastian
Created on Dec 20, 2021

Scheduled microservice startups

Customers have microservices, that actually just run a e.g. a daily or hourly job that might take not more than e.g. 5 minutes or so. The rest of the day or hour this microservice is basically just idleing and taking up some c8y ressources and producing costs for the customer for doing nothing..

For services like these it would be great if we would support something like a cron job for microservice startups. This would allow the customer to save costs and ressources.

This configurable cron job would start a microservice instance if e.g. currently none is running. And if the microservice exits with return code 0 after it finished its job, the microservice instance is not going to be restarted as the return code is handled like a successfull shutdown.

  • Attach files
  • Admin
    Jane Porter
    Mar 16, 2023

    Hi Tristan,

    Thank you for raising this Idea, we will assess it and look to include it in our backlog once the work on the containerisation and move to managed Kubernetes is complete.

    Thanks, Jane.