Docstoc

Quantitative Analysis of J2EE _ .NET

Document Sample
Quantitative Analysis of J2EE _ .NET Powered By Docstoc
					  Analysis of
J2EE & .NET
              Contents
 Background
 Goal
 Introduction of J2EE & .NET
 Library Service System
 Comparison
 Conclusion
Q&A
                 Goal

 Find out which platform is better
 Analyze the performance of J2EE
 and .NET

 Compare J2EE and .NET on various
 features
                  J2EE
 Java 2 Platform, Enterprise Edition
 Standards and specifications
 Sun Microsystems
 J2SE based
 Java language
             J2EE Framework

                         Client



                                        Java Connector Architecture
                                        (enterprise apps integration)
     Servlet /        EJB Container
  JSP Container     (Business Logic +     Java Message Service
(Presentation Tier) Persistence Tier)
                                                 Java Mail


                   Java Virtual Machine (JVM)


        Host Operating System (Unix, Linux, Windows, etc)
                                                          Framework


                       Client
                                                                          Presentation Layer – JSPs + Servlets


                                         Java Connector Architeture
                                        (enterprise apps integration)   EJB Container
     Servlet /        EJB Container
  JSP Container     (Business Logic +
(Presentation Tier) Persistence Tier)
                                          Java Message Service          Business Logic Layer – Session Beans
                                                                            Host Operating System (Windows)
                                                 Java Mail

                                                                           Persistence Layer – Entity Beans
               Java Virtual Machine (JVM)



 Host Operating System (Unix, Linux, Windows, etc)

                                                                                        Database
                     .NET
 Product strategy
 Microsoft
 Many Languages
   e.g. C#, Visual Basic, C++
         .NET Framework
                        Client


.NET Framework

                  ASP.NET / Window Form


                 Framework Class Libraries


            Common Language Runtime (CLR)



            Host Operating System (Windows)
                                   Framework

            Client
                                     Web Server
                                      Presentation                ASP.NET
.NET Framework                           Layer
     ASP.NET / Window Form


    Framework Class Libraries        Application Server
                                      Business Layer       .NET Managed Class
 Common Language Runtime (CLR)

                                       Data Layer                 ADO.NET
 Host Operating System (Windows)


                                                       Database
   Library Service System
 Acts as a benchmark
 Simulates Library’s operations
 Consists of
   Server Side
      EJB (J2EE) / C# (.NET)
   Client Side
      JSP (J2EE) / ASP.NET (.NET)
              Test Cases
 Server
   CPU – Intel Pentium III 733MHz
   RAM – 512 MB
   Operating System – Window XP

 Client
   CPU – Intel Pentium IV 2.4GHz
   RAM – 512 MB
   Operating System – Window XP
             Test Cases
 Simple Test Cases
   Case I: Testing on GET method
   Case II: Testing on SET method
   Case III: Testing on UPDATE method
   Case IV: Testing on DELETE method
                Main Comparison Standards




 Scalability

 Portability

 Performance
                   Portability
 This portability is an absolute reality today
  because the Java Runtime Environment (JRE),
  on which J2EE is based, is available on any
  platform.

 .NET only runs on Windows, its supported
  hardware, and the .NET environment
                  Scalability
• Scalability is essential when growing a web
  services deployment over time, because one
  can never predict how new business goals
  might impact user traffic.
• A platform is scalable if an increase in hardware
  resources results in a corresponding linear
  increase in supported user load while
  maintaining the same response time.
                 Scalability
 since .NET supports Win systems only, a >
  number of machines are needed than a
  comparable J2EE deployment due to processor
  limitations.
 This multitude of machines may be difficult for
  organizations to maintain.
                  Performance
 A platform performs if it yields an acceptable response
  time under a specified user load.

J2EE reduces database traffic through two tactics:
-Stateful business processes: maintain business process
  state in memory, prevents writing on every request.
-Long-term caching: re-reading database data upon
  each request, prevents reading on every request.
                  Performance
Performance can be tested by using

 Automation testing tools –used to simulate a user by
  requesting pages
 Load testing tools –These tools will simulate any
  number of users using your site and provide you with
  important data like average response times.
 Profiler. A profiler is a program that examines your
  application as it runs. It provides you with useful run time
  information such as time spent in particular code blocks
  etc
          Documentation




Both provide very good documentation
              Conclusion
                   J2EE    .NET
Performance
Portability
Documentation

Language

Developer Tools
                    Decision
 For an existing
  company
   Cost


 For a new developing
  company
   Importance of multi-
    platform / multi-
    language support
Thank You
              References
 The J2EE Tutorial
 Java 2 Fourth Edition
 www.whitepapers.com
 http://www.microsoft.com/net/

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:5
posted:10/1/2011
language:English
pages:23