Java EE VS. NET Platform: Difference analysis

Java EE and http://www.aliyun.com/zixun/aggregation/13480.html "> NET platform Similarities

Figure 2 shows all the similarities between the Java EE and the platform. As you can see, many. NET platform features no corresponding function in Java EE. In some cases, as to whether or not to support these features, if supported, what is considered a clear decision to make, note: To understand unfamiliar abbreviations, look at the glossary.

Figure 2. Technical correspondence

Technology. NET Java Support Technology Publishing protocol DCOM, SOAP IIOP firewall isa* not defined-HTML page cache isa*, asp.net no presentation layer technology infrastructure II S does not define program design model asp.net Servlets, JSP high-availability nlbs*, acs*, other not defined load balancing nlbs*, acs*, other undefined admin acs* does not define middle tier technology base Infrastructure COM + EJB programming tools Visual Studio.NET not defined-high availability acs* does not define load balancing acs* does not define security API COM + Secure call context JAAS Message Queuing API M SMQ JMS 1.0 Asynchronous Component Queued (COM +) message driven beans (EJB 2.0)-Naming and directory services ADSI JNDI data-tier technology distributed transactions MS-DTC JTS number of relationships According to the Library API ado.net JDBC 2.0 hierarchical database API Ado.net-database storage sqlserver**-Mainframe database Connectivity his* Java Connector Architecture Technology E-commerce architecture Commerce Ser ver*-business-to-business BizTalk server*-

For. NET platform is an optional add-on service.

* * SQL Server is a formal. NET Platform database technology, but you can use any database that supports ado.net, including most databases.

The difference between Java EE and the. NET Platform

You can see that there is a big overlap between Java EE and the. NET platform technology. But how do you choose between them? In this section, the author will discuss the major differences I have seen.

Developer Neutrality

Many companies buy Java EE, which they believe will give them a neutral position as a developer. In fact, this is a set goal of Sun's plan:

It is possible to configure and implement a variety of products that meet the requirements of the Java EE specification. A portable Java EE application can run correctly after it has been successfully deployed in any of these products [12].

In fact, few people who are not rivals of sun-Java are convinced that this is achievable. Paul Harmon is one of the most important independent EE speakers, Cutter Consortium's chief advisor and author of a widely distributed Architecture/e-business e-mail advisory. Although Harmon is always against Java EE, he recently wrote an unusually candid comment on the portability of Java EE developers.

Has the EJB model reached the point where I can move an EJB component from one EJB application server to another? Not in most cases. The EJB specification is not comprehensive enough. By providing proprietary solutions to improve the model and ensure that their customers can create production systems, EJB Application Server developers make up for this. [13]

Harmon summed up the current situation of developers neutrality, his comments are as follows:

Now, the reality is that if you want to develop an EJB application, you should be loyal to a developer. [14]

The reality today is that there is no such thing as a developer neutrality. Of course. NET platform is not a developer-neutral, it is bundled with Microsoft's operating system. But neither is the realization of the Java EE. The best advice I can give is to choose a developer and plan to stand with it all the time, so that you can take full advantage of the platform that the developer offers.