from Hacker News

Pingora: build fast, reliable and programmable networked systems

by KajMagnus on 2/28/24, 9:56 AM with 43 comments

  • by ttrrooppeerr on 2/28/24, 10:18 AM

    Their, at the time, blog post announcement about Pingora: https://blog.cloudflare.com/how-we-built-pingora-the-proxy-t...

  • by dang on 2/28/24, 11:41 AM

    Related:

    Cloudflare has replaced Nginx with in-house, Rust-written Pingora - https://news.ycombinator.com/item?id=32864119 - Sept 2022 (141 comments)

    Pingora, the proxy that connects Cloudflare to the Internet - https://news.ycombinator.com/item?id=32836661 - Sept 2022 (123 comments)

  • by lewisl9029 on 2/29/24, 3:01 AM

    Have been looking forward to this release for quite a while! Huge props to the Cloudflare team for putting this out there!

    I've been operating a cluster of NGINX nodes on Fly.io and using njs (NGINX's custom JS scripting engine) for all of my custom routing logic, and have been really feeling the limitations (had to spin up a separate companion app in nodejs to work around some of these). Having access to the entirety of the Rust language and ecosystem to customize routing behavior sounds incredibly compelling!

    I did a quick scan over the codebase and couldn't see anything around disk caching like in NGINX, only memory caching. Curious if Cloudflare is operating all their production nodes with memory caching as opposed to disk caching at the moment?

    I'd love to see an option for disk caching for use cases that are a bit more cost sensitive.

  • by inapis on 2/28/24, 11:30 AM

    so in a quick glance, this does not look like nginx/caddy. It is not a binary you download, install and just configure to talk to your upstream servers. Rather a set of packages which you assemble to fulfill a particular use case. You basically end up writing a "new" reverse proxy just for your use case.

    Not sure how useful this would be for anyone except very large businesses or someone like cloudflare itself.

  • by eptcyka on 2/28/24, 10:23 AM

    Would be cool of it was possible to use this with rustls. But I assume they didn't use it since i rustls o ly focuses on TLS 1.3 and does not support anything lower.

  • by throwaway63467 on 2/28/24, 1:17 PM

    Nice! It seems HTTP/3 isn’t mentioned or supported, which is weird as they offer HTTP/3 support in their cloud service and have their own QUIC implementation. Haven’t looked in detail so maybe it’s just missing from the readme or they didn’t open-source it (yet).

  • by jamesear on 2/28/24, 11:42 AM

    Cloudflare work on some cool stuff! It's a shame they don't hire for software engineer positions in Australia.

  • by Sytten on 2/28/24, 10:16 AM

    I had been waiting on that for a couple years since they first talked about it in their blog. Congrats!

  • by diarrhea on 2/28/24, 10:56 AM

    Very cool. Would play around with this in a heartbeat in the home lab, but Caddy's automatic HTTPS (ACME HTTP-01 and DNS-01 challenges) would be sorely missed.

    I suppose one can supplement certbot in this setup? Or use the "highly programmable" APIs Pingora provides directly?

  • by bogwog on 2/28/24, 11:43 AM

  • by sanxiyn on 2/28/24, 11:16 AM

    I heard that when Cloudbleed happened, Cloudflare CTO declared that there will be no more new projects in C or C++, and that's how it happened. Needless to say, lots of time and money were wasted.