A business process may need to call several services, wait for a response and retry failed steps without losing track of progress. Temporal provides a workflow service that records execution state so application work can continue across process failures. Developers write the workflows and workers that perform the business actions. It helps coordinate that logic, but the server does not supply the business code or make external actions safe to repeat; worker versioning and recovery still need design.
Chart ownership
The Temporal-owned chart repository publishes the server chart through go.temporal.io/helm-charts. Its current documentation says the chart installs Temporal server components and requires you to provide persistence databases. The default execution store and the visibility store have different responsibilities and supported backend choices.
Before adoption
Plan database ownership, schema migrations, retention and recovery before installation. Configure client authentication, transport security and namespace boundaries. Application workers still need their own delivery and versioning strategy; installing the server does not deploy business workflows. Test worker failure and replay compatibility as well as server restarts. Existing deployments using older chart generations should follow the repository's migration guidance instead of carrying old database-subchart assumptions into an upgrade.
Sources & further reading
Spotted something that needs another look?
Help improve this page →