I schedule them so I can run a recurring task every day.
Examples:
1. Crawl a website, and store the data to a database - update every few hours.
2. Check a website for changes.
3. Process log data, and save it to another location.
Docker may be overkill for some of these, but it provides a simple way to launch a new task in a container with all dependencies installed. The overhead seems to be relatively small for starting a new container, so it's worth the overhead vs. configuring a machine to run the container.
Seams reasonable. I think it also can help to not have zombie processes after cronjobs. Well, then we'll definitely consider having scheduling. Thanks mate!
Examples:
1. Crawl a website, and store the data to a database - update every few hours.
2. Check a website for changes.
3. Process log data, and save it to another location.
Docker may be overkill for some of these, but it provides a simple way to launch a new task in a container with all dependencies installed. The overhead seems to be relatively small for starting a new container, so it's worth the overhead vs. configuring a machine to run the container.