Meta Deploys ZGateway Proxy for ZippyDB Traffic
Meta’s engineering team has introduced ZGateway, a stateless proxy tier between client applications and ZippyDB, the company’s widely used key-value store. The system handles more than 1 billion operations per second and currently carries about 40% of ZippyDB traffic, with Meta projecting that share to exceed 60%. The average computational overhead is about 6%.
ZGateway was created to address connection growth across more than a million client hosts. Under direct access, clients could connect to tens of thousands of shards across large numbers of database hosts, creating high memory, CPU and file-descriptor consumption and increasing the risk of reconnection failures. The proxy consolidates these connections through regional tiers discovered using ServiceRouter.
The service terminates TLS, applies access controls and tenant-level admission policies, resolves shards, batches requests and forwards them to the appropriate replicas. Some tiers also provide read-through caching, using change-data-capture events to maintain bounded freshness. Meta reports that a controlled overload test isolated six noisy tenants among roughly 1,350 buckets while the remaining tenants completed 99.9% of requests with no rejections. ZGateway also supports migration controls, cross-region failover, adaptive load balancing and transaction handling. It is an internal Meta system rather than a generally deployable product.
Written by Sakhanda Wire AI from reporting by MarkTechPost. Facts, quotes and full context are in the original article below.