Skip to content
Tenura docs

Services, RPC & Web

Microservices, ingress, typed RPC, async / durable APIs.

When to read this section

You are exposing a service to the network: an internal microservice, an HTTP API, an async API with retry-safe receipts, or a typed RPC interface other services consume. These recipes use lease-bounded ingress and shared-memory transports where they fit, and durable receipts where retries are unavoidable.

Suggested order

  1. Typed RPC Service — the smallest API surface other services can call. Establishes the request/response shape.
  2. Zero-Copy Microservices That Talk Through Memory, Not Sockets — the inter-service variant. Same call shape, dramatically lower latency.
  3. Web Server With Leased Ingress and Replicas — the public HTTP variant with ingress that elastically scales.
  4. Durable Async API With Receipts — the retry-safe variant. Use this for any endpoint a client may legitimately retry.

What’s not here

Streaming endpoints and message buses. See Pipelines & Workflows. Inference-specific request gateways. See GPU & Inference / shared inference.