[inapis]

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.

[mcpherrinm]

River is going to be a fully-featured reverse proxy product built on top of Pingora:

https://www.memorysafety.org/blog/introducing-river/

It's mentioned briefly in the Cloudflare blog post. I'd expect that if you're a current nginx or other proxy, River is what you'd want as an alternative.

One of the big things I'm excited about in the River plan is the ability to use wasm for scripting, which should make it relatively easy to extend.

[mkeedlinger]

Can't wait! I've currently settled on Caddy as my reverse proxy, but something rust based and extended with wasm would be great

[derekperkins]

I'm surprised Envoy isn't mentioned anywhere

[paulgb]

One reason I'm excited about this is that it appears to let you write arbitrary routing logic into a layer 7 proxy. This is something we had to build for https://plane.dev and it would have been nicer to use something like this, but we couldn't find anything like it at the time.

[wongarsu]

From their quickstart and user guide it doesn't look too verbose. For anyone whose config has reached the point where you are wondering whether it would be easier to express in code, this might be a good product to try.

Or if you run shared hosting or some other scenario where you are effectively maintaining your server configuration twice: once for the actual server and once in the database for your dashboard and other services. This would allow you to just read the config from the canonical source, instead of risking bugs when the two configs diverge.

[egnehots]

from their doc, Reasons to use Pingora:

- Security is your top priority: Pingora is a more memory safe alternative for services that are written in C/C++.

- Your service is performance-sensitive: Pingora is fast and efficient.

- Your service requires extensive customization: The APIs Pingora proxy framework provides are highly programmable.