Self-journaled host adapters for TanStack Workflow

[isaacwasserman]

I really appreciate the idea of Tanstack Workflow as standard interface for durable execution. However, I've noticed that the adapter interface doesn't currently support popular durable execution tools like Temporal, AWS Lambda Durable Functions, or Vercel Workflows because it assumes that there is a manually accessible store (like a database) whereas existing durable execution tools provide high level primitives like ctx.step() and ctx.sleep() that are self-journaling (i.e. implicitly maintain their own state). All Tanstack Workflow would need to do in the case of these environments is wrap the provided primitives.

Now, you may ask, "if you're already using a durable execution service, why are you trying to use TanStack Workflow?", but I think the package can be useful simply as a multiplexer. It could even be used by package developers to publish services that run as durable functions while the host provides the durable execution environment in the form of a configured adapter.

Is this something the maintainers would consider? As far as I can tell, nothing like this exists today, and would be very useful.

Disclaimer: I understand TanStack Workflow is still in the very early stages of development, so I don't expect this to be acted on right away.