.NET really defeated J2EE? Can it?

zhaozj2021-02-16  81

.NET really defeated J2EE? Can it?

Let's take a look at what is the advantage of J2EE and .NET.

BY Budi Kurniawan

The Middleware Company (TMC) is a company engaged in Java training and consultation, due to a controversial report published in October 2002, a controversy of J2EE community. This Report Contained Benchmark Tests on J2EE and Microsoft .NET Framework seems to be in implying .NET is better than J2EE (such as mentioned .NET applications more easily upgrade, can build and configure less time, And less code used than J2EE procedures.) This has caused strong protests of Java associations, especially those who have pointed out that Benchmark should have been prompting at some time. I will not participate in these claims, I only hope to be able to compare these two technologies objectively.

The base is that TMC spends great efforts to study results, but its results are not so ideally. The TMC initial plan is to prepare a fair test between the two platforms, but eventually, because only contact Microsoft does not contact the BEA, IBM, Sun, and other J2EE members to make this plan Forced interrupt. The later results show that Microsoft is the investor of this test.

The public also found that TMC invites Microsoft experts to configure and debug the .NET Framework for the baseline, but did not seek any suggestions to J2EE. Perhaps TMC believes that it is already an expert in J2EE field (it has published two highly praised EJB books), just as it claims to be on its website. Regrettably, it is quite unexpectedly, it does not implement it according to the best practices I recommend. (You can find the analysis made by Rickard Oberg in www.dreambean.com/petstore.html.)

Let us put political and money on one side. Does the .NET Framework be defeated as J2EE when it is released last year? So far, this answer is not known, waiting until TMC re-guiding a test including Microsoft and J2EE authority certification. However, here I want to point out a few reasons for the J2EE community need to treat .NET - I said to treat it more seriously. First, let's take a look at the advantages of J2EE to overcome Microsoft .NET:

Due to a wide range of libraries, Java's language and technology are more mature and have been tested, this Microsoft has to spend a few years to catch up.

Java is the earliest commercial language (it is earlier than Visual Basic .NET).

Many compilers and programming language studies in many times have also used Java, and the results of these research projects directly improve Java's social popularity. For example, IBM has used Just-IN-TIME (JIT) preferred method (Optimization) completed by JIKES JVM and its compiler. And .NET is also very new, so only Microsoft is studying alone. But this situation will soon change.

More Java open resource projects are users who don't have to spend too much cost, such as Tomcat Web Container, and Jonas EJB servers. These products often demonstrate that Java is a small, budget limited company's best choice.

However, no one is able to underestimize Microsoft (ask SONY more worrying Xbox). These factors will prove that .NET is faster than J2EE:

.NET is running in a Windows platform, compared with other products, it is a high location in Microsoft products. Engineers engaged in .NET can access the details of the operating system, so debugging them is very easy to debug them. Any enemy between J2EE .NET is going to work on Windows because .NET is not really portable. However, for the J2EE program server, Windows is only a black box. Microsoft has proven its success in chasing new technologies. With only one year, .NET Framework's performance has been able to compare with more mature J2EE. .NET also implements new technologies that have not been implemented, such as caches and server-side components. In the ASP.NET page, you can implement a cache only to write a line of code, so you can greatly enhance performance. Conversely, there is no definition of cache in the Java specification. Java developers have to write code or use a third-party tool to achieve a cache, such as using Jakarta Taglibs Project. Moreover, .NET contains GUI server-side components when they first released last year, while Java will contain these components in the future JavaServer Faces version, but this will be later than one year after this technology. .

Many Java Web technology has not yet formed standards, such as Struts, which is recommended by medium and large Java web applications. It is very common, but it is not used as a standard. So no one can guarantee that this universally used technology will not be replaced by a new standard of later. For those who first tried to choose a server-side technology, this is especially confused. And Microsoft is different, it supports all REDMOND issued.

J2EE has considerable participants. This will encourage more innovations, and many efforts are excessive. For example, BEA and IBM can study the same R & D, which result in the same enhanced performance, if they participate in competition, then they will have developed faster. But this is not necessarily realized in business competition. Even members of the members in the open resource are sometimes competed (including JBoss and Jonas, Tomcat and Jetty). On the other hand, all .NET programs are managed by Microsoft, so there is no redundancy.

The new Java specification is drafted by many partner companies and individuals in a virtual democracy. Of course, even minimal participants can make their own ideas, but they are usually a time-consuming long process. Microsoft's new technologies are drafted by some groups, they can make decisions faster. Microsoft has proven that its speed is quite fast in realizing new technologies.

Indeed, according to the development speed of .NET Framework, I am afraid that the J2EE community is still behind.

About the Author:

Budi Kurniawan is an IT consultant that he specializes in Internet and object-oriented programming, teaches Java and Microsoft technology. He is very good

Java for the Web with servlets, JSP, And EJB; A Developer's Guide To Scalable Solutions (New Riders) Author, he also developed the most popular Java Upload Bean, you can

BrainySoftware.com gets it, many important companies have licensed and used it in the project. Budi contact information is

Budi@brainysoftware.com.

转载请注明原文地址:https://www.9cbs.com/read-14290.html

New Post(0)