Java EE 6 and Developer Productivity
One of the things I like is the focus on lightweight development with WebLogic Server. There is a 2X-6X download size improvement for developers, no installer, unzip and go on Win/Linux/OSX. The zip distribution is down from 318mb on the 11g zip distro to 168m on the 12c zip distro. You can start an instance with -Dservertype=wlx to launch without EJB, JMS, and JCA containers.
One good thing is how Java EE6 makes it possible to write less code and less XML. Less is better for at least three reasons:
- Less coding means less time, means less cost
- Less lines of code or XML means less potential bugs
- Less code could improve performance
In a sample application from JavaOne showed Java Classes 25% less, Lines of code 50% less, Lines of XML 80% less. This is interesting!
Other keywords are: JSP 2.1, JSF 2.0, EJB 3.1, JPA 2.0, Context and Dependency Injection and Restful Web Services, Maven support
Integrated Traffic Management
I had hoped that Oracle Traffic Director also would be available also outside of Exalogic, but this seems not to be the case at this time. WL 12c is integrated with Oracle Traffic Director which does routing, load balancing and traffic shaping. It has fast, highly-configurable request routing and caching of dynamic content. It can achieve up to 3.5X more throughput and 28% lower CPU than Apache. Traffic Director can on the fly discover new available WL servers.
Much Higher Performance
The presentations show good numbers on performance improvements: WebLogic Server: #1 in Performance. New world records september 2011: Multi-Node Overall EjOPS: 2.4X more workload than IBM. Overall EjOPs per Processor: 56% more workload than IBM. Overall EjOPS per Core: 50% more workload than IBM on identical hardware.
There is a seamless upgrade from WL, iAS and others. iAS has automated tooling, WL11g has a simple upgrade, Glassfish needs a simple redeploy, and JBoss has migration services. For iAS customers you can upgrade for free (no license cost) to WebLogic Basic.