Building Asynchronous SOA for Modern Apps
summary
Claims workflow orchestrators replace brittle event‑driven state machines by providing state management, built‑in retries/backoff (examples include a configurable 200 retries), long‑running execution with at‑least‑once semantics, and out‑of‑box metrics and tracing. Compares Apache Airflow, Argo, Temporal and AWS Step Functions, recommends Temporal for complex dynamic or week‑long workflows and Step Functions when fully tied to AWS, and reports that using orchestrators reduces operational overhead and increases reliability.
AI-written summary · about
chapters (15)
- 0:00Asynchronous SOA intro
- 1:02Defining service-oriented architecture
- 3:11Async SOA in real systems
- 5:39State management challenges
- 7:26Resiliency and error handling
- 9:10Traceability and auditability
- 10:15Maintainability in complex systems
- 12:02Solving challenges with workflows
- 15:52Streamlining state management
- 18:03Enhancing resiliency
- 20:13Enabling traceability
- 22:00Facilitating maintainability
- 24:13Developer productivity
- 26:46Workflow orchestrator options
- 30:18When to use workflows
related talks
41mGetting started with Orchestration and Choreography in Distributed Applications
44mGetting started with Orchestration and Choreography in Distributed Applications
44mOrchestrate Your Business Workflows with Temporal.io
52mMovin beyond request-reply: how smart APIs are different
20mModern Application Architecture with AWS Step Functions
51mChoreography vs Orchestration in serverless microservices
46mThe End of Event-Based Architectures? Orchestration with Temporal
25mOrchestrating Workflow for Microservices Integration