Analysis of Java EE and Windows DNA architecture from a commercial perspective

The following sections discuss the commercial benefits of using EJB and Java EE for comparison with COM + and WINDOWS DNA.

1. Industry support

Any commercial technology to have a good market situation, the industry's significant participation of important enterprises is very important. Java EE is led by the Sun, the manufacturers jointly launched, and has been widely recognized industrial standards. In the industry ' enterprise computing ' field of large enterprises such as: IBM, BEA Systems, Oracle and so are involved.

The participation of suppliers in the Java EE specification phase allows them to absorb the experience they have experienced over the years in the field of enterprise computing and to facilitate their rapid development of the Java EE products. Because of the above strategy, there are now more than 25 different server-side platforms supporting the Java EE specification.

Due to the adoption of open collaboration to develop norms, Java EE also embodies a large number of enterprises in the field of computing suppliers knowledge and professional technology. This means that a product solution can meet any business requirement. With a large number of vendor support, users will have a wider range of choices.

In contrast, the WINDOWS DNA architecture was developed and completed by Microsoft alone. If a customer chooses this proprietary architecture that is not widely supported by the industry, it will limit them to the technical implementation of one vendor. This prevents customers from using other vendors ' products in the future, and these products are likely to be best suited to the specific needs of an enterprise.

2. Protect existing IT investments

Since companies must adapt to new business needs, it is important to make use of existing enterprise information system investments rather than to redesign the overall programme. In this way, a server-side platform mechanism built on existing systems in a progressive (rather than radical, total negation) manner is what the company needs.

The Java EE architecture can take advantage of the user's original investments, such as Bea Tuxedo, IBM CICS, IBM Encina, Inprise Visibroker, and Netscape application Server used by some companies. This may be due to the extensive industry support of Java EE and the involvement of some of the key ' enterprise computing ' domain vendors. Each supplier offers existing customers a way to upgrade to a portable Java EE area without having to invest in obsolete investments. The existing operating system and hardware can be kept in place because the Java-EE platform's products are almost capable of running on any operating system and hardware configuration.

The three benefits of Java EE's ability to retain existing IT assets are as follows:

Applications can be exploited

Existing code can be reused in the Java EE scenario, and an application can be reclassified without rewriting. This reduces development time, accelerates the pace of market entry, lowers development costs, and keeps the project at a reasonable budget level. This also lowers the risk of the business because the company can use the programs that have been validated and worked on, rather than removing the existing systems from being rewritten.

Existing products and use license agreements can be used

If a company has already purchased certain licensed protocols or maintenance protocols, such as middleware, operating system, or hardware, that have acquired some existing technologies, these licenses can still be used in the Java EE environment. Therefore, it can reduce the project cost and shorten the training time.

Less reliance on vendors

Because the provider you are serving is a product for the Java EE platform, there is only one vendor, and you do not need to rely on the help of two vendors to establish a connection between their products. This reduces the complexity of the application and lowers the overall risk level.

In contrast, Microsoft's Windows DNA architecture requires customers to purchase and install Windows 2000, and may require customers to purchase new hardware. Customers will not have the opportunity to use the original vendor's license or maintenance agreement to increase the cost of the project.

We should also see that Windows DNA does provide a connection to a user's existing system, but customers use this connection to rely on two vendors: Microsoft and the supplier that is now offering you a product. A solution that uses only one vendor is usually more manageable and reliable than a two-vendor connection scenario.