1 / 22

J2EE vs .NET: Comparing Architectural Approaches for Enterprise Application Development

This comprehensive analysis delves into the architectural differences between J2EE and .NET frameworks for enterprise application development. It examines critical factors such as distributed systems support, cross-platform capabilities, performance, security, and integration with multiple data sources. The discussion highlights key roles within both J2EE and .NET ecosystems, detailing modular component design, business automation strategies, and modeling business processes. By comparing the strengths and weaknesses of both platforms, developers can make informed choices for their enterprise applications.

audra-gonzales
Download Presentation

J2EE vs .NET: Comparing Architectural Approaches for Enterprise Application Development

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. J2EE vs. .NET Tom Tong

  2. Enterprise Application 1 distributed 2 multiple-platform 3 critical 4 performance 5 security 6 multiple-data sources

  3. General Approaches Business Automation Component technology Service Synchronization Abstraction Bridge and Connection Modeling Business Details …….. Technological Details (database, network, operation system…)

  4. J2EE solution Modular components Job division Ease development System level Services Standardization Java Virtual Machine (JVM) Operation System

  5. J2EE Roles • EJB Developer • Application assembler • Deployer • System administrator • EJB Server Provider • EJB Container provider

  6. J2EE Application Model

  7. J2EE Architecture

  8. J2SE Architecture

  9. Component development

  10. EJB developer’s job EJB design (session bean, entity bean, message driven bean) Business Modeling EJB components

  11. .Net solution • Take full advantage from operating system • Pack as many as possible functionalities into operating system • Operating system manage enterprise resources • Operating system works like container

  12. .Net Application Model Presentation Layer Data Layer Communication Layer Base Library Management Common Language Runtime (CLR)

  13. .Net Framework • From Win32 API to .Net Framework Base Operation System

  14. Next Generation .Net (Longhorn)--Base Operating System

  15. Presentation Layer (Avalon)

  16. Data Layer

  17. Communication Layer

  18. .Net Multiple Language Support C#, C++, C, VB, #J, almost all all languages except Java Application Intermediate Language(IL) JIT compiler Common Language Runtime Base Operating System

  19. .Net vs. J2EE

  20. .NET vs. J2EE • J2EE: single language on multiple operating system • .Net multiple language on single operating system

  21. Advantages and Disadvantages Development support Maintainability Scalability Legacy integration Portability: write one, runs everywhere Security: Deployment: Performance:

  22. Question ? And comments !

More Related