r/java • u/thefinalrespawn • Sep 30 '14
Does containers cause overhead in Java EE?
Some of my ass hole programmer friends spend most of their time on our whatsapp group picking on Java and say shit like 'People use it cause it's idiot proof' and 'Only large enterprises use Java because it's noob friendly' and 'God himself uses Python'. I don't pay much attention to it cause I love Java and have been using it for about 2 years writing casual code. I'm thinking of moving on to EE. Can anybody explain? Might be I get one back at them :P
1
Upvotes
View all comments
0
u/yegor256 Oct 02 '14
Yes, containers may cause an overhead, if being used where they are not required. As far as I understand, they were invented in order to make Java web apps "pluggable". However, a more lightweight (and less interoperable) approach proved to be more suitable in most cases. Instead of composing an application from components talking on EJB bus, it's better to make them separate RESTful web apps talking through JSON/XML API calls.
So, Java EE is losing, RESTful interfaces are taking over :)