Skip to content
EN FR

HTTP Service

Documentation status: architecture — see Maturity and evidence.

Purpose

The HTTP service family provides an HTTP boundary around published logiCells capabilities and web resources. It can be used for application endpoints, web publication, API adapters, and runtime-facing service integration.

The public contract is the published capability, not a private server class or a historical configuration tag.

Architecture

model capability
    -> publication contract
    -> HTTP adapter
    -> HTTP endpoint
    -> client

Use HTTP when

  • a client needs request/response access to a published capability;
  • an application exposes REST-style or documented HTTP endpoints;
  • web content or a renderer is hosted behind an HTTP boundary;
  • an RPC adapter uses HTTP as its transport.

Operational rules

  • configure TLS for remote production endpoints;
  • keep authentication and authorization explicit at the application boundary;
  • apply timeouts to remote calls;
  • retry only safe or idempotent operations;
  • propagate correlation identifiers;
  • do not expose private Runtime objects as durable business identifiers.

Local and remote execution

HTTP is a transport boundary. It does not redefine the application model. A generated SDK can target a local Runtime or a remote Runtime while preserving the same public object model where the capability supports parity.

Configuration status

Exact server-module names, configuration tags, and legacy .services examples are version-dependent implementation details and are intentionally not presented here as stable public contracts. Use the configuration reference shipped with the Runtime version being deployed.