ores.synthetic.service

ores.synthetic.service is the NATS service entrypoint for the synthetic data domain. It reads configuration, opens the NATS connection, and runs the event loop. Composition happens in two places: registrar.cpp registers the entity handlers and history providers from ores.synthetic.core, and the per-entity event registrars in messaging/ wire the DB-notify to NATS publish chain for each changed event. The feed control plane (feed configuration, feed start and stop, folder feed control, IR curve preview, and simulation handlers) also lives here. One per-kind registry, feed_kind_registry, carries what the control plane needs to know about an asset class — its factory kind, its config read permission, its config-row loader, its build-input resolver and its simulate payload — so no handler branches on a kind.

• Configuration file: NATS server URL and environment settings.
• NATS request messages for entity CRUD, feed configuration and control, simulation, and preview.

• A running NATS service handling all synthetic data subjects.
• 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/feed_kind_registry.hpp — the per-kind registry.
• src/registrar.cpp — handler and history provider composition.
• src/messaging/ — per-entity event registrars.

• ores.synthetic.core — all entity handlers and services.
• ores.synthetic.api — shared protocol types and feeds.
• 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.

The options this service takes beyond logging, NATS and the database. Codegen writes the member, its wire field, its command-line declaration and its assignment from each entry.

• ores.synthetic.core — repositories, services, and NATS handlers.

The suites link what the profile cannot know about.

target_link_libraries(${lib_target_name}
    PUBLIC
        ores.service.lib
        ores.security.lib
        ores.synthetic.core.lib
        ores.analytics.quant.lib
        ores.marketdata.api.lib
        ores.marketdata.client.lib
        ores.marketdata.core.lib
        ores.iam.client.lib
        ores.iam.core.lib
        ores.refdata.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)