Why WebSphere Is Better Than .

NET

Selecting a Foundation
So far, we have seen middleware solutions for
integrating people, processes, and data
Now lets take a look at some of the underlying
technologies
Programming Model
Web Services
Service Oriented Architecture
Enterprise Services Bus

CTS7-06 Why WebSphere is Better than .NET.ppt

Challenges to Implement Todays on demand,

Server-Side Applications
How do I manage transactions?
How do my applications find the
components they need?
How do I easily access other
applications and data in a
consistent manner?

WebSphere/J2EE

.NET

Which one is best on the

servers?

How do I optimize for performance?

How do I handle security?
Friendly Finance

How do I expose my applications to be

used by any client?

CTS7-06 Why WebSphere is Better than .NET.ppt

WebSphere/J2EE Enjoys Strong Customer

Adoption

#1 in market share
50,000 customers worldwide
2,800+ active ISV solutions running on WebSphere
1M+ registered WebSphere developers
93 out of Fortune 100 companies
Top 45 worldwide commercial and savings banks
14 out of top 15 worldwide telecommunications firms
All 13 worldwide pharmaceutical companies
21% year-to-year revenue growth in 2002, far outgrowing
the competition

CTS7-06 Why WebSphere is Better than .NET.ppt

Why WebSphere/J2EE is Better Than .NET

Best Server-Side Environment

Runs on any platform, including Linux

Stronger environment for on demand applications
Container concept makes good programming easier
Better performance in real-world workloads
Tighter security
WebSphere maturity avoids 5 years of .NET rollout misery
Web services interoperability and service oriented
architecture
Enterprise Service Bus for on demand business
integration
Tooling provides greater programmer productivity
5

CTS7-06 Why WebSphere is Better than .NET.ppt

WebSphere Enables Platform Portability

WebSphere
Studio

Open standards make it

possible to develop
application once, deploy
on multiple platforms
J2EE
Application

WebSphere
Application
Server

WebSphere
Application
Server

Windows

Linux

WebSphere
Application
Server

WebSphere
Application
Server

WebSphere
Application
Server

OS/400

zOS

UNIX
(AIX, HP-UX, Solaris)
CTS7-06 Why WebSphere is Better than .NET.ppt

Portability Finally Achieved via Standards and

Cross-Platform Products
Product implementation of J2EE
available on a wide variety of
server platforms

WebSphere Application Server

Defines containers and a profile of

standards for the Java runtime
platform

J2EE Standards

Runs same Java code on any

hardware/operating system

Java Virtual Machine

CTS7-06 Why WebSphere is Better than .NET.ppt

J2EE Platform
WebSphere Application Server
HTTP
SSL

End User's
Web Browser

RMIIIOP

Web Container

JSP Page

Connectors

JAF

JAXP

Java
Mail

JDBC

JTA

JMS

JAAS

J2SE

Connectors

JAXP

JAF

Database

Enterprise
JavaBean

Servlet

JDBC

JTA

JMS

JAAS

Java
Mail

EJB Container

Customer
Data

J2SE

JDBC

CTS7-06 Why WebSphere is Better than .NET.ppt

DEMO: Friendly Finance is Open for Business 24x7

A look at the web site

Customer service functions

Log in
Account Management

Linux deployment
Windows deployment
CTS7-06 Why WebSphere is Better than .NET.ppt

A Good Strategy
Going forward, you should never develop
another server side application that doesnt
have deployment flexibility

That makes sense

IBM

Friendly Finance
CTS7-06 Why WebSphere is Better than .NET.ppt

10

Microsoft Middleware and the .NET Framework

SQL
Server

Application
Center
(Clusters)

Exchange
Server

Host
Integration
Server

BizTalk
Server

Commerce
Server

Sharepoint
Portal
Server

Internet Security
and Accelerator
Server

Mobile
Information
Server

Content
Management
Server

.NET Framework
MSMQ

MTS/COM+

WMI

IIS

Some Enabled with

.NET Interfaces
Implementations
are Still Older
Technology

Bundled in Windows
Server 2003
Enables new
applications to run in
.NET execution
environment

