⚗️ Proposal for checking service status in the `dynamic-scheduler`

[GitHK]

⚗️ Proposal for checking service status in the `dynamic-scheduler`

[sanderegg]

are you implementing Celery?

[GitHK]

are you implementing Celery?

Not at all.

I have evaluated celery and scheduler. None were sufficient for this application.
I have to build a lightweight scheduler with the requirements mentioned above.

[bisgaard-itis]

are you implementing Celery?

Not at all.

I have evaluated celery and scheduler. None were sufficient for this application. I have to build a lightweight scheduler with the requirements mentioned above.

Very interesting! But it also looks like quite a mouthful! Would it not be possible to build this on top of Celery or some other tool supported by a large community?

[sanderegg]

I do agree with @bisgaard-itis on this. if possible using an already well tested tool and build on top is a better option I think than creating everything from scratch.

[GitHK]

@bisgaard-itis @sanderegg
I would like to use a pre baked solution.

My main difficulty here is that, while the service is running I need to do the following:

• schedule a new async handler
• modify the schedule period of an existing async handler
• remove and an async handler

With celery is a bit complex to do so. It's a bit more statically configured.
I will have to implement the trie logic for scheduling and the only advantage I would get is run an event after "x" seconds done by celery. I can already have that with RabbitMQ with much, much less complexity.
And as a final argument against celery, it does not play nice with async.

Any other suggestions that I can investigate are welcomed.

[matusdrobuliak66]

@bisgaard-itis @sanderegg I would like to use a pre baked solution.

My main difficulty here is that, while the service is running I need to do the following:

• schedule a new async handler
• modify the schedule period of an existing async handler
• remove and an async handler

With celery is a bit complex to do so. It's a bit more statically configured. I will have to implement the trie logic for scheduling and the only advantage I would get is run an event after "x" seconds done by celery. I can already have that with RabbitMQ with much, much less complexity. And as a final argument against celery, it does not play nice with async.

Any other suggestions that I can investigate are welcomed.

Maybe check https://pypi.org/project/aio-celery/ whether it would be useful?

[GitHK]

@bisgaard-itis @sanderegg I would like to use a pre baked solution.
My main difficulty here is that, while the service is running I need to do the following:

• schedule a new async handler
• modify the schedule period of an existing async handler
• remove and an async handler

With celery is a bit complex to do so. It's a bit more statically configured. I will have to implement the trie logic for scheduling and the only advantage I would get is run an event after "x" seconds done by celery. I can already have that with RabbitMQ with much, much less complexity. And as a final argument against celery, it does not play nice with async.
Any other suggestions that I can investigate are welcomed.

Maybe check https://pypi.org/project/aio-celery/ whether it would be useful?

Being able to use async is just a minor detail.
I already said that I have discarded celery. It is not suited for this application. I'm searching for something that can fit to the requirements and celery is not it.