02.1
ProxyingFour protocols, one engine
HTTP, WebSocket, SSE and gRPC each get a handler tuned to them, sharing connection pooling and a graceful shutdown that drains in-flight work.
Pooled
#What it is
Bastion turns a Forge application into a full reverse proxy. It is the in-process counterpart to Octopus: same FARP-derived routing, no additional deployment.
#What it does
- Multi-protocol proxying across HTTP, WebSocket, SSE and gRPC, including streaming.
- Automatic route generation from FARP manifests, alongside static routes from config or the admin API.
- Load balancing: round-robin, weighted, random, least-connections, consistent hash.
- Per-target three-state circuit breakers, active HTTP probes and passive failure tracking.
- Token-bucket rate limiting, global or per-route or per-client, and retries with exponential, linear or fixed backoff plus a retry budget.
- Traffic splitting for canary, blue-green, A/B and shadow releases.
- Response caching with per-route policies that respect Cache-Control.
- Upstream TLS and mTLS with automatic certificate reload.
- OpenAPI aggregation across all upstream services, with Swagger UI and per-service specs.
- An admin dashboard built in ForgeUI, plus a full REST admin API and hot config reload.
#The aggregation trick
Because every service's spec already arrives in its FARP manifest, the unified OpenAPI document is a by-product rather than something anyone maintains. That single fact has removed more documentation drift than any process I have tried.