Keeping up with the blazingly fast-changing landscape of front-end engineering and Javascript can be challenging. From build tools to full-blown frameworks, we are spoilt for choice – and sometimes bewildered by it. Determined to cut through the noise and be a guiding light, Web Directions Code...
Node.js has impressed me several times with high performance right out of the box. In my last Node.js project it was the same: we beat the given performance targets without having to tweak the application at all. I never really experienced this in Java EE projects. Granted the project was perfectly suited for Node.js: a small project centered around fetching JSON documents from CouchDB. Still I wanted to know: how would Java EE compare to Node.js in this particular case?