# APIs & durable systems

> We build long-running operations that survive restarts, retries and partial failure, using Temporal for durable execution. When a step fails at three in the morning the workflow resumes from where it stopped rather than from the beginning, and the full history of what happened is available afterwards.

For: Engineering leads with reliability pain
Canonical: https://www.techfabric.com/services/apis

---

Temporal turns a fragile chain of API calls into a workflow with history. When a step fails at three in the morning, the workflow resumes from where it stopped rather than from the beginning, and you can read exactly what happened.

## What it includes

- Durable workflows with complete, replayable execution history
- Compensation and rollback paths designed in, not bolted on
- Human-in-the-loop approval gates that survive process restarts
- Migration of existing job chains onto durable execution

## Questions

### What problem does durable execution actually solve?

Any process with more than a few steps that must not half-complete: a payment that charges but does not fulfil, a repossession that starts but is never recorded, a pipeline that dies mid-run and leaves partial data. Temporal makes the workflow itself durable, so the process survives the infrastructure under it.

### Do we have to rewrite our services to use Temporal?

No. The usual pattern is to leave the services alone and put a workflow in front of the sequence that calls them. Your existing APIs become activities. That is how we migrate an existing job chain without a rewrite.

### How is this different from a queue and retries?

A queue gives you delivery. It does not give you the state of a business process. Temporal keeps a complete, replayable history of the workflow, so you can answer what happened, where it stopped and what compensating action ran, without reconstructing it from logs.

### Can a human approval sit in the middle of a workflow?

Yes, and it survives a restart. A workflow can park for days waiting on a signal, then continue from exactly where it stopped. We use that pattern in our own systems for anything that leaves the workspace.

### Do you work with Temporal Cloud or self-hosted?

Both. TechFabric is a Temporal partner and we have certified durable paths against Temporal Cloud, including a workflow that survived a full application restart and completed from its original history.