Microservices

Solution Microservices

These are the microservices that implement the business logic of your solution. They are built by coding agents in the same way as core microservices and benefit from all the same infrastructure. What distinguishes them is that their logic is specific to your domain rather than being general-purpose framework functionality.

Core Microservices

Microbus comes bundled with a few core microservices that implement common functionality required by most if not all Microbus applications.

HTTP ingress - The HTTP ingress proxy bridges the gap between HTTP-based clients and microservices running on Microbus.

HTTP egress - The HTTP egress proxy relays HTTP requests to non-Microbus URLs.

SMTP ingress - The SMTP ingress microservice captures incoming emails and transforms them to actionable events.

Configurator - The configurator is responsible for delivering configuration values to microservices that define configuration properties. It is a must-have in practically all applications.

Metrics - The metrics microservice aggregates metrics from all microservices in response to a request from Prometheus.

OpenAPI portal - The OpenAPI portal microservice renders a catalog of the OpenAPI documents of each and every microservices.

Bearer token - The bearer token microservice issues long-lived JWTs for external actor authentication. These tokens are signed with PEM-configured Ed25519 keys and are typically returned to end users after successful authentication.

Access token - The access token microservice issues short-lived JWTs signed with ephemeral Ed25519 keys for internal actor propagation. On each incoming request, the HTTP ingress proxy exchanges the external bearer token for an internal access token, enriching it with additional claims via configurable transformers. The access token’s claims serve as the basis for authorization decisions throughout the call stack.

Foreman - The foreman is the orchestration engine for agentic workflows, managing the lifecycle of flows that progress through a series of task steps. It persists all state in a SQL database.

LLM - The LLM microservice bridges LLM tool-calling protocols with Microbus endpoint invocations. Callers pass a provider hostname, a model identifier, and a list of canonical endpoint URLs as tools; the service drives the tool-calling loop and dispatches calls over the bus. It ships with Claude, ChatGPT and Gemini providers, and reports per-call token usage.

MCP portal - The MCP portal microservice exposes the bus’s tools to LLM clients via the Model Context Protocol. MCP-aware clients connect to a single endpoint and discover, then invoke, the tools they’re authorized to call.