Right.. the tricky thing is when you think your use case is relatively basic, you're a one person team, and you want to decide whether to pull in such a powerful tool, and deploy and manage it.. or take a more DIY approach, have it all just run on demand in the cloud, and not have to learn a bunch of APIs and concepts as they're described by Temporal etc.
cloudflare alarms seem like a decent solution for scheduling. If you want a state machine, you can just use a state machine (xstate).
The durable object primitives are more limited, but therefor seem a little easier to get your head around if you don't need all sorts of complex signalling.
introspection / analytics is obviously a pain to have to deal with yourself. I guess you'd end up saving the state to a database after any action. And you could probably get a reasonable little analytics dashboard fairly painlessly by chucking something like appsmith in front of it?
cloudflare alarms seem like a decent solution for scheduling. If you want a state machine, you can just use a state machine (xstate).
The durable object primitives are more limited, but therefor seem a little easier to get your head around if you don't need all sorts of complex signalling.
introspection / analytics is obviously a pain to have to deal with yourself. I guess you'd end up saving the state to a database after any action. And you could probably get a reasonable little analytics dashboard fairly painlessly by chucking something like appsmith in front of it?