220 likes | 357 Views
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. Component technology. Service. Synchronization. Abstraction. Bridge and Connection.
E N D
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 Component technology Service Synchronization Abstraction Bridge and Connection Modeling Business Details …….. Technological Details (database, network, operation system…)
J2EE solution Modular components Job division Ease development System level Services Standardization Java Virtual Machine (JVM) Operation System
J2EE Roles • EJB Developer • Application assembler • Deployer • System administrator • EJB Server Provider • EJB Container provider
EJB developer’s job EJB design (session bean, entity bean, message driven bean) Business Modeling 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 Management Common Language Runtime (CLR)
.Net Framework • From Win32 API to .Net Framework Base Operation System
.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 • 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: