How Cloudflare Was Able to Support 55 Million Requests per Second With Only 15 Postgres Clusters

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

Cloudflare achieved the ability to support 55 million requests per second using only 15 Postgres clusters. They utilized PgBouncer as a connection pooler to manage Postgres connections, avoided the thundering herd problem, employed high-performance bare metal servers instead of cloud infrastructure, used the TCP Vegas congestion avoidance algorithm for concurrency management, ordered queries at the PgBouncer layer, and ensured high availability with the Stolon cluster manager.

<p>Yeah, cloud never disappoint as I seen it’s a fascinating thing to say that cloud flare is handling 55 million requests per second It is unimaginable number and it is. I was wondered how it is capable of handling search request.</p>


<p>Cloudflare offers more than said for the developers.</p>
