Is there a feature-based reason to use this over HAProxy or nginx, or is this a "it's written in Node" thing?
* Asynchronous SNI - you may load cert/key pairs on the fly and let bud know which backend do you want it to connect the incoming client to
* Asynchronous OCSP stapling
* TLS ticket rotation, with possibility to scale to the big cluster
* x-forward frame for SPDY, and soon for HTTP/2 too
* Lots of other features, but nothing bud-specific
Bud is written in C, not Node. It uses NPM for cross-platform packaging, but that is optional.
> Is there a feature-based reason to use this over HAProxy or nginx,
It can be useful to have SSL termination be in its own process to isolate OpenSSL from other parts of your internal system like HTTP routing/request handling. For instance, in cases where you have explicit security requirements like FIPS 140-2.
Got it, thanks.
> It can be useful to have SSL termination be in its own process to isolate OpenSSL from other parts of your internal system like HTTP routing/request handling. For instance, in cases where you have explicit security requirements like FIPS 140-2.
Sure. I run two HAProxy instances for that, though.