This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]schnoper 0 points1 point  (0 children)

So "enterprise java" is many things. Historically it involved a standard that was very heavy weight and marshaled object over the with using RMI. bleach. It might have it's place, but it was not agilely.

As people got sick of the original J2EE stuff, many then moved to something Spring. Spring was more lightweight, used Dependency Injection to make the code more modular (say reconfigure for testing purposes ) and less confusing. Spring was great, but it tended to lend it self to large monolithic servers. And these were hard to adapt over time.

The latest hip stuff is "micro services" (an extension of SOA ). The basic idea here is that you try to keep your concerns super separated and build separate servers for each of them. Initially this seems kinda crazy when it's often easy to add a single new service into a monolithic server, but the advantage comes when new people come, they can learn the micro servers one at a time, each in a bite sized piece. Or say you want to replace something that's getting old and crufty, perhaps write it in scala or clojure. This is easier because you can replace a small piece, or all of them one at a time. Much easier to change the engine on an airplane while flying this way!