E-business Architecture.NET vs J2EE Judith Molka-Danielsen Feb.27, 2004.
Published byModified over 5 years ago
Presentation on theme: "E-business Architecture.NET vs J2EE Judith Molka-Danielsen Feb.27, 2004."— Presentation transcript:
E-business Architecture.NET vs J2EE Judith Molka-Danielsen Feb.27, 2004
Issues in developing an architecture Vendor neutrality – device independence Platform maturity Interoperability (in B2B transactions) Scalability and performance Programming languages and skills needed Portability and legacy integration Modularity and reuse Costs
2-tier : Client-Server architecture High load between client and server. Tight interoperations of presentation logic, business logic, and data access logic. Not scalable; Not flexible
N-tier architecture : application functions are partitioned into N independent layers. Each layer is scalable and upgradeable independently. Do not have to recreate each layer, when one is changed. Each layer can cluster servers, to increase reliability, access, scalability.
J2EE : Java 2 Platform Enterprise Edition Has extended APIs from Java 2 Standard Edition. Has components for modularization. Supports object-oriented languages. Has JDBC API for database access. Supports Enterprise Java Beans (EJB), Java Servlets API, Java Server Pages (JSP) API, XML, Java Mail API, and JavaMessaging API.