Skip to content

Feature Matrix

All 52 features across 7 groups, each backed by unit and integration test coverage. 1075/1075 tests green.

The gateway implements 52 distinct capabilities divided across seven core functional subsystems. Every feature listed below is verified in automated unit and integration suites.

GroupFeatureStatus
Core RoutingRadix Routerimplemented
Core RoutingReverse Proxy Handlerimplemented
Core RoutingRequest Pipelineimplemented
Core RoutingRequest Context Poolimplemented
Core RoutingWebSocket Tunnelingimplemented
Core RoutingOpenAPI Generatorimplemented
Core RoutingClient Disconnect Propagationimplemented
Core RoutingRequest Coalescingimplemented
Core RoutingStreaming Response Pathimplemented
ResilienceCircuit Breakerimplemented
ResilienceRetry Managerimplemented
ResilienceHealth Checkerimplemented
ResilienceFallback Handlerimplemented
ResilienceTimeout Managerimplemented
Traffic ControlRate Limiterimplemented
Traffic ControlResponse Cacheimplemented
Traffic ControlLoad Balancerimplemented
PayloadBody Parserimplemented
PayloadRequest Transformerimplemented
PayloadResponse Transformerimplemented
PayloadCompression Handlerimplemented
ObservabilityMetrics Histogramimplemented
ObservabilityNative Structured Loggerimplemented
ObservabilityPerformance Dashboardimplemented
ObservabilityAccess Log Samplingimplemented
ObservabilityCPU & Memory Profilerimplemented
OperationsConfig Loader & Validatorimplemented
OperationsPlugin Execution Chainimplemented
OperationsAuto Tunerimplemented
Identity & SecurityJWT Auth Pluginimplemented
Identity & SecurityAPI Key Engineimplemented
Identity & SecurityUpstream Credential Injectionimplemented
Identity & SecurityRFC 7807 Problem Detailsimplemented
ResilienceTraffic Shadowingimplemented
Identity & SecurityInbound HMAC Verificationimplemented
Traffic ControlDaily Quota (per consumer)implemented
Identity & SecuritySSRF Guardimplemented
Identity & SecuritySecurity Headersimplemented
OperationsAdmin Control Planeimplemented
Traffic ControlSticky Sessionsimplemented
Core RoutingOpenAPI {param} Syntaximplemented
Core RoutingRegex-Group Path Paramsimplemented
Core RoutingOpenAPI Route Sourceimplemented
Traffic ControlCORS Policyimplemented
ObservabilityW3C Trace Contextimplemented
Identity & SecurityOutbound Secret Maskingimplemented
Traffic ControlIdempotency Keysimplemented
ResilienceAdaptive Load Sheddingimplemented
ResilienceConcurrency Limiterimplemented
OperationsRequest Record Storeimplemented
OperationsRequest Replayimplemented
ObservabilityAudit Event Streamimplemented

Features are collectively declared, enabled, and tuned through config/gateway.config.json:

Feature AreaConfiguration PathCore Controls
Routing & Upstreamsroutes, upstreamsMethods, path patterns, target origin URLs, timeout budgets.
Resilienceupstreams[].healthCheck, plugins[circuit-breaker]Health intervals, error thresholds, circuit trip cooldowns.
Traffic Managementplugins[rate-limit], plugins[cache]Window size, max tokens, TTL cache limits, key extractors.
SecurityapiKeys, plugins[auth-jwt]JWKS keys, API key header names, issuer/audience validation.
PerformanceperformanceWorker counts, memory pool sizing, buffer capacities.

Features cooperate in a strict layered pipeline:

  1. Network & Ingress: The native HTTP server receives the socket connection and allocates a pooled RequestContext.
  2. Pre-Routing Security: API Key verification and JWT token checks validate identity and enforce rate limiting quotas.
  3. Routing Match: The Radix Router selects the upstream target based on HTTP method and path patterns.
  4. Resilience & Proxying: Circuit breakers, retry managers, and reverse proxy handlers dispatch the request to the upstream origin.
  5. Post-Processing & Telemetry: Transformers modify headers or bodies, access logs are emitted, and metrics counters are updated atomically.

Measured on the reference target (4-core x86_64, Node 22):

ScenarioResultTarget
Hot target path (load-test, 100 conn)P99 5ms · 38,405 RPSP99 < 10ms · RPS > 10k ✓
acquire+release pool overhead1.5 µs/op—
Circuit breaker CLOSED fast-path~1.1 µs/req saved—
Full proxy path @ 100 conn~3.2k RPS · P99 ~40mshardware-bound ceiling*

* The full-proxy ceiling is loopback round-trip bound on a shared 4-core box (raw url-forward hop alone measures 223 µs/op), not code overhead — gateway code above the raw hop is ~28%. Documented honestly; not chased further.

  • Subsystem Isolation: Plugin or policy failures bubble up as structured RFC 7807 responses rather than crashing the Node.js process.
  • Resource Exhaustion: When concurrency limits or load-shedding thresholds are breached, the gateway sheds excess load with HTTP 503 or 429 rather than exhausting event loop memory.