0.2.3 released 4 years ago. I don’t know, a last release that long ago doesn’t inspire faith in the health of the project.
The last release was 0.8.0, about a month ago.
Redbird: A modern reverse proxy for Node
31–40 of 77 posts
Re: Redbird: A modern reverse proxy for Node
#32Sorry, but what’s a reverse proxy?
Re: Redbird: A modern reverse proxy for Node
#33Sorry, but what’s a reverse proxy?
It's where the server has a proxy that can fetch resources from different places. E.g. ServerA (proxy) get a request for /something, but then fetches it from ServerB (web server) and returns it to the client. It proxies the response to the client.
The comparison is a forward proxy, which the client has, and a reverse proxy is where it's on the server side.
Re: Redbird: A modern reverse proxy for Node
#34I am one of those JS guys who like to put JS/Node.js everywhere, but I do not get the problem Redbird is trying to solve: the Express.js doc is quite clear that for serious things, you should use a dedicated http server. [1] If you just want reverse-proxying, you can choose between the simplicity of Caddy or the power of Nginx (or Apache). Why would I want to run a JS app (that I know will be less performant) to do t…
- node (whose main reason for existing is event driven IO) is in the same order of magnitude as nginx (whose main reason for existing is also event driven IO). I think sometimes people think node is ruby/python/php levels of performance. It isn't.
- And as another comment mentions, developer productivity may be better than minor performance difference - you mentioned Caddy, same rationale applies here.
- nginx is also a bit crippled as useful features (like dynamic reconfig) are only in the proprietary nginx plus.
- This has good defaults - having to set up the seperate webserver for ACME is a pain, this is way easier.
Re: Redbird: A modern reverse proxy for Node
#35Yet another JavaScript project reinventing the wheel and badly at that. It seems the NodeJS community suffers from NIH syndrome more than others. This is a sign of lack of seniors and leadership.
Re: Redbird: A modern reverse proxy for Node
#360.2.3 released 4 years ago. I don’t know, a last release that long ago doesn’t inspire faith in the health of the project.
The last release was 0.8.0, about a month ago.
The releases on github are outdated.
Re: Redbird: A modern reverse proxy for Node
#370.2.3 released 4 years ago. I don’t know, a last release that long ago doesn’t inspire faith in the health of the project.
It doesn't look like they're using GitHub releases. npm shows some much more recent versions: https://www.npmjs.com/package/redbird.
Re: Redbird: A modern reverse proxy for Node
#38I am one of those JS guys who like to put JS/Node.js everywhere, but I do not get the problem Redbird is trying to solve: the Express.js doc is quite clear that for serious things, you should use a dedicated http server. [1] If you just want reverse-proxying, you can choose between the simplicity of Caddy or the power of Nginx (or Apache). Why would I want to run a JS app (that I know will be less performant) to do t…
- node (whose main reason for existing is event driven IO) is in the same order of magnitude as nginx (whose main reason for existing is also event driven IO). I think sometimes people think node is ruby/python/php levels of performance. It isn't. - And as another comment mentions, developer productivity may be better than minor performance difference - you mentioned Caddy, same rationale applies here. - nginx is als…
Do you know of a performance benchmark that shows the current status? I can't find many that describe node not at those levels of performance, Especially against Ruby.
Re: Redbird: A modern reverse proxy for Node
#39Sorry, but what’s a reverse proxy?
It's where the server has a proxy that can fetch resources from different places. E.g. ServerA (proxy) get a request for /something, but then fetches it from ServerB (web server) and returns it to the client. It proxies the response to the client. The comparison is a forward proxy, which the client has, and a reverse proxy is where it's on the server side.
Reverse proxies also often provide optional benefits like...
Load balancing, not having to run the webserver as root to bind to 80/443, caching responses, buffering, rate limiting, injecting headers, serving static assets, etc.
Re: Redbird: A modern reverse proxy for Node
#40Earlier quoted context omitted.
Convenience is one I've used redbird to create a local dev proxy that can run be via npm scripts (which were already in the repo) so our engineering team didn't have to run the entire constellation of docker containers if they were only working on frontend code, and the only setup required was `npm install` which they already needed to do I do wish you could just `npm install nginx` though
how would npm install nginx be different from [yum|apt] install nginx?
On top of what others said, ease of use during (team) development through simplicity and consistency - some developers have Macs, some have Linux, some have Windows - and no one wants a work project altering their system anyhow.