WIN32
Represents 2% of total
code base
11

CTS7-06 Why WebSphere is Better than .NET.ppt

Microsoft .NET Framework

Desktop Application

Server Application

Windows User
Interface

ASP.NET
Web
Services

Web
Forms

ADO.NET

Network

XML

Programming languages
VB.NET,C#,C++,JScript.NET

Support for server

or desktop
applications

Data Access, XML, and

Internet access

Base Classes

.NET Execution Engine

based on Microsoft
Intermediate Language
(MSIL)

Common Language Runtime

MSMQ

MTS/COM+

IIS

WMI

Win32

CTS7-06 Why WebSphere is Better than .NET.ppt

12

New .NET Capabilities Trail Java by 5 Years

New!

5 Years Ago

Server Side Programming Model

.NET

WebSphere/J2EE

Abstracted Runtime Environment

CLR

JVM

Abstract Instruction Set

MSIL

Byte Code

Native Compilation

JIT

JIT

Object Introspection

Yes

Yes

Garbage Collection

Yes

Yes

Exception Handling

Yes

Yes

Type Safety

Yes

Yes

Persist Session State

Yes

Yes

Data Connection Pooling

Yes

Yes

Replace Server Components

at Runtime

Yes

Yes

CLR - Common Language Runtime, MSIL - Microsoft Intermediate Language, JVM - Java Virtual Machine

CTS7-06 Why WebSphere is Better than .NET.ppt

13

WebSphere Provides Stronger Environment for

on demand Applications

Transactions

Location Services

J2EE designed from the ground up to support distributed

transactions (JTS, JTA)
.NET doesnt have this support; must rely on legacy COM+
services

J2EE has JNDI directory services to find remote objects

.NET remote calls hardcode location of remote objects

Connection Architecture

J2EE has J2EE Connector Architecture

.NET has no standardized architecture for connecting to
enterprise systems
CTS7-06 Why WebSphere is Better than .NET.ppt

14

WebSphere Provides Stronger Environment for

on demand Applications (contd)

Connectivity

Web Services

WebSpheres Enterprise Services Bus provides a strong

backbone with a broad reach to connect to virtually all
systems and applications
.NET has no concept of an Enterprise Services Bus

WebSphere has extended Web services with ServiceOriented Architecture (SOA) concepts
.NET has no equivalent SOA construct today

Performance

WebSphere scales well to multi-tier deployments

.NET best practices recommend single-tier deployment
CTS7-06 Why WebSphere is Better than .NET.ppt

15

Container Concept Makes Server-Side

Programming Easier

Containers provide an environment in which to run

application components

WebSphere/J2EE container simplifies the job of creating
server-side applications

CICS was the industrys first commercially successful
container
WebSphere
Containers

Web Container
JSP Page

Servlet

Connectors
JDBC
JAXP

JAF

J2SE

Enterprise
JavaBean

JTA
JAAS
JMS

Connectors
JDBC
JAXP

JTA
JAAS
JMS

Java
Mail

RMIIIOP EJB Container

Database

Java
Mail
JAF

J2SE

CTS7-06 Why WebSphere is Better than .NET.ppt

16

How Containers Help the Underlying OS

A) No Containers

1000
Clients

1000 Connections
+
1000 Processes
+
50 MBytes of RAM
+
10,000 Open Files

Operating
System dies

B) With a Container
Container
1000
Clients

50

50 Shared Connections
+
50 Processes
+
25 MBytes of RAM
+
500 Open Files

CTS7-06 Why WebSphere is Better than .NET.ppt

Operating
System is fine

17

WebSphere/J2EE Containers Manage More Than

Just Transactions

Supports transactions and data sharing transparently

Provides platform transparency application or components are unaware
of the underlying platform
Provides a single-level store programming model so that components are
free from the issues of when and how to load their persistent state
Handles the communication, distribution, and addressing necessary for
distributed components
Increases reuse by allowing components to be used by different
applications simultaneously
Performs component activation/deactivation to better manage total
system resources
Automatically manages pools of servlets, EJBs, DB connections to
create/destroy resources more efficiently
Caches web pages and fragments to respond to requests more quickly
Protects components from unauthorized access
Provides Message-Driven Bean (MDB) initiation
Provides J2EE/CA shared connection services
CTS7-06 Why WebSphere is Better than .NET.ppt

