ores.compute.service

Table of Contents

1. Diagram

ores.compute.service component diagram

Figure 1: ores.compute.service

2. Summary

ores.compute.service is the NATS service entrypoint for the compute orchestrator. It opens database and NATS connections, registers all message handlers from ores.compute.core, and runs the event loop.

3. Inputs

  • Configuration file: NATS server URL, PostgreSQL connection string.
  • NATS messages from workers and UI clients.

4. Outputs

  • A running NATS service for compute orchestration.

5. Entry points

  • src/main.cpp, src/app/, src/config/.

6. Dependencies

  • ores.compute.core, ores.compute.api, ores.logging, nats.c.

7. Build dependencies

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.

8. Options

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.

8.1. telemetry_interval_seconds

Interval in seconds between compute grid telemetry samples.

Set to 0 to disable the grid poller entirely.

9. See also

10. Test dependencies

The suites link what the profile cannot know about.

target_link_libraries(${lib_target_name}
    PUBLIC
        ores.service.lib
        ores.security.lib
        ores.compute.core.lib
        ores.eventing.core.lib
        ores.nats.lib
        ores.database.lib
        ores.utility.lib
        ores.telemetry.core.lib
    PRIVATE
        ores.workflow.api.lib
        ores.iam.client.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)

Emacs 29.3 (Org mode 9.6.15)