New Year's expectations of a Java architect

On the last day of the end of the year, I am excited about God and hope that the Java Community in the coming year will be a little angry to realize our little wishes...

1. Java 7.0 released

Java7.0 attracts architects in the following places: the garbage first garbage collection algorithm, nio2 merge, and the fork-join framework of the concurrent package.

Garbage first is similar to the BEA jrockit sort algorithm, which replaces the CMS algorithm with the original pause time priority and provides a fixed garbage collection time-for example, barely acceptable 20 ms. Architects can finally rest assured that the system will not pause for two seconds.

The good news is that we may not have to wait for jdk7. the beta version of the G1 algorithm is already in jdk6.0 update14.

2. WS-I basic profile 1.2/2.0 released

WS-I basic profile profiles
It is actually the most important protocol in WS. The original design was a unified and interconnected WebService. With the expansion of the WS-* standard and the expansion of various WebServices
The arbitrary implementation of Library has already been messy. While WS-I basic profile re-provides a basic interoperability guarantee for this chaotic world.

WS-I basic profile 1.0 defines only the most primitive standards of soap 1.1, WSDL 1.1, HTTP 1.1, XML schema, and 1.1 adds attachments profile 1.0.
In 1.2, MTOM 1.0 (attachment protocol) and WS-Addressing 1.0 (asynchronous message) will be added, 2.0 will be upgraded to soap 1.2, and basic security profile authentication will be added, it should already be able to form a sufficiently harmonious Web Service world.

Of course, the specification is only a specification, and more importantly, the mainstream WebService libraries focus on its support, rather than spending time on the WS-* few other users.

3. glassfish V3 released

In open-source application server, glassfish community is becoming more and more popular.

Vv2 has an easy-to-use and Chinese-speaking management console and convenient cluster management. V3. it is even more excited that you do not need to load useless modules such as EJB and JMS when starting osgi quickly.

4. Release of netbeans 7.0

Everyone is getting bored. Eclipse only implements a Java ide + plugin platform. The Java EE version is not available until eclipse 3.4,

The Integrated Design of netbeans plugin gives everyone a relatively smooth feeling of javaee development. After version 7.0 supports Maven and a series of improvements, netbeans should be an option for everyone.

The good news is that the version of netbeans 7.0 is changed to netbeans 6.7, so it should be released faster.

5. Better ESB Solutions

The old mule idea or some commercial solutions have never been completely satisfactory.

For the time being, the fuse ESB 4.0 benchmark (ServiceMix 4.0 + camel) and JBoss ESB benchmark of inoa are promising.

I have developed the SCA standard license and Tuscany license for many years. I also hope that there will be real cases for you to understand its usage.

6. A better Java remoting call Solution

Since ejb2 is not the perfect choice, the efficient distributed synchronous calling scheme has always been the most embarrassing thing for Java architects.

I personally feel that the future solution should be simple and natural support for the cluster's HTTP protocol + a certain efficient data format, but either Hessian protocol or Google protocol buffers protocol, the key is to form a factual standard.

7. Popularization of osgi Technology

In the Application Server field, osgi has been fully promoted. Today, not all osgi application servers are embarrassed to say hello, for example, glassfish3 relies on Apache Felix plugin, and spring DM server relies on Eclipse equinox plugin, however, I don't know when this trend will go into the development of common application products.

8. Popularization of distributed computing and distributed storage technologies

One or two open-source projects, such as hadoop ghost and gridgain ghost, cannot meet the needs of Web websites to build their own distributed computing and storage platforms.

9. Java and Dynamic Language

When Java is slowing down, it is a new development direction to deliver business logic to dynamic programming.

Spring bought the groovy development/grails development support company g2one. sun stood behind jruby development and Jython development, and supported dynamic languages by Java 6, spring 2, and netbeans IDE, the technical preparations have almost been completed, waiting for whether this trend can actually be detonated.

The only slow one is Jython. The stable version is equivalent to Python 2.2.1, while many Python projects such as Django require python 2.5.

10. Others

It seems that there is no expectation for spring, javaee, rest, Ajax, and RIA. Alas ....

In addition, we also hope to have a better distributed cache solution for Java. terracotta plugin is not actually a silver bullet, and Oracle coherence plugin does not have a free version.