Microservice Orchestration & Distributed Systems
Coordinating multiple microservices into a reliable end-to-end transaction is one of the hardest problems in distributed systems. A payment service might succeed while the inventory service fails, leaving your data inconsistent and your customers confused. Orcher solves this by letting you write distributed workflows as regular code — with every cross-service call journaled to PostgreSQL.
The transaction state, made explicit
The classic distributed failure isn't that a service goes down — it's that afterwards nobody knows where the transaction stands. When every service call runs through a journaled task, that question always has an answer.
Either recovery path is durable: retries pick up exactly the calls that never completed, and rollback runs saga compensations in reverse order — themselves journaled, so an interrupted rollback resumes instead of restarting.
Compose along service boundaries
Child workflows let the orchestration mirror your architecture: one child per service, each owning its service's steps, retries, and failure handling — independently testable, reusable across parent workflows.
The services stay stateless — the transaction's state lives in the workflows that call them.
See Child Workflows for Service Composition for the composition mechanics, and Multi-Service Deployment for running the children in parallel across services or regions.
Waiting on other systems
Distributed transactions rarely stay inside your infrastructure. A step may need a webhook from a third party, a human approval, or a callback that arrives hours later — event gates pause the workflow at zero resource cost until the answer arrives or a timeout decides for it.
Patterns
Child Workflows
Break complex orchestrations into smaller, independently testable components mapped to microservice boundaries.
Saga Pattern
Track completed steps and run compensating actions in reverse order when a multi-service transaction fails.
Event Gates
Pause workflows until external input arrives, with timeouts that automatically escalate or reject.
Multi-Service Deployment
Coordinate operations across multiple services or regions in parallel, with rollback on failure.
Best Practices & Performance
Guidelines for idempotent compensation, shallow hierarchies, timeouts, and performance benchmarks.