-
Notifications
You must be signed in to change notification settings - Fork 10
###1. Why do we really need an another Java scheduler? When we were developing a Audit4j, we had requirements to schedule jobs and it should contains Cron featuring scheduling. We thought about Quartz and it is not lightweight enough to integrate with audit4j framework. Then we went for the Cron4j then it causes the licensing issues. The biggest issue we had is, we wanted a managed thread provider (JSR-236 API) coupled with application container.
###2. Is it really re-inventing the wheel? We thought of developing new scheduler for Audit4j without writing codes from the sketch and without any licensing violations. After several surveys, Spring Scheduling implementations are adopted as a base. Most implementations are added as it is and some classes slightly modified. A thin wrapper and some additional implementations are added for better API experiences.
###3. When do I use Clockwise? If you are using Spring, we encourage to use Spring scheduling. If you want lightweight scheduling library, Clockwise will perfectly fit for you.