What is a Neki router?

Neki is a Postgres-compatible routing layer for sharded databases that determines which shards should execute a query and coordinates results before each selected Postgres instance creates its own execution plan. A stateless fleet of routers sits between applications and database shards, handling client connections, session state, SQL parsing, query planning, and distributed processing without requiring a separate Postgres backend process per client connection or an additional PgBouncer layer. Routers send planned work over gRPC to sidecars beside each Postgres instance, which use pooled connections to forward requests and stream responses. Queries containing a shard key, such as a user ID, can be routed to one shard and use reusable parameterized plans, while queries without a shard-key predicate are scattered across all relevant shards and then gathered, limited, or otherwise combined by router operators. Neki’s EXPLAIN options reveal both its distributed routing plan and representative Postgres execution plans, helping users inspect routing choices, remote work, and runtime behavior. By independently scaling routers for connection handling and distributed query processing and shards for data storage and database capacity, Neki is designed to grow beyond the limits of a single Postgres instance.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.