ores.workflow.service

Table of Contents

1. Diagram

ores.workflow.service component diagram

Figure 1: ores.workflow.service

2. Summary

ores.workflow.service is the NATS service entrypoint for the workflow domain. It reads configuration, opens database and NATS connections, registers all message handlers from ores.workflow.core, and runs the event loop.

3. Inputs

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

4. Outputs

  • A running NATS service for workflow operations.
  • NATS response messages returned to callers.

5. Entry points

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

6. Dependencies

  • ores.workflow.core, ores.workflow.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. See also

9. 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.workflow.core.lib
        ores.nats.lib
        ores.database.lib
        ores.utility.lib
        ores.eventing.core.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)

Emacs 29.3 (Org mode 9.6.15)