3 ms·
It is not Java. It is how people over engineer enterprise applications. - Annotations are overused. - Design patterns are overused. - Too many layers, too ma
by huherto 7y ago
It is not Java. It is how people over engineer enterprise applications.
- Annotations are overused.
- Design patterns are overused.
- Too many layers, too many abstractions.
- Using properties where a constants would be enough.
- Using concurrency when you don't need it.
Probably a cultural problem more than a technical.
- forinti 7y agoPrecisely! EJB used to be a nightmare (a lot easier now with annotations), but I would see people use them for web apps that had 10 users tops. It was insane.
- theandrewbailey 7y agoI barely remember how EJB used to be, though I recall that it involved a mess of XML and interfaces. Nowadays, EJB is a built-in dependency injection system. Put @Singleton on one class, then @EJB on a field in a Servlet (or what have you).