Featured answer
Give me an overview of temporal
Temporal is a durable execution platform in the temporalio/temporal repository, written in Go, that runs application logic called Workflows and automatically handles intermittent failures and retries failed operations. The server process starts from cmd/server/main.go, and the service directory acts as the orchestration hub that coordinates history persistence logic, task execution and queue processing, and task matching. The client directory holds client-facing RPC stubs for history, matching, frontend, admin, and operator, along with client-side routing and connection caching, while the common directory supplies shared logging, metrics, dynamic configuration, RPC wiring, namespaces, and persistence glue. The chasm directory defines the core data model and interfaces for typed components and archetypes, and the schema directory embeds the schema filesystem used during database setup. In the layer chart, Application has 812 files, Utility has 597, and Data has 276, so those are the largest areas to explore. To start reading, open cmd/server/main.go first, then the service directory, and then chasm for the data model.
| Layer | Files |
|---|---|
| Application | 812 |
| API | 125 |
| Service | 95 |
| CLI | 2 |
| Config | 77 |
| Types | 9 |
| Data | 276 |
| Utility | 597 |
| Docs & Tooling | 31 |
Basis: Inferred · knowledge graph· as of a2de6d8