Should I Turn My Lightweight API Scheduler into an Open-Source Project?
-
Hey everyone,
I recently came across a scenario where I needed a lightweight solution to schedule delayed and recurring callbacks for my API. Specifically, I wanted my API to interact with a service that could trigger a designated endpoint, for example, after 2 hours. Additionally, this service should also be capable of making daily calls to a specific endpoint. I'd also like to run this service in a Docker container as part of my application setup.
In my search for a solution, I explored several options:
* RabbitMQ (no support for recurring tasks)
* Celery and Redis Queue (too heavy for my needs)
* AWS EventBridge and Step Functions (not self-hostable)
* Temporal and Apache Airflow (both heavy and not self-hostable)Eventually, I stumbled upon APScheduler. I ended up building a simple Flask app around it and bundled everything into a Docker container. It’s been working pretty well so far.
I'm surprised there isn't a go-to solution for such a simple use case (or maybe I just haven't found it yet). Are these kinds of requirements unusual? If not, do you think it would be worthwhile to refine what I’ve put together and turn it into an open-source project?