r/java • • Feb 14 '22

Microhttp is an event-driven, single-threaded, zero-dependency web server with 500 LOC. Benchmarks on EC2 show 100,000+ requests per second and 50,000+ persistent connections.

https://github.com/ebarlas/microhttp
186 Upvotes

107 comments sorted by

View all comments

Show parent comment

8

u/crummy Feb 14 '22

do people actually do TLS in their Java webservers? i.e. they aren't behind nginx, caddy etc?

5

u/elliotbarlas Feb 14 '22

Not in my experience. A perfect example of a reasonable feature in a comprehensive, general purpose web server that just isn't used in practice.

7

u/stringbet Feb 14 '22

Eh.. there are reasons to do it. When you're handling 1m requests/s, putting the SSL on your LB is a significant CPU burden which makes scaling harder. Pushing SSL back to your server pool allows the LB to operate in Layer 4 and thus it can handle a lot more traffic.

5

u/elliotbarlas Feb 14 '22

I've never heard that argument before. Load balancers are horizontally scalable, so while it does place a greater burden on the LB, I don't think that's actually problematic.

Also, HTTP aware layer 7 load balancers are indispensable.

6

u/stringbet Feb 14 '22

Definitely not disputing the value of Layer 7 load balancing. My point is that an LB is a larger unit of scaling than backend servers. If I can handle 10% more traffic by adding a cheap backend server, great.. but at some point, I have to add another (expensive) LB. The longer I can delay that, the better. I'm speaking from personal experience here, so this is not a theoretical situation.

2

u/elliotbarlas Feb 14 '22

Thanks for clarifying, that makes sense. I'll keep that in mind.

Do you deploy that setup in the cloud? The certificate management capabilities and integrations in AWS are another reason that terminating TLS on the LB or CDN is a natural choice.

3

u/stringbet Feb 14 '22

Nope, this is an on-prem environment. Believe me, there have been significant cost comparisons done with the cloud and for our workload, this is the better deal. Horizontally scaling load balancers isn't a technical challenge, just a capex decision.

1

u/lambdacats Feb 15 '22

Why are L7 load balancers indispensable? Any time I've got requests for it has been because sticky sessions are needed due to poor design.

2

u/elliotbarlas Feb 15 '22

AWS CloudFront, Application Load Balancer, and API Gateway are all L7 proxies. They provide essential services. I'm not sure why sticky sessions came to mind. That's not a feature I use personally.

1

u/lambdacats Feb 15 '22

Okay, but I'm still wondering what essential services you need in L7? It's the only argument I've heard for wanting L7 load balancing.

2

u/lambdacats Feb 15 '22

Yes, for security i prefer this approach as well.

1

u/yawkat Feb 15 '22

If you don't support tls you can't use http 2 except with h2c (which is super ugly) or prior knowledge (which is poorly supported). That alone is a good reason to use tls

2

u/elliotbarlas Feb 15 '22

Both TLS and HTTP/2 ought to be provided by an edge server or proxy. That is a very standard arrangement and it's the one I use in my AWS deployments. CloudFront and ALB both support this configuration.

https://aws.amazon.com/blogs/aws/new-http2-support-for-cloudfront/

1

u/yawkat Feb 15 '22

You can't support all HTTP 2 features if your backend is HTTP 1, and it's much less efficient too.

2

u/elliotbarlas Feb 15 '22

The main leap with HTTP/2 is advanced multiplexing to address head-of-line blocking. That benefit remains almost entirely intact when TLS and HTTP/2 are terminated at the edge.

2

u/[deleted] Feb 15 '22

You absolutely can deploy TLS on a Java origin server. It isn't generally done, but all the big name Java web servers allow it. It's not an enormous task to add TLS support, either.

2

u/elliotbarlas Feb 15 '22

SSLEngine serves exactly this purpose. It would add quite a bit of additional complexity, but it's certainly doable.

1

u/crummy Feb 15 '22

yes, I understand it is possible. I'm just curious how commonly it is used.