Skip to content
EN FR

Runtime service model

Documentation status: architecture — see Maturity and evidence.

A declarative service does not itself implement a queue, scheduler, agent, journal, or HTTP server. It selects and configures a runtime capability registered by the engine or by a runtime package.

service metadata
  -> parser / declarative structure
  -> service definition
  -> moduleClass / runtime registry lookup
  -> configured runtime instance
  -> start / stop lifecycle
  -> service behavior

Three levels are useful to keep separate:

  • serviceGroup: package-level grouping and deployment boundary;
  • serviceGroupDefinition: reusable service contract and configuration;
  • serviceInstance: concrete running instance with address, port, database, activation, and instance-specific parameters.

Common metadata includes a stable identifier, service family, implementation binding, diagnostic settings, startup policy, base URL/path, pages, parameters, parsers, and runtime package dependencies.

Implementation bindings shown in examples are public-normalized names. They select a concrete implementation; they are not business concepts and should not leak into domain vocabulary.