Meta Built ZGateway to Manage ZippyDB Traffic

The proxy layer reduces connection overhead by 19x to improve reliability for large-scale database infrastructure.

Updated on Sept. 28, 2026 in Data Centers

Isometric editorial illustration of metallic server canisters connected to a central server rack, representing database infrastructure traffic management.
Meta has deployed ZGateway, a new stateless proxy layer designed to handle traffic for its ZippyDB database infrastructure and improve system reliability. AI Illustration. Upload story photo >

Live Poll

Do you trust that new proxy architectures effectively improve long-term digital service reliability?

Meta has introduced ZGateway, a new stateless proxy layer designed to manage traffic for ZippyDB, the company's system for product metadata and configuration workloads. The architecture currently processes 40% of all ZippyDB traffic.

Why it matters

Direct client connections previously caused file descriptor exhaustion and memory issues, threatening database stability. This new layer isolates the database servers from these connection-related risks.

ZGateway handles over 1 billion operations per second, delivering a 97% to 98% reduction in per-host connection counts. During high-CPU load testing, 99.9% of requests for 1,350 tenant buckets were successfully processed.

The players

Meta

A global technology firm focused on social media, artificial intelligence, and hyperscale data center infrastructure.

The details

ZGateway functions as a managed proxy tier that sits between client hosts and ZippyDB servers. Clients maintain sticky connections—persistent, consistent pathways between a specific client and server—to regional gateway hosts, which then multiplex requests to the backend database fleet. This design offloads the connection management burden from the database nodes, preventing the out-of-memory errors associated with massive direct-client connection counts.

Timeline

  1. September 28, 2026: Official details of the ZGateway architecture were published.

The Tech Race

As Meta continues to scale its data infrastructure, the shift toward proxy-based routing mirrors broader industry efforts to decouple client connection state from backend database performance. This architectural move ensures that ZippyDB can handle higher throughput without exhausting resources at the individual node level.

This backend architectural update ensures more reliable performance for applications and services powered by ZippyDB metadata. The changes occur entirely at the infrastructure layer, requiring no direct action from platform users or external developers.

The takeaway

Meta has successfully demonstrated that decoupling connection management from core database nodes significantly improves system headroom. Watch for future updates regarding the migration of the final 60% of traffic through the ZGateway fleet.

Further reading

For more on how major platforms scale backend infrastructure, visit our section on Data Centers.

Source note: This article includes information reported by InfoQ.

Live Poll

Do you trust that new proxy architectures effectively improve long-term digital service reliability?