.NET-JAVA debates again review 2002-02-25 · · Brooks ··
For many financial institutions, this J2EE-.NET problem may still be resolved when they deploy internal or purchased solutions in these platforms in a few years. Obviously, leading companies, such as JP Morgan Chase & Co., Bank One Corp., Wachovia Corp. and Suntrust Banks Inc., and many other large financial companies will have their own conclusions, and Microsoft, The .NET plan will become a crucial partner in their corporate information technology strategy. These institutions are based on Microsoft technology, allowing some of the security Internet bank sites for maximum capacity.
Sun Microsystems want you to think that from its numerous J2EE developer implementation, one of them will give you a wider, more "open" option. At the time of fact, J2EE specification is just a specification. Therefore, for extensions, and ultimately is open to interoperability.
When you choose a J2EE developer, start using its extended feature set (J2EE developer uses them in a fierce competition, you will lock yourself to this developer.
Mr. Piper, doing your own things - we must start comparison between the advantages. Appropriate comparison is to compare .NET Framework with a specific J2EE implementation, rather than comparing with a very small specification. Java provides the idea of Java is apparent to the J2EE market with 67% of the J2EE market together with BEA Systems Inc.. IBM has recently issued a 268 file that describes the steps to transfer applications from non-IBM WebSphere J2EE servers to WebSphere to further explain "developers neutral" is a myth.
In the era of performance and scalability, when responding to the industry standard server reference (such as different TPC metrics), it is worthwhile to use non-Java solution to use non-Java solutions. .
Mr. Piper said that the Java and J2EE specifications are designed for large machine size, while SUN's own reference application .NET version (a virtual e-commerce website) is 6.6 to 7.6 times . Worse, Enterprise Java Beans have not yet provided reuse or scalability commitments. A GIGA analyst has recently said that some Java developers who are discouraged for "Performance issues around J2EE around the database", at least if the J2EE is not allowed to continue to improve, can you consider new .NET technology more seriously in the future. .
Piper students also refute that J2EE provides more choices. Although Sun may claim that Java is a standard, Java is still controlled by SUN Microsystems.
Java has not been submitted to an internationally recognized standard group, so Java is just a standard compared to other widely used languages, such as Visual Basic, is just a standard.
Unfortunately, any developers designed on the J2EE platform have a language: Java. Millions of developers have been familiar with Cobol, Basic, Perl, C and Java languages, while the .NET platform supports these languages.
Mr. Piper said that Java will allow banks to run applications in numerous operating systems. Whether the bank is willing to retain a variety of different operating systems, and try to maintain the relationship between many different channels? In this scenario, Java will definitely promise "writing, debugging everywhere (Write Once, Debug Everywhere". The bottom line is, Java and J2EE are targeted by the application of applications between different platforms. Microsoft's .NET's application set between XML platforms using industrial standards becomes a goal. These two methods are different in philosophy.
We believe that the key customer needs are optimized for a particular platform, but it is also necessary to integrate with applications running on different platforms.
We feel that .NET provides a very simple, more decent development model, and developers using .NET and Voyager platforms, developers who use .NET and Voyager platforms will continue to provide higher performance applications for electronic finance, and at the same time Earth reduces their development time.
