• Published on

  • View

  • Download


<ul><li><p>.NET vs. J2EEBATTLE OF THE TITANS&amp;A PERFORMANCE CASE STUDY</p><p>Jagadeesh Danala</p></li><li><p>ReferencesThe great debate: .NET vs. J2EEhttp://www.javaworld.com/javaworld/jw-03-2002/jw-0308-j2eenet_p.html </p><p>Comparing J2EE with .NET part 1 &amp; part 2http://internet.about.com/library/aa_netJ2EE1_080702J2EE and .NET (RELOADED)Yet Another Performance Case Studyhttp://www.middleware-company.com/casestudy/ The W3C definition of Shared context. http://www.w3.org/2001/03/WSWS-popa/paper29 </p><p>Jagadeesh Danala</p></li><li><p>OverviewBasic truthsJ2EE.NETJ2EE and .NETComparing J2EE with .NETPlayersLegacy Integration and Backwards CompatibilitySingle vendor vs. Multiple vendorThe language factor</p><p>Jagadeesh Danala</p></li><li><p>OverviewComparing J2EE with .NET (contd..)Web services supportShared contextPerformance case studyTests conductedCodebases usedResultsSummaryConclusion</p><p>Jagadeesh Danala</p></li><li><p>Basic TruthsJ2EEJava-centric and platform-neutral</p><p>J2EE is not a product you buy from Sun.</p><p>J2EE is a set of specifications each of which indicate how various J2EE functions must interoperate</p><p>If I dont buy J2EE from Sun, how does Sun make money?</p><p>J2EE 1.4 released with features to completely support web services JAX-RPC 1.1 API, J2EE Management 1.0 API, web service endpoints etc.</p><p>Jagadeesh Danala</p></li><li><p>Basic Truths.NETWindows-centric and language-neutral</p><p>.NET is a Microsoft product strategy that includes a range of products from development tools and servers to end-user applications.</p><p>Plans to make .NET platform neutral are in progress,Mono the open source implementation of the .NET development environment, being the example.( http://www.go-mono.com )</p><p>Jagadeesh Danala</p></li><li><p>Basic TruthsJ2EE and .NETBoth accelerate and simplify business application development.</p><p>Web services technology development was aided by Servlet Technology which was developed in response to the ASP technology. So one begets the other, which begets the other, which begets the other, ad infinitum.</p><p>A J2EE application can invoke a service on .NET platform and vice-the-versa.</p><p>Jagadeesh Danala</p></li><li><p>Comparing J2EE with .NETPlayersJ2EE is being is a set of specifications produced by the Java Community Process which consists of Sun Microsystems along with the top software vendors such as BEA, IBM Oracle etc.</p><p>.NET is the sole effort of Microsoft with some backing from the open source community.</p><p>Jagadeesh Danala</p></li><li><p>Comparing J2EE with .NETLegacy IntegrationJ2EE supports Java Connector Architecture (JCA) and use of adapters that eases linking with legacy code.</p><p>.NET offers legacy integration with its Host Integration Server 2000 but with limited connectivity to select systems.</p><p>J2EE legacy integration features are superior to those found in .NET since JCA market is building a huge marker place of adapters to ease application integration.</p><p>Backwards CompatibilityASP.Net is now a full programming language environment compared to its script-based predecessor.</p><p>Visual Basic is finally Object-oriented in VB.Net which makes upgrading from VB 6.0 or later difficult.</p><p>Jagadeesh Danala</p></li><li><p>Comparing J2EE with .NETSingle vendor vs. Multiple vendorJ2EE tools often are not interoperable due to problems in portability. The reason being that they are not from a single vendor and hence not well-tested.</p><p>.NET provides complete solution of tools and services but which may lack some of the higher-end features found in J2EE solutions.</p><p>Jagadeesh Danala</p></li><li><p>Comparing J2EE with .NETThe language factor.NET framework based on CLR.A single .NET component can be written in any language.The above feature has two disadvantagesMaintenance is made difficult since we need experts in different languages to develop, debug and maintain a particular application.Negatively affects team productivity since best practices are hard to be shared among knowledge workersDevelopers of other languages like Cobol, Perl etc feel disenfranchised due to the single-language standardization of J2EE.</p><p>Jagadeesh Danala</p></li><li><p>Comparing J2EE with .NETWeb services supportJ2EE enables eBusiness collaboration and Web services through its JAXP (Java API for XML Parsing). </p><p>.NET lacks support for ebXML, which is fast becoming an international standard for eBusiness collaboration, making it a real problem for industry-wide acceptance.</p><p>Microsoft still pursues its own BizTalk proprietary framework with proprietary SOAP extensions.</p><p>Jagadeesh Danala</p></li><li><p>Comparing J2EE with .NETShared contextUsers dont need to type in their user names and passwords every time they use web services.</p><p>J2EE proposes a shared context that is specific to various industry areas to serve customer needs such as banking and finance, medical history etc. </p><p>.NET proposes to present a single shared context repository approach based on its Hailstorm services, which is user-centric and is risky in the context of security maintenance and dominance of a single entity over identity date of individual and businesses.</p><p>Jagadeesh Danala</p></li><li><p>Comparing J2EE with .NETCodebases usedJPetStore Demo 1.3.2 for J2EE-Servlets-JSP </p><p>Modified Java Pet Store named mPetStore for J2EE-EJB-CMP2</p><p>msPetShop for .NET-C#.</p><p>Jagadeesh Danala</p></li><li><p>Performance case studyTests conducted Web application test</p><p>24 Hour Reliability Test</p><p>Web Services Test</p><p>Case study performed by THE MIDDLEWARE COMPANY.</p><p>Jagadeesh Danala</p></li><li><p>Performance case studyResults Web Application Test</p><p>Jagadeesh Danala</p></li><li><p>Performance case studyResults Web Application Test</p><p>Jagadeesh Danala</p></li><li><p>Performance case studyResults 24 Hour Reliability test</p><p>Jagadeesh Danala</p></li><li><p>Performance case studyResults 24 Hour Reliability test</p><p>Jagadeesh Danala</p></li><li><p>Performance case studyResults Web services test</p><p>Jagadeesh Danala</p></li><li><p>SummaryWeb application testThe test results showed that both .NET and the fastest J2EE platform performed approximately the same. The J2EE solution was slightly better than the .NET solution (about 2%) when using Oracle 9i. When using Microsoft SQL Server, the .NET solution was slightly better than J2EE (about 11%). In general the J2EE implementations performed equally well against both databases . The .NET implementation performed almost the same as J2EE when using Oracle 9i and slightly better when using Microsoft SQL Server.</p><p>Jagadeesh Danala</p></li><li><p>Summary24 Hour Reliability testThe results of this test were that the fastest J2EE and the .NET platform performed almost identically, with less than 2% difference in performance.</p><p>Web Services TestThe results of this test showed that the .NET platform outperformed the fastest J2EE platform, by over 200%.</p><p>Jagadeesh Danala</p></li><li><p>ConclusionThe case study also finds thatFor enterprise applications, performance is important. But not all-important.Moreover the perception of the vendor as an enterprise company, conformance to standards, strength of the ecosystem around the product, the degree to which the product is a defacto standard among its class, stability of the product or technology, ease of use, IDE integration and other tools support, total cost of ownership (TCO), portability, scalability, and many other such factors often outweigh Performance.Hence the choice of the framework is best decided after taking all the above factors into consideration.</p><p>Jagadeesh Danala</p></li><li><p>Thank You!</p><p>Jagadeesh Danala</p></li></ul>


View more >