18

What About .NET?

.NET does not manage transactions.

NET does not provide platform transparency

.NET Remoting users must deal with the complexities of communication,

distribution, and addressing necessary for distributed components
DCOM does support distributed components

.NET restricts component reuse

to write good programs

.NET components must run on Wintel platforms.

.NET does not manage data persistence

.NET does not automatically support distributed components

Must rely on legacy COM+ services for this support. RESULT: more difficult

Users must code transaction and security requirements in the components source
code

.NET does not perform component activation/deactivation

.NET does not pool resources

Some managed data providers pool DB connections

COM+ must be told which COM+ components should be pooled

.NET does not automatically cache web pages and fragments

.NET does protect components from unauthorized access

.NET has no concept analogous to J2EE/CA

Users must migrate to Windows Server 2003

CTS7-06 Why WebSphere is Better than .NET.ppt

19

Its Smart To Use a Container

Easier to write good code

Fewer bugs

Application programmers do not have to repetitively write

difficult code for each application

Resource management in multi-user environment is complex,

is more likely to have bugs than business code, and those
bugs are more difficult to correct

More flexible administration

Declarative configuration means that administrators can

change policy without waiting for a programmer to make code
changes
These are advantages over .NET
CTS7-06 Why WebSphere is Better than .NET.ppt

20

10

Better Performance

What about Performance?

WebSphere performs better

than .NET in real-world
workloads and we have the
benchmarks and customer
references to prove it

Friendly Finance

IBM

CTS7-06 Why WebSphere is Better than .NET.ppt

21

Friendly Bank Benchmark:

Effects of Separated Tiers
71

46.2

Increased performance

WAS
Single Server

WAS
Separated Tiers

33.9
20.3

Decreased performance
.NET
Single Server

.NET
Separated Tiers
CTS7-06 Why WebSphere is Better than .NET.ppt

24

11

DEMO: Effects of Distributed Processing

WAS 5 + IBM HTTP Server
RMI / IIOP

Compare
performance
of two-tier
configurations

JSP
Servlets
HTTP

EJB

2 way
xSeries

2 way
xSeries

Windows 2003 RC2 & IIS6

HTTP/Binary .NET Remoting
ASP.NET

.NET Objects

IIS

Serviced
Components

2 way
xSeries

2 way
xSeries

CTS7-06 Why WebSphere is Better than .NET.ppt

25

Potential Microsoft .NET Performance Pitfalls

1.

.NET Remote or DCOM multi-tier deployments

2.

Clusters

3.

Searching ADO.NET data sets

4.

Use of Web Forms impacts performance

5.

Distributed transactions on a multi-system scope

6.

Using auto-complete in transactions vs. manual

7.

Mixed workloads

CTS7-06 Why WebSphere is Better than .NET.ppt

28

12

Office Depot

Office Depot replaced Microsoft Web solution with WebSphere

Needed to scale their e-commerce infrastructure to meet projected

growth

Performance improved by 50% over previous Microsoft solution

Requires 75% fewer servers than Microsoft solution (160 > 40)

Solution

WebSphere Application Server V4.0

WebSphere Studio Application Developer

IBM iSeries hardware servers

29

CTS7-06 Why WebSphere is Better than .NET.ppt

eBay
Results to date:

Went live with WebSphere 4.0.2 on schedule, March 2002

Dynamic environment

Update HTML 18 times/week

Major code release once per week

30KLOC changes weekly

View item running on 66 2way xSeries processors

138 million items

2 million new items per day

320 million views per day

8000 transactions per second

One third less code, equivalent performance to C++

CTS7-06 Why WebSphere is Better than .NET.ppt

"WebSphere, with its Java-based

J2EE technology framework, gives
us tremendous business
advantages."
Maynard Webb
President eBay Technologies

30

13

Schwab Brokerage/Trading Applications

Barista II proof of concept project

Separate tier for EJB business logic

Heavyweight account overview pages

350 pps with 67% CPU utilization on servlet nodes and 73% on EJB nodes
Demonstrated capability to meet production requirements of 16.5 million
transactions per day (Peak/average ratio is 8.7)
account
overview page

servlet
44 nodes

EJB
15 nodes

data
15 nodes

RS/6000 Winterhawk II

31

CTS7-06 Why WebSphere is Better than .NET.ppt

WebSphere/J2EE: A Consistent Model for Security

Declarative, Roles-Based Access Control
Application
Provider

Developers create
application components
E.g. Build a method to
delete accounts

Application
Assembler

Declare what Role is

required to access
each resource.
E.g. Supervisors
can delete Accounts

Security
Administrato
r

Assign Roles to
Users

use LDAP server

as the user
directory

E.g. Assign Supervisor

Role to Kate

JSPs, servlets, EJBs, etc. are all protected with the same model
CTS7-06 Why WebSphere is Better than .NET.ppt

32

14

Microsoft Mixed Security Models

COM+ role-based access control model is declarative

.NET role-based access control is specified in source code

[PrincipalPermission(SecurityAction.Demand,Role=Teller)]
public void CreateAccount(){.}

The two models have different class hierarchies and define roles
differently

This

means that serviced components (COM+) have a different security

model than pure .NET components

SharePoint does not even use role-based security

Site groups/cross-site groups

Inconsistent models tend to provide looser security

Increased

chance of mistakes, oversight, conflicts

CTS7-06 Why WebSphere is Better than .NET.ppt

33

Demo: Consistent Security Model

Application
Assembler

WebSphere Application
Assembly Tool

A consistent security model provides tighter security

Spot and resolve conflicts

Fewer mistakes and oversights
Easier to manage effectively
CTS7-06 Why WebSphere is Better than .NET.ppt

34

15

.NET Is Way Behind IBM In Platform Build-Out

Microsofts server environment will be
unstable for the next 5 years because
the remaining 98% of code has to be
re-implemented in .NET

A complete server platform, all built on

J2EE, provides a stable environment
going forward

DATA
BASE

COLLABORATE

HOST
INTEGRATION

FLOWS

COMMERCE

DATA
BASE

COLLABORATE

HOST
INTEGRATION

FLOWS

CLUSTER

PORTAL

EDGE

PERVASIVE

CONTENT
PUBLISH

CLUSTER

PORTAL

EDGE

PERVASIVE

COMMERCE

CONTENT
PUBLISH

2%
MQ

.NET Framework

MQ

Transactions

Transactions

J2EE Environment

UI

HTTP

UI

HTTP

WIN32

WIN32 / Linux / Unix / zOS / OS400

35

CTS7-06 Why WebSphere is Better than .NET.ppt

Microsoft Roadmap: 5 Years of Misery

Native COM

3 Major Technology Transitions

Native .NET
Native Longhorn

Windows Client

Win XP

Office Suite
Windows Server
SQL Server
Exchange Server

Office 2003
+VS Tools

Office XP

W2k

W2k3

Yukon
Exchange
2003

Exchange
2000
SPPS 2001
BizTalk
2000

Kodiak

SPPS 2003
BizTalk
2002

BizTalk 2004

Jupiter
Visual Studio

Blackcomb

SQL 2000

SharePoint Portal
BizTalk

Longhorn

Phase1
VS 6.0

2000

2001

VS .NET

VS .NET
2003

2002

2003

2004

CTS7-06 Why WebSphere is Better than .NET.ppt

Phase 2
VS
Whidbey

VS
Orcas

2005

2006

2007
36

16

Why WebSphere/J2EE is Better Than .NET

Best Server-Side Environment

Runs on any platform, including Linux

Stronger environment for on demand applications
Container concept makes good programming easier
Better performance in real-world workloads
Tighter security
WebSphere maturity avoids 5 years of .NET rollout misery
Web services interoperability and service oriented
architecture
Enterprise Service Bus for on demand business
integration
Tooling provides greater programmer productivity
CTS7-06 Why WebSphere is Better than .NET.ppt

37

17