How temporalio/omes works
Omes drives Temporal load through registered scenarios and executors, with workers in multiple SDK languages consuming the resulting tasks. A separate project harness supports user-authored apps; worker metrics and Temporal integrations are additional runtime capabilities. The README documents the workflow and sidecar, while source excerpts and the index support only selected dispatch and worker links, so unsampled connections are omitted.
Main entry points: app.py Kitchen Sink Worker · main.go Omes CLI · workerctl Worker Control · main.py Harness Dispatch
Components 23
Load Runner
- Omes CLI
cmd/omes/main.go - Scenario Registry
scenarios - Scenario Definitions
scenarios - Load Executors
loadgen - Kitchen Sink Executor
loadgen/kitchensink/client_action_executor.go - Action Generator
loadgen/kitchen-sink-gen/src/main.rs - Worker Control
internal/workerctl - Worker Pool
internal/workertest/workerpool.go
Project Harness
- Project Scenario
scenarios/project - Project Runner
workers/python/harness/src/harness/project.py - User Project App
workers/python/apps/helloworld/app.py - Harness Dispatch
workers/python/harness/src/harness/main.py
SDK Workers
- SDK Client
workers/python/harness/src/harness/client.py - Worker Harness
workers/python/harness/src/harness/worker.py - Kitchen Sink Worker
workers/python/apps/worker/app.py - Workflow Actions
workers/python/kitchen_sink.py - Activities
workers/python/activities.py - Nexus Service
workers/python/nexus_service.py
Metrics
- Process Metrics Sidecar
metrics - Prometheus Export
metrics/prometheus.go
Other components
- Operator
- Temporal Server
- Worker Process
Connections 26
- Operator → Omes CLI: invokes
- Omes CLI → Scenario Registry: registers
cmd/omes/main.go - Scenario Registry → Scenario Definitions: provides
- Scenario Definitions → Load Executors: starts
- Load Executors → Kitchen Sink Executor: selects
- Kitchen Sink Executor → Temporal Server: produces load
- Action Generator → Kitchen Sink Executor: generates actions
- Omes CLI → Worker Control: runs worker
- Worker Control → Worker Pool: starts processes
internal/workertest/workerpool.go - Worker Pool → Worker Process: manages
internal/workertest/workerpool.go - Operator → Project Scenario: configures
- Project Scenario → Project Runner: drives via gRPC
- Project Runner → User Project App: dispatches load
- User Project App → Harness Dispatch: registers with
workers/python/apps/helloworld/app.py - Harness Dispatch → Project Runner: dispatches mode
workers/python/harness/src/harness/main.py - Harness Dispatch → Worker Harness: dispatches mode
workers/python/harness/src/harness/main.py - Worker Harness → SDK Client: creates client
workers/python/harness/src/harness/main.py - Worker Harness → Kitchen Sink Worker: runs factory
- Kitchen Sink Worker → Workflow Actions: registers workflow
workers/python/apps/worker/app.py - Kitchen Sink Worker → Activities: registers activities
workers/python/apps/worker/app.py - Kitchen Sink Worker → Nexus Service: registers handler
workers/python/apps/worker/app.py - SDK Client → Temporal Server: connects
- Worker Process → Temporal Server: consumes tasks
- Worker Control → Process Metrics Sidecar: starts sidecar
- Process Metrics Sidecar → Worker Process: monitors
- Process Metrics Sidecar → Prometheus Export: exports metrics