Seeking Feedback on Using @effect/cluster for Production Workflows
I'm at a point where I need to implement a reliable, durable workflow solution. Since most of my code base is written in Effect, I'm very inclined to do it with @effect/cluster.
I just want to know if anyone has been running this in production to know whether, even though it is still early, it's something that I should venture into.
eg: are there any pitfalls that makes it unusable right now.
The alternatives are, of course, Temporal, Ingest, restate.dev - But I much prefer the level of control you have with @effect/cluster over how you write and structure of the code as opposed to the more opinionated alternatives out there.
I just want to know if anyone has been running this in production to know whether, even though it is still early, it's something that I should venture into.
eg: are there any pitfalls that makes it unusable right now.
The alternatives are, of course, Temporal, Ingest, restate.dev - But I much prefer the level of control you have with @effect/cluster over how you write and structure of the code as opposed to the more opinionated alternatives out there.
