DATABASES Signal 46
Neki router gives apps one Postgres connection while planning queries across shards
↗
A Neki router sits between an application and a sharded Postgres database, presenting a single connection while routing and coordinating queries across shards.
For engineers running sharded Postgres, Neki removes the need for a separate connection pooler and lets applications connect as if to a single database. It adds a scaling knob for distributed query processing separate from data sharding, and its stateless routers can be added or removed as workloads change.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
The router builds a Neki plan to decide which shards execute a query, then Postgres builds its own plan per shard.
Routers are stateless and handle client connections, so they can be scaled independently of shards.
The router speaks the Postgres protocol, parses SQL, and coordinates results, replacing PgBouncer and a TCP proxy.
THE CLUSTER