docker-compose upgo run ./workflow/main.goto "execute" (submit) a new workflowgo run ./worker/main.goto spin up the worker to actually execute the workflow and its actions- http://localhost:8088 to check out the execution status
The most basic understanding: an enhenced RPC framework.
As the workflow (client) only says what workflow to execute with what activities, it is up to the workers (servers) to actually execute those workflows.
Due to the fact it is so generic but handles so many common "workflow" cases, it is a power tool to boost productivity to focus on the actual business logic instead of redo the plumbing everytime a similar use case arises.
- Temporal gives you full visibility in the state of your Workflow and code execution.
- Temporal maintains the state of your Workflow, even through server outages and errors.
- Temporal makes it easy to timeout and retry Activity code using options that exist outside of your business logic.
- Temporal enables you to perform "live debugging" of your business logic while the Workflow is running.
https://docs.temporal.io/docs/go/introduction https://docs.temporal.io/docs/go/run-your-first-app-tutorial/ https://medium.com/@ijayakantha/microservices-the-saga-pattern-for-distributed-transactions-c489d0ac0247