Why must every implementation of a durable workflow be a service? Can't we just have a simple SDK that utilizes existing infrastructure like Redis or PostgreSQL, which is most likely already being used in the application?
This project is currently under development. Our aim is to offer an easy method to define and execute durable workflows in TypeScript, leveraging the common infrastructure you may already be familiar with. While it may not scale as effectively as other dedicated services, it should suffice until you're in a position to invest in those services.
Existing solutions like,
- Temporal is great, but it's costly, has a steep learning curve and self hosting is not easy.
- Inggest is great, but it's costly and no way to self host right now (as of April 2024). If going by the trend most likely it won't be easy to self host when they do release it.
- Trigger is great, and one of the solutions which is easy to self host and easy to write, but with their changes in v3 it does not seem easy to self host.