Which of the entire Java technology zoo should be used in your project?

Question

Java

I have been working with Java at the SE level for a long time. I used to write Swing applications, now JavaFX2. But it's time to take on EE. The goal is serious - one of the projects develops into something more than just a desktop application, and serious scalability is required.

I have been eyeing Java EE for a long time. I read docs.oracle.com/javaee/7/firstcup/doc/home.htm from cover to cover , experimented - I got the general idea. There are more practical questions. Which of the entire zoo of technologies should be used in your project? What is worth scoring as hopelessly outdated?

What technologies are currently used in "combat" solutions? JSP? jsf? Hibernate? I don't want to waste time learning something that is already outdated. There are practically no materials in Russian, and what is outdated for 5-10 years already. Examples which are given on a site orakla - are too divorced from a reality. Advise in which direction to dig?

Answer 1

Perhaps you will be satisfied with Jooq as an ActiveRecord and SQL constructor.
In most cases, EclipseLink, Hibernate, eBean, iBatis are pretty sloppy.
Particular attention should be paid to model caching - here ehCache rules the show.
You can use offheap caching - Apache DirectMemory.
Most CRUD can be described via restfull api, Swagger will help here.
Recently, j2ee has become synonymous with buggy and sluggishness.
You shouldn't rush without a good reason...
If you really want J2EE, you can try Grails, Vaadin, ZK.
I've been using Play2 + angularjs and partly AIR/Flex for quite some time now, very happy.
I advise you to consider switching to Flex for building interfaces.
AIR is great for mobile applications.

Answer 2

I would not advise messing with any jsf / adf frameworks, they are buggy and almost not customizable. Further, depending on the tasks, if you need a beautiful and functional client, then I would not recommend using ZK either (it has a rather cool client-server binding, which, unfortunately, is not deprived of bugs).
then. for the frontend, I would advise jsp, SpringMVC + possibly angularjs (depending on tasks).
For the backend - Spring, Hibernate or SpringDAO, Jax-WS, if you need speed and normal work with generics, I would not use it, I would advise you to get confused with trift then ( http://thrift.apache.org/ ). From the application server, most likely you don’t need anything, Tomcat (a servlet container) will be enough. Caching - yes, EhCache.
Good luck!