ores.scheduler.service
Table of Contents
Summary
ores.scheduler.service is the NATS service entrypoint for the scheduler
domain. It reads configuration, opens database and NATS connections, starts
the cron-based scheduler loop from ores.scheduler.core, registers all
message handlers, and runs the event loop. All scheduling logic lives in
ores.scheduler.core.
Inputs
- Configuration file: NATS server URL, PostgreSQL connection string, and environment settings.
- NATS request messages for job-definition and job-instance management.
- System clock — the scheduler loop fires due jobs based on cron expressions.
Outputs
- A running NATS service handling all scheduler management operations.
- Periodic job executions (SQL, NATS-publish, MQ actions) fired on schedule.
- NATS response messages returned to callers.
- Structured logs via
ores.logging.
Entry points
src/main.cpp— process entry point.src/app/— application bootstrap, starts the scheduler loop.src/config/— configuration parsing and validation.
Dependencies
ores.scheduler.core— all handlers, job-dispatch logic, and cron loop.ores.scheduler.api— shared protocol types.ores.logging— structured logging infrastructure.nats.c— NATS client for connection management.
See also
- ores.scheduler — component group overview.
- ores.scheduler.core — all business logic for the scheduler domain.
