Re:Oracle’s Java 11 trap
by riku_iki on Wednesday September 26, 2018 @03:57PM
(#18079662)
I think the premise of JEE is that you label your class by @SessionBean annotation, and everything is installed automatically for that class: RPC, load balancing, security, monitoring, and you don't need to shop for individual components and find the way how to glue them together.
How this premise is implemented is another story. I am not sure about quality because didn't use jee for last 10 years, but when I was using it, IBM stack was far ahead of everything on the market, and was like your private PaaS with cloud functions, but with high license fees of course.
[ Parent
| on HN ]
That sounds good. I wonder how it is implemented, though. I read through the WildFly feature list and there are several features you mention, such as clustering or failover. I wonder how you get to bridge the gap from the application to the underlying infrastructure, though.
EDIT: I see from the docs http://docs.wildfly.org/14/High_Availability_Guide.html that you need to configure an Infinispan cluster, what looks like a non-trivial operation.
Re:Oracle’s Java 11 trap
by Aaargh20318 on Thursday September 27, 2018 @10:40AM
(#18084935)
Paraya uses HazelCast for clustering by default. IIRC all it needs is for the servers to be in the same network.