samples-go

> Temporal is absolutely not for a static graph I'd clarify this to say "Temporal is absolutely not limited to a static graph." It can certainly handle a static graph, but it can also handle a dynamic one. Here is an example in Go (https://github.com/temporalio/samples-go/tree/main/choice-mu...), there are similar ones for other languages. I think the confusion might stem from the determinism requirement in Temporal (and other replay-based Durable Execution platforms). It's not the Workflow Definition (i.e., the code) that must be deterministic, it's the Workflow Execution (i.e., a specific running instance of that code) that must be deterministic. Each running instance is allowed to take a different path through that code, so long as it does so consistently when executed with the same input.

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 develop

There's loads of code-examples: https://github.com/temporalio/samples-go https://github.com/temporalio/samples-typescript https://github.com/temporalio/samples-php https://github.com/temporalio/samples-java