ores.analytics.service

ores.analytics.service is the NATS service entrypoint for the analytics domain. It reads configuration, opens database and NATS connections, registers all message handlers from ores.analytics.core, and runs the event loop. All business logic lives in ores.analytics.core.

• Configuration file: NATS server URL, PostgreSQL connection string.
• NATS request messages for analytics configuration operations.

• A running NATS service for analytics operations.
• NATS response messages returned to callers.
• Structured logs via ores.logging.

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

• ores.analytics.core — all NATS handlers, repositories, and services.
• ores.analytics.api — shared protocol types.
• ores.logging — structured logging.
• nats.c — NATS client.

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.analytics — component group overview.
• ores.analytics.core — all business logic for the analytics domain.

The suites link what the profile cannot know about.

target_link_libraries(${lib_target_name}
    PUBLIC
        ores.service.lib
        ores.security.lib
        ores.analytics.core.lib
        ores.eventing.core.lib
        ores.nats.lib
        ores.database.lib
        ores.utility.lib
        ores.telemetry.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)