The Router compared with other options

This page compares the Stella Ops Router with well-known ways to put .NET services behind one entry point or to call them: the reverse proxies and API gateways YARP, Ocelot, Envoy and Kong Gateway, Dapr service invocation, gRPC with a service mesh (Istio), and request/response over a message bus (MassTransit, NServiceBus).

As of 2026-11-08. Every statement about another product comes from that product’s public documentation on that date, linked in Sources. Products change; check the linked page before you decide. Statements about the Router come from its source and its documentation. Each section describes how each option approaches the subject; it does not rank them.

At a glance

Connection modelWhere endpoints are declaredCaller authorization
Stella Ops RouterServices connect out to the gateway; they listen on no portIn service code (attributes) or existing ASP.NET Core endpointsJWT at the gateway, plus claims each endpoint publishes
YARPThe proxy connects to backend addressesConfiguration (appsettings.json) or codeASP.NET Core policies per route
OcelotThe gateway connects to backend hosts and portsocelot.jsonASP.NET Core schemes, scopes and claims per route
EnvoyThe proxy connects to upstream endpointsStatic configuration or xDS APIsJWT filter, RBAC filter
Kong GatewayThe gateway connects to upstream servicesAdmin API, declarative files, Kubernetes resourcesPlugins (JWT, OpenID Connect)
Dapr service invocationCaller and callee each run a sidecar; the callee listens on a portThe callee’s own HTTP routes or gRPC methodsmTLS between sidecars, access-control lists
gRPC with IstioThe callee is a gRPC server; mesh proxies intercept traffic.proto contractsMesh mTLS, JWT and authorization policies
MassTransit request/responseServices connect to a broker; no inbound portMessage contracts and consumersBroker credentials; per-request authorization not described
NServiceBus callbacksEndpoints connect to a queuing transportMessage types and handlersDelegated to the transport

Connection model

Router. Each service process connects to the gateway over a transport and announces its name, version, region and endpoints. The service needs no listening port, no load balancer entry and no inbound firewall rule; the gateway routes to the services that are connected.

YARP opens its own connections to destinations, each configured with an address, and offers destination resolvers as an integration point for service discovery [Y1, Y2, Y3]. Ocelot routes to the DownstreamHostAndPorts of each route, or looks them up from a discovery provider such as Consul, Kubernetes, Eureka or Service Fabric [O1, O2]. Envoy keeps connection pools to upstream endpoints, found by static configuration, DNS or its endpoint discovery API [E1, E2]. Kong proxies to the URL of a Gateway Service or to upstream targets given by address or DNS [K1, K2].

Dapr: the caller calls its own sidecar, which finds the callee’s sidecar through a name-resolution component; the callee’s sidecar calls the port the application listens on [D1, D2]. Istio: a gRPC client connects to a server host and port; the mesh adds proxies beside each workload (sidecar mode) or per node (ambient mode) [I1, G1]. MassTransit and NServiceBus services connect to a broker or queuing transport and consume from queues; MassTransit returns responses on a temporary queue [M1, N1].

Declaring endpoints

Router. An endpoint is a class with [StellaEndpoint(method, path)], found at compile time by a source generator, or an existing ASP.NET Core endpoint published through the bridge. Timeouts and required claims travel with each endpoint; a microservice.yaml file can override them (Microservice SDK).

YARP takes routes and clusters from configuration or code [Y2]. Ocelot reads ocelot.json [O1]. Envoy uses static configuration or the xDS discovery APIs [E3]. Kong uses its Admin API, declarative files or Kubernetes resources [K3]. Dapr targets the callee’s existing HTTP endpoints or gRPC methods [D1]. gRPC uses .proto contracts [G1]. MassTransit declares message contracts and consumers [M1, M2]; NServiceBus declares message types and handlers [N2].

Caller authorization

Router. The gateway validates JWT bearer tokens from any OpenID Connect provider, then checks the claims each endpoint publishes, such as a scope, before it forwards the request (Security).

YARP applies an ASP.NET Core authorization policy per route [Y4]. Ocelot authenticates with ASP.NET Core schemes and checks scopes and claims per route [O3, O4]. Envoy has a JWT authentication filter and an RBAC filter [E4, E5]. Kong has a JWT plugin, and claims-based authorization uses its OpenID Connect plugin [K4, K5]. Dapr offers mTLS between sidecars and access-control lists keyed on the caller’s identity [D3, D4]. Istio provides mTLS, JWT request authentication and authorization policies [I2]. MassTransit and NServiceBus rely on broker credentials and the security of the transport; per-request authorization is not described in the pages read [M3, N3].

Rate limiting

Router. The gateway counts per target service in each gateway process (in memory) and per environment across gateways (in Valkey), with overrides per service and per route. Inside an endpoint, a limiter library counts per business key, in memory, PostgreSQL or Valkey (Rate limiting).

YARP applies ASP.NET Core rate-limiter policies per route [Y5]. Ocelot has built-in per-route rate limiting [O5]. Envoy has a local token-bucket filter and integrates with an external global rate-limit service [E6, E7]. Kong’s rate-limiting plugin counts locally, in its data store or in Redis [K6]. Dapr’s rate-limit middleware applies per sidecar, not cluster-wide [D5]. Istio uses Envoy’s local and global rate limiting [I3]. MassTransit has rate-limiting middleware that delays message delivery [M4]. NServiceBus documents no rate limiting of callers in the pages read [N4].

Timeouts and cancellation

Router. Each endpoint declares its timeout; the gateway answers 504 when it expires. A timeout or a caller disconnect cancels the endpoint’s cancellation token; over the Messaging transport this needs frame protection on both sides (Long requests and cancellation).

YARP offers per-route timeouts [Y7]. Ocelot cancels a request that exceeds its quality-of-service timeout [O7]. Envoy’s route timeout defaults to 15 seconds, and an upstream timeout gives 504 [E8, E9]. Dapr applies timeouts through resiliency policies [D6]. gRPC sets no deadline by default and does not interrupt a server handler on cancellation; the handler observes it [G2, G3]. MassTransit’s request timeout defaults to 30 seconds, and cancelling stops the wait while the request can still be consumed [M1]. NServiceBus callbacks can be cancelled by the caller and do not survive a process restart [N1].

Transports

OptionBetween entry point and service
RouterTCP, TLS (with mTLS and certificate pinning), UDP, RabbitMQ, Messaging over Valkey, in-memory
YARPHTTP/1.0, 1.1, 2 and 3; gRPC; WebSocket [Y8, Y9]
OcelotHTTP/1.0, 1.1 and 2.0; WebSocket [O1, O8]
EnvoyHTTP/1.1, HTTP/2, HTTP/3, gRPC, TCP, UDP and others [E1, E10]
KongHTTP(S), gRPC(S), TCP, TLS, UDP, WebSocket [K1]
DaprgRPC between sidecars; HTTP or gRPC to the application [D1, D2]
gRPC with IstioHTTP/2; the mesh handles HTTP, gRPC, WebSocket and TCP [I1]
MassTransitRabbitMQ, Azure Service Bus, Amazon SQS/SNS, SQL Server and PostgreSQL, ActiveMQ, in-memory [M5]
NServiceBusAzure Service Bus and Storage Queues, Amazon SQS, RabbitMQ, SQL Server, PostgreSQL, IBM MQ, MSMQ and others [N5]

Operational footprint

Router. One gateway process (a .NET tool or your own ASP.NET Core host) and the services; no database. Valkey only for environment rate limits or the Messaging transport; RabbitMQ only for that transport (Deployment).

YARP is a NuGet package used as middleware in an ASP.NET Core application [Y2]. Ocelot is a NuGet package in an ASP.NET Core application [O9]. Envoy runs as a separate process or container [E1, E11]. Kong runs with PostgreSQL in traditional mode, or without a database in DB-less mode, or split into a control plane and data plane [K7, K8]. Dapr runs a sidecar per application and, on Kubernetes, a set of control-plane services [D4]. Istio runs proxies and its istiod control plane [I4]. MassTransit and NServiceBus need a broker or a database transport, and NServiceBus needs a persister for some features [M5, N6].

Sources

All pages read on 2026-11-08.