J2EE vs..NET Tom Tong
Enterprise Application 1 distributed 2 multiple-platform 3 critical 4 performance 5 security 6 multiple-data sources
General Approaches Business Automation Business Details Abstraction Modeling Component technology Service Synchronization Bridge and Connection …….. Technological Details (database, network, operation system…)
J2EE solution Ease development System level Services Standardization Modular components Job division Java Virtual Machine (JVM) Operation System
J2EE Roles EJB Developer Application assembler Deployer System administrator EJB Server Provider EJB Container provider
J2EE Application Model
J2EE Architecture
J2SE Architecture
Component development
EJB developer’s job Business Modeling EJB design (session bean, entity bean, message driven bean) EJB components
.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
.Net Application Model Presentation Layer Data Layer Communication Layer Base Library Common Language Runtime (CLR)Management
.Net Framework From Win32 API to.Net Framework Base Operation System
Next Generation.Net (Longhorn) --Base Operating System
Presentation Layer (Avalon)
Data Layer
Communication Layer
.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
.Net vs. J2EE
.NET vs. J2EE J2EE: single language on multiple operating system.Net multiple language on single operating system
Advantages and Disadvantages Development support Maintainability Scalability Legacy integration Portability: write one, runs everywhere Security: Deployment: Performance:
Question ? And comments !