Add an in-memory TaskManager implementation

[inoorinoor]

Problem

Currently, the library provides task scheduling support via external dependencies such as Redis or a database. However, in some cases services may run as a single instance where no external storage is available or needed.

For example:

• A service deployed as a single instance.
• The service does not use a database or Redis at all.
• Task scheduling is only required in-memory within that process.

In such scenarios, it would be very useful to have a built-in in-memory TaskManager implementation. This would allow developers to use the scheduling features without introducing additional dependencies just for task locks.

An in memory task manager could:

• Provide the same API as the existing task managers, so users can switch between implementations if needed.
• This feature would simplify adoption for lightweight services and make the library more flexible.

Would you consider adding such an in-memory implementation?

[Patrick-Pr]

+1 for this as I encounter the same problem currently. An in memory TaskManager would be very nice.

I want to build a relative simple service which is doing the same task repeatedly on a fixed schedule. My service only consumes GraphQL endpoints runs transformations and writes data back no databases involved at all. So adding one only for running the task in a single instance would be an overhead in my case.

[Flaxoos]

Thanks for the ticket, and the input @Patrick-Pr

I'ts definitely a good feature to add and should be easy to implement. I will take it on soon, when I have time for it, but if any of you would like to take it on, please feel free to make a PR. Contribution from the community is welcome and appreciated!

[Flaxoos]

@inoorinoor @Patrick-Pr Implemented, You're welcome to review