What it does
Kestra orchestrates tasks, schedules, and event triggers with a visual interface. Flow definitions describe dependencies and execution configuration.
Why it’s interesting
Versioned flow definitions make orchestration reviewable. Isolated task execution helps manage language dependencies but requires thoughtful resource and secret configuration.
Real-world use case
On a new file event, validate data, run a transformation, and notify the team.
What I can learn
- 01
DAG validation and task execution
Learn how declarative task definitions are validated and assembled into a directed workflow before execution.
- 02
Containerized task isolation
See how isolated containers let tasks use different languages and dependencies without changing the orchestrator process.
- 03
Event triggers and scheduling
Compare event-based triggers such as webhooks with time-based schedules and understand how each starts a workflow.
One thing to explore
Flow parsing and task execution
Follow the core/src/main/java/io/kestra/core implementation and connect it to the concepts above.
Explore the source (opens in a new tab)10-Minute Challenge
Inspect a simple flow definition
Before you start: Docker and a browser; server start and initial image download may exceed ten minutes.
- Open the official local quickstart and use its Docker instructions.
- Create a flow with a single script task that prints a message.
- Execute it and inspect the task status and logs.