IMHO Temporal and its team is great - it checks all boxes on abstracting away queues, schedulers, distributed state machines for your workflows related load balancers/gateways.
After following discussions and commits Hatchet, Inngest, Windmill, I have a feeling in few years time all other systems will have 95% overlap in core features. They are all influence each other.
Much bigger question what price you will pay by introducing workflow system like Temporal in your code base.
Temporal and co are not for real-time data pubsub.
If latency is an issue or want to keep small memory footprint, better to use something else.
The max payload is 2 MB. It needs to be serializable. Event History has limitations. It's a postgres write heavy.
Bringing the entire team on the same page, and it's not trivial either. If your team has strong Golang developers like in mine. They might oppose it and state something like Temporal is unnecessary abstraction.
For now, I decided to keep prototyping with Temporal and has it running on my personal projects till I create strong use cases and discover all edges.
The great side of effect of exploring Temporal and its competitors you will see better ways of structuring of your code. Especially with distributed state and decoupling execution.
After following discussions and commits Hatchet, Inngest, Windmill, I have a feeling in few years time all other systems will have 95% overlap in core features. They are all influence each other.
Much bigger question what price you will pay by introducing workflow system like Temporal in your code base.
Temporal and co are not for real-time data pubsub.
If latency is an issue or want to keep small memory footprint, better to use something else.
The max payload is 2 MB. It needs to be serializable. Event History has limitations. It's a postgres write heavy.
Bringing the entire team on the same page, and it's not trivial either. If your team has strong Golang developers like in mine. They might oppose it and state something like Temporal is unnecessary abstraction.
Writing your code is fun. Studying and reusing someone else patterns is not so much. Check https://github.com/temporalio/samples-go
For now, I decided to keep prototyping with Temporal and has it running on my personal projects till I create strong use cases and discover all edges.
The great side of effect of exploring Temporal and its competitors you will see better ways of structuring of your code. Especially with distributed state and decoupling execution.