Microsoft and Sun's battle have been continuing, everyone has advocated their own technology is the best solution, but there is no difference in winning. The current competition is mainly concentrated in .NET architecture and J2EE architecture. Net and J2EE hopes to occupy more markets in the development of Web Service. But no matter how they advocate themselves, .NET and J2EE do not exceretively complete the basic business functionality of establishing Web Service. Each of them can be better applied to a certain business, or a certain group, or even a group. Therefore, companies can use both technologies to be used, rather than only like usually one.
Ancient language: all ends are both ends, such as small and thin. In the good, he is on both ends, and the metric is taken, and then it is used. Then we will measure .NET and J2EE from the angle of the demand for the web service.
We have always been in a variety of technologies that integrate each other, although this environment is not easy to maintain. In addition, Web Service is susceptible to integration and providing a complete supply chain that makes us more inclined to accept this fusion. Of course, it is still a problem that the web service is still applicable to the company. Although there are a large number of demonstration projects and more research expectation Web Service's joining, we still need to confirm that it can deal with intensive transmission and multi-function commands in the enterprise, and even provide supply chains. Although Web Service is powerful in data exchange and providing remote query, it is not so effective in programs that need to use continuous sessions without making data loss. In addition, XML Schema and other dispute criteria are still in progress.
It is also worrying that the beautiful future of Web Service is bleak due to the private weight of each supplier. Web Service is usually defined in J2EE and .NET, which means that the supplier is working hard to add a layer of outer packaging to the Web Service to make the third party can use it in its own core technology. This will cause the supplier to generate differences in the support of the Web Service standard, just like the case of ODBC's first occupation of the market for 10 years ago.
According to this statement, the Web Service promises will be widely used in the near future. During this period, the company should consider combining .NET and J2EE, regardless of the investment of Web Service. Enterprises are always unwilling to invest in those who have not been confirmed. We should want to see the scene of the previous technology, such as
Combined with .NET and J2EE, and Web Service gradually joined with demand increases and standards, especially from the current situation of currently invested E-Business. This may not be what we hope, but from the following reasons, the situation is not so bad.
J2EE and .NET have powerful built-in integration. J2EE provides J2EE Connector Architecture (JCA) that is able to integrate Siebel, Oracle, SAP, and other enterprise applications in a Java development environment. JCA is almost supported by all major suppliers, and it details how to build adapters that connect existing systems. Therefore, Microsoft defines many standards for current integration technologies, such as ODBC and OLEDB, and continues to provide tools such as BizTalk Server, Host Integration Services, and Data Transformation Services to use in different types of integration technology. Enterprises can also get adapters that are easy to integrate technologies from most third party vendors. This adapter simplifies integration techniques through smart reducing or even eliminating custom integrated codes.
In the end, future companies will be more characterized by using integrated technology and using J2EE and .NET combined with the previous application. So what should we do? It is said that it should stop the dispute. Each supplier is promoting its own Web Service solution, however, its performance, security and other issues still need a practical test. Next, you must prepare for the inevitability of tensions between J2EE, .NET, and pre-application. It should focus on the enterprise's front desk and background homework and supply chain integration technology. It is necessary to face the market competitiveness of J2EE and .NET to coordinate the development of technical devices, existing basic construction, tools and industry support. Enterprises will not only use one technology, which means that due to the popularity of Web Services, the future world will be as complex as existing environments.
Finally, we must decide where Web Service can use its maximum utility. Where to implement the Web Service project, whether it is based on J2EE or .NET, so that the Web Service is more standardized. In addition, you need to decide how to re-build relationships between business processes and supply chains, which uses the new features of Web Service.
Editor: Standing in the perspective of demand, we have seen the Web Service, there are many options, when choosing, the most important indicator is not the technical itself. China's doctrine can give us an enlightenment. The need for IT technology is not a single independence, in the ocean of many technologies and products, is the most critical.
Source: PConline
