ores.dq.service

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.

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

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

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

• 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.

What the shared profile cannot know, declared here rather than hand-edited into the generated build file. Each block is spliced into its generated file after the profile's baseline.

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

The suites link what the profile cannot know about.

target_link_libraries(${lib_target_name}
    PUBLIC
        ores.service.lib
        ores.security.lib
        ores.dq.core.lib
        ores.nats.lib
        ores.database.lib
        ores.utility.lib
        ores.telemetry.core.lib
        ores.eventing.core.lib)

target_link_libraries(${tests_target_name}
    PRIVATE
        ${lib_target_name}
        ores.utility.lib
        ores.testing.lib
        ores.logging.lib
        Catch2::Catch2
        faker-cxx::faker-cxx
        Threads::Threads)