Ecommended way to manage scheduled tasks in larger Lucee applications?

dev support
1

Hi everyone,

I’m working on a Lucee-based application with multiple scheduled tasks running for cache cleanup, API syncs, and background processing.

I wanted to ask how others are organizing scheduled tasks in larger projects. Are you keeping everything inside Lucee scheduled tasks, or moving some jobs to external workers/services for better monitoring and reliability?

Curious to hear what has worked best in production environments.

2

I’d highly recommend the new Quartz Scheduler Extension

3

I’ve got a separate tasks server running lucee for scheduled tasks and a web-based tasks application. This server also runs a commandbox CLI app that I wrote that uses commandbox task runners and waits for incoming tasks from a rabbitmq server. This creates separation between my production web servers and tasks that need to be run at an interval, and also tasks that need to be run on demand (via the CLI app), like processing a media file, or indexing a piece of data.

I’m using the built in scheduled tasks feature in the Lucee admin and that works well because I there are some Lucee functions that allow me to access those tasks - I use list, pause, and resume - from my tasks web app so I can pause all, or resume all with an api call or by clicking a button. This is helpful when switching between blue/green deployments when you want to take it offline and drain the work being done.