#XState on server for long-running scheduler?

1 messages · Page 1 of 1 (latest)

soft hull
#

I dig XState on the client for short-running processes.

But is XState also good for this?: on the server for managing state of long running scheduled actions X minutes, hours, days, weeks, months... into the future?

And if so, is there any info out there I can check out?

I do see the blurb on XState for the server in the docs, the "XState in the backend" YouTube video example and "waitFor" in the docs which mentions use for short-running processes.

Thanks!

daring timber
#

@junior estuary Might want to open up about future plans for this.

soft hull
junior estuary
# soft hull Looking thru Canny to try to get up to speed on v5... And see things like this: ...

It's already possible to use XState with Temporal; just takes some manual wiring up of some things. Here's an example: https://github.com/Devessier/temporal-electronic-signature

GitHub
GitHub - Devessier/temporal-electronic-signature: Electronic signat...

Electronic signature demonstration built with Temporal and XState - GitHub - Devessier/temporal-electronic-signature: Electronic signature demonstration built with Temporal and XState

soft hull
#

Thanks David. Yeah I saw that a while back.

  1. Is that Xstate + Temporal a good use for long running scheduler in your opinion?

  2. Will v5 have anything in this department to keep an eye out for?

  3. Curious if anyone has thoughts on Xstate + other, non-Temporal services/tools for long running scheduler?

Thanks!

junior estuary
#
  1. Is that Xstate + Temporal a good use for long running scheduler in your opinion?

I'd say so! Can even use after transitions and schedule them for days, weeks, ++

#
  1. Will v5 have anything in this department to keep an eye out for?

Potentially. We're building it with server-side use-cases in mind.