4 ms·
This is something I do not understand with java as a webserver - doesn't such behavior show a major design problem? "Lots of traffic" can be expected by any we
by softwarelimits 9y ago
This is something I do not understand with java as a webserver - doesn't such behavior show a major design problem?
"Lots of traffic" can be expected by any webserver software - handling "too much" of it in a not too painful way could be a design goal. Just spitting out an error on such a condition and making the site disappear is a little bit too simplistic for my taste.
I have seen this error on sites with java webservers many times - is this an accepted limitation in the java world?
I am not trying to be snarky here, I have lots of respect for aphyrs work, but I am really wondering about this "normal behaviour" of java webservers - how can an "enterprise platform" get away with this?
- aphyr 9y agoThe jepsen.io server is literally something I hacked together in a few weekends. I wouldn't really point to it as an exemplar of high quality production-facing engineering. :) That said, it does push 50,000 reqs/sec on my local box, did just fine on an AWS m3.medium, then fell over today at 5 reqs/sec on a heroku "pro" dyno, so... this is something I'll have to address.
- sandGorgon 9y agoYou should switch over to using Hugo and generating static html for most of your site. Deploying it to Firebase CDN or Netlify should cost you a few dollars every month.
- wmf 9y agoPretty much no web servers or apps are tested to destruction probably because few tools can even generate good overload. It's just an industry in perpetual infancy.