ores.dq.service

Table of Contents

Diagram

ores.dq.service component diagram

Figure 1: ores.dq.service

Summary

ores.dq.service is the NATS service entrypoint for the data-quality domain. It reads configuration, opens database and NATS connections, registers all message handlers from ores.dq.core, and runs the event loop. All business logic lives in ores.dq.core; this component is responsible only for bootstrap, dependency injection, and graceful shutdown.

Inputs

  • Configuration file: NATS server URL, PostgreSQL connection string, and environment settings.
  • NATS request messages from Qt clients and peer services (badge, dataset, change-management operations).

Outputs

  • A running NATS service handling all data-quality operations.
  • NATS response messages returned to callers.
  • Structured logs via ores.logging.

Entry points

  • src/main.cpp — process entry point.
  • src/app/ — application bootstrap and dependency injection.
  • src/config/ — configuration parsing and validation.

Dependencies

  • ores.dq.core — all NATS handlers, repositories, and domain services.
  • ores.dq.api — shared protocol types.
  • ores.logging — structured logging infrastructure.
  • nats.c — NATS client for connection management.

See also

  • ores.dq — component group overview.
  • ores.dq.core — all business logic for the data-quality domain.

Emacs 29.1 (Org mode 9.6.6)