ores.controller.core

Table of Contents

Diagram

ores.controller.core component diagram

Figure 1: ores.controller.core

Summary

ores.controller.core is the service registry and lifecycle controller for ORE Studio. It maintains a catalogue of service definitions (service_definition), running instances (service_instance), and lifecycle events (service_event), letting the platform monitor which services are up, track failures, and drive orchestrated startup/shutdown sequences. NATS handlers expose the registry to Qt clients and other services.

Inputs

  • NATS registration and heartbeat messages from all running services.
  • NATS management requests from Qt clients (service listing, event history).
  • PostgreSQL connections to ores_controller_* tables.

Outputs

  • Service-registry records persisted to the ores_controller schema.
  • NATS response messages returned to callers.

Entry points

  • include/ores.controller.core/ores.controller.core.hpp — aggregate include.
  • include/ores.controller.core/messaging/registrar.hpp — registers handlers.
  • include/ores.controller.core/messaging/ — per-entity NATS handlers.

Dependencies

  • ores.controller.api — shared domain types and NATS protocol schemas.
  • ores.dq, ores.iam.core, rfl, soci, nats.c.

See also

Emacs 29.1 (Org mode 9.6.6)