DEVOURED
Skipper, Airbnb's embedded workflow engine, is now open source
Airbnb open-sourced Skipper, an embedded workflow engine that removes the need for a centralized orchestration cluster by persisting process state locally.
What: Skipper is now available under the Apache 2.0 license. It treats Java or Kotlin classes as long-running processes, using leases and database-backed persistence to handle failures without external infrastructure like Temporal or Airflow.
Why it matters: This represents a shift toward 'process-oriented' architecture where developers can manage complex stateful workflows within their own service boundaries rather than relying on heavy external dependencies.
Takeaway: If you are managing long-running stateful services in Java/Kotlin, evaluate if Skipper can replace your current orchestration dependency for simpler deployment.
Deep dive
- Embedded Architecture: Skipper runs inside the application process.
- State Persistence: Uses the service's own database to track process progress.
- No Central Cluster: Eliminates the operational overhead of managing external orchestration servers.
- Fault Tolerance: Replicas use leases to automatically resume stalled or failed workflows.
- Developer Workflow: Processes are defined as code using standard language primitives.
Decoder
- Orchestration Cluster: A centralized group of servers responsible for managing, scheduling, and executing multi-step workflows.
Original article
Airbnb has open-sourced Skipper, the embedded workflow engine its teams run in production, under Apache 2.0. Processes are Java or Kotlin classes whose progress persists in the service's own database, with no central orchestration cluster. Replicas run the scheduler and use leases to take over work when one fails.
Explore all 61 articles in today's digest
Fresh dev news, AI-digested daily. Never miss a trend at devoured.fyi