Integration Technology:. NET Single-choice J2EE

Statement:ArticleSource network. The copyright belongs to the original author.

[It168]I don't want to compare the integration technology. In fact, all developers understand the truth. Microsoft's Development Platform naturally has the advantages of integration. In fact, there is no need to fight, the battle is clear ,. net is famous, it won in this battle, I think many people will not hold too much ambiguity, so let's take a look. net is better than J2EE in what aspects.

Although I am a Java enthusiast, over the past three years of Java Development, it has given me a lot of happiness and gains. At least in my life, I can use it to make a living, but today, I have to leave some praise to me. net, because I like Microsoft's architecture very much. When I was using VB for development, I was amazed at Microsoft's Integration Technology and API, it provides you with clear solutions and ideas, and is easy to understand.

. Net Integration Technology

In the past, Microsoft's architecture was only based on COM/DCOM, and COM/DCOM was the binary standard for inter-process communication. Although there is no mistake in this standard, it is out of line with fields other than Microsoft. That is to say, this standard has become a bottleneck between integration with other software platforms.

In addition, database operations are also a problem. Although ADO simplifies data access, it becomes a problem to transfer data from one place to another. Ado recordset) an object is a binary structure that stores data. This binary format has no significance for non-Microsoft platforms.

. Net makes up for these defects because it is fully based on standards. For example, the data is in XML format through the process boundary, and the data has a connection to XSD, so any client can convert the data correctly.

At the same time, the. NET integration technology is fully reflected in WebServices. (Soap-based WebServices is Microsoft's innovation, derived from Microsoft's Simple Object Access Protocol, or soap)

. Net regards WebServices as the only integrated solution, so we can use it very simply. Using WebServices in. NET is like using APIs in other core languages, such as strings or collections.

. Net is incomparable to any development platform. It can be organically integrated with Microsoft and many non-Microsoft related products, able to develop more optimized products.

J2EE Integration Technology

Java (or J2EE) provides more extensive and complex integrated APIs than Microsoft. Every Integration Technology J2EE you can think of in an enterprise has a corresponding API.

In J2EE, the most important APIs are JMS and ejbs. JMS is a unified interface specification for message-oriented middleware, and multiple EJB applicationsProgramIs still frequently used in different tasks.

In J2EE, there is also a simple remote object specification RMI-IIOP, And the JCA adapter Technology for connecting Java programs to non-Java programs and software packages and middleware, where Java programmers can indirectly access the JDO specification of the database, j2EE has not abandoned WebServices at the same time, which may be the most lengthy WebServices API-Jax-rpc I have seen.

In general, J2EE has a lot of APIS, but a few of them are used in development, and many APIs make you feel very troublesome.

Summary:

If you have an integration problem, which of the two competing technologies will you choose as a solution? Unless you can control the server environment from every possible aspect, J2EE is your best choice.

The above is my personal feeling. In this regard,. NET is more transparent and Its WebServices are more smooth.

But we know that enterprise integration businesses are usually very diverse, and enterprises generally do not let everything run on Windows server, but may include a combination of Solaris, Linux or HP-UX and other systems, these situations may affect your choice.

Therefore, the specific platform should be determined based on your actual situation and cannot be generalized.

Source: http://tech.it168.com/j/n/2006-11-30/200611300816690.shtml