Internet banking: Choose. NET or Java EE?

J2ee Internet Banking: choose. NET or Java EE? (2002.02.25) From: CSDN
from: "American Banker", the author is Corillian company Chief Technical Officer (CTO). Although the article focuses on internet banking, the. NET vs. Java advantages are discussed.
Opinion/Controversy
View:. Net-java the debate again; support Microsoft side counterattack
Friday, January 25, 2002, author Chris Brooks
On the January 11 point of view article "in terms of platform advantage, Java is a better choice than. NET (for a Platform Edge, Java is Better Choice than. net)", Eontec Colin Piper the old Microsoft Company vs. Debate between the Ibm/sun Microsystems.
For many financial institutions, this j2ee-.net problem may still be unresolved when they deploy internal or purchased solutions on these platforms within a few years. It is clear that the leading companies, such as J.P. Morgan Chase & Co., Bank One Corp., Wachovia Corp. and SunTrust Banks Inc., as well as many other large financial companies, will draw their own conclusions, while Microsoft, using its. NET plan, will become a vital partner in their enterprise information technology strategy. These institutions are building on Microsoft technology to allow some of the largest-capacity secure Internet banking sites.
Sun Microsystems wants you to think that choosing one of its many Java developer implementations will give you a broader, more "open" choice. In fact, the Java EE specification is just a norm. Therefore, for extensions, and ultimately for interoperability, it is open.
When you choose a Java EE developer, you start using its Extended feature set (the Java developers use them to differentiate themselves in the fierce competition), you lock yourself into the developer.
Mr. Piper, do your own thing-we must begin to compare the merits. The appropriate comparison is to compare the. NET framework with a specific Java EE implementation, rather than with a specification that is of minimal value. When faced with the International Business Machines Corp. and Bea Systems Inc., which occupies 67% of the Java-EE market, the idea of providing options is clearly flashy. IBM has recently released a 268-page file that describes the steps to move applications from non-IBM WebSphere Java-EE servers to WebSphere, further explaining that "developer Neutrality" is a myth.
In the era of performance and scalability, when responding to industry-standard server benchmarks (such as different TPC metrics), it is worthwhile to mention that IBM, Sun, and Oracle companies use non-Java solutions to tout their product performance.
Mr. Piper said the Java and EE specifications were designed for mainframe-scale computing, while the number of concurrent users handled by Sun's own reference application, a hypothetical E-commerce site, was 6.6 to 7.6 times times as many. Worse still, the Enterprise Java beans has not yet provided a commitment to reuse or scalability. A Giga analyst recently said that some Java developers frustrated with "Java EE's performance issues around database access" were at least considering whether the situation could be more serious in the future if the condition of Java EE did not continue to improve. NET technology ".
Piper students also retort that the Java EE offers more options. Although Sun may claim Java as a standard, Java is still controlled by Sun Microsystems.
Java has not yet been submitted to an internationally recognized standard group, so Java is simply a standard compared to other widely used languages, such as Visual Basic.
Unfortunately, any developer who designs on the Java EE platform already has a choice of language to choose from. Millions of of developers are already familiar with COBOL, Basic, Perl, C + +, and Java languages, and the. NET platform supports these languages.
Mr. Piper says Java will allow banks to run applications on many different operating systems. Are banks willing to keep many different operating systems and try to maintain customer relationships in many different channels? In this scenario, Java will certainly promise to "write once, debug everywhere (write once, debug everywhere)".
The bottom line is that Java and EE are targeted for application portability between different platform views. Microsoft Inc. 's. NET is targeted at application integration between XML platforms using industry standards. The two methods are different in philosophy.
We believe that critical customer requirements are optimized for performance and portability for a specific platform, but are also ready to be integrated with applications running on different platforms.
We feel,. NET provides a very simple, more appropriate development model, compared to Java, use. NET and Voyager platform developers will continue to provide more high-performance applications for e-finance while significantly reducing their development time.
Mr. Brooks is the chief technical Officer of Corrillian Corp., an internet banking software developer based in Oregon State.