NAPHIT: Microsoft Platform Marley Gray Senior Architect Evangelist National 'NET Adoption Team Micro

1
NAPHIT Microsoft PlatformMarley GraySenior
Architect EvangelistNational .NET Adoption
TeamMicrosoft Corporation
2
Agenda

• What is the Microsoft Platform
• Evolution of the Platform
• Performance
• Integration

3
Big Ideas

• Robust managed runtime environment that is built
  for multi-language, security, performance
• Webservices as an enabling technology
  interoperability, device independence, decoupling
  presentation from data
• Radically changing the UI landscape
• Windows is the platform, .NET is the key
  ingredient.

4
Windows Client Roadmap
Q1 2005
Today
2002/03
Mira smartdisplays
Longhorn

• Communication and collaboration
• Mobility
• Digital media and entertainment
• Personal empowerment
• Fundamentals
• Major UI Update

Windows XP Media Center Edition PCs
Media Center PCs
Windows XP Tablet PC Edition
Tablet PC Version 2
5
Windows Server Roadmap
Yesterday
Today
Post Longhorn
Blackcomb

• Intelligent, Self-Managing OS and Services
• Virtualization
• Trustworthy Computing
• Federation

6
Windows 2003 ServerSolutions Infrastructure

• Enabling collaboration
• File and print server
• Mail server
• Providing network access
• Anytime, anywhere, any device access
• Remote access/virtual private network (VPN)
  server
• Cost-reducing network services
• Directory services (AD/LDAP)
• Domain Name System (DNS)
• Dynamic Host Configuration Protocol (DHCP) server
• Enabling new opportunities through
  Internet/Intranet Web and Application Services
• Web server
• Web application server
• Streaming media server
• 32 and 64 bit versions.

7
IIS 6.0 ArchitectureThe transition from IIS5 to
IIS6
INETINFO
Aspnet_wp.exe
metabase
ASP.NET ISAPI
CLR App Domain
CLR App Domain
CLR App Domain
TCP/IP
8
Increasing .NET Scale Performance Better Real
World Performance

• E-commerce benchmark from Doculabs. Measures the
  overall performance of some scenarios that are
  commonly used by e-commerce sites.
• Logon, browse items, search, shopping cart
  operations, check out.
• Static file caching, data-base operations,
  session state management.

1P 49 4P 120 8P 170
Reqs/sec
1P - 4P 3.3x 1P - 8P 5.0x
9
Windows as an Application Server

• Windows Server 2003 is the 4th generation
  application server.
• MTS 1997 (Transactions, TP Monitor, Object
  Pooling)
• COM 1.0 1999 (MTS , Queued Components, Async)
• COM and .NET Framework 1.0 (2002)
• COM 1.5 and Windows .NET Framework 1.1 (2003)
• COM TPC benchmarks speak for themselves

10
_at_Bench Web Services Benchmark

• Tests Web Service performance and scalability
• Compares .NET to J2EE
• .NET on Windows Server 2003
• JBOSS on Linux
• Two mainstream commercial J2EE application
  servers on Windows
• Shows .NET performance with Oracle and SQL Server
  backend databases

11
Web Service Performance8 CPU Web Service Host
1486.53
1600.00
8 CPU - J2EE
1400.00
It is believed that the high performance results
for .NET are due to the fact that Web Services
were part of the core .NET framework from the
start and not added features on top of an
existing framework, as is the case with J2EE.
-Doculabs, April 2003
8 CPU - .Net 1.1
1076.95
1200.00
1000.00
Transactions Per Second
800.00
513.33
600.00
411.87
296.25
400.00
200.00
0.00
JBOSSRH Linux 8.0Oracle 9i DB
.NET 1.1Win 2003Oracle 9i DB
.NET 1.1Win 2003SQL Server 2000
J2EEApp Server YWin 2000Oracle 9i DB
J2EE App Server X Windows 2000 Oracle 9i DB
Source Doculabs Web Service Benchmark, March
2003
12
Web Service Performance4 CPU Web Service Client
App Server to remote 8 CPU Web Service Host App
Server
796
798
800.00
8 CPU - J2EE
700.00
8 CPU - .Net 1.1
600.00
500.00
396
Transactions Per Second
400.00
332
300.00
220
200.00
100.00
0.00
JBOSSRH Linux 8.0Oracle 9i DB
.NET 1.1Win 2003Oracle 9i DB
.NET 1.1Win 2003SQL Server 2000
J2EEApp Server YWin 2000Oracle 9i DB
J2EE App Server X Windows 2000 Oracle 9i DB
Source Doculabs Web Service Benchmark, March
2003
13
Web Service InteroperabilityJ2EE and .NET
Together4 CPU Web Service Client App Server to
remote 8 CPU Web Service Host App Server
800.00
8 CPU - J2EE
700.00
8 CPU - .Net 1.1
600.00
500.00
405
393
Transactions Per Second
400.00
300.00
200.00
100.00
0.00
.NET Web Service Client (ASPX/Windows
2003) to JBOSS Web Service Host(RH Linux
8.0/Oracle 9i DB
J2EE App Server Y Client (JSP/Windows
2000)To .NET Web Service Host (Windows
2003/Oracle 9i DB)
Source Doculabs Web Service Benchmark, March
2003
14
_at_Bench Web Services Benchmark Discussion

• .NET up to 400 better throughput than leading
  J2EE app servers
• .NET up to 260 better than J2EE with Oracle as
  common backend
• .NET wins every tested scenario
• Web Service Hosting
• Web Service Enterprise Application Integration
• Tests demonstrate .NET and J2EE interoperability
  with Web Services

15
Evidence TPC.ORG

• Transaction Processing Performance Council
• Windows and SQL 2000 holds 2 Scale-up position
  with 658,277  tpmC _at_ 9.80 US per transaction.
• Windows/SQL holds 3 of 5 top positions in
  non-clustered benchmarks.
• Windows and SQL Server are 1,2 and 3 on the
  clustered results with a top tpmC of 709,220
  _at_ 14.96 US

16
Microsoft IT Offerings
Applications
Business Apps
Productivity Apps
Developer Tools
Enterprise Systems Management
Security
Application Infrastructure
E-Business Infra
Knowledge Worker Infra
Database
Storage
Network/Operating System Infrastructure
Source IDC, MS analysis
Based on IDCs 100 Individual Markets
17
Agenda

• What is the Microsoft Platform
• Evolution of the Platform
• Performance
• Integration

18
What is Microsoft .NET

• Microsoft .Net is the name given to the
  development approach on the Microsoft platform to
  build loosely coupled, next generation
  applications on the Microsoft Platform leveraging
  XML Web Services.
• .NET Development XML Web Services are a key
  focus of the Windows Platform and enabling
  technology is present at all levels of the
  technology stack.

19
Web services support across the Microsoft
platform
Clients
Experiences Solutions
Tools
Services
Servers
20
Before the Framework

• Multiple Languages and Development / Runtime
  Environments (C, VB, J, ASP)
• Developers Need to choose a given dev environment
  based on the task at hand.
• COM provided solid App Server starting point.
  (Transactions, Object Pooling, etc)
• UDA being realized at the Data Store Level not
  significantly at the Application interoperability
  level.
• Good learning in the move from Client Server to
  Web Application Paradigm. Multi-tiered
  application models was a good thing!

21
Windows .NET Framework
22
UI Evolution

• Next Generation
• Clients
• Exploit power of the edge
• XML Web service connected
• Offline support
• Natural user interface
• Integrated communications
• Analytics and action
• Seamless deployment
• Applies to smart devices too

23
Smart Clients have

• Killer UI
• Great XML Webservice clients
• Offline support for roaming networks
• No more DLL Hell No-Touch deployment
• Evidence based security
• Leverage the power of the edge device
• Use less bandwidth over time
• Integrate with other desktop applications.

24
Agenda

• What is the Microsoft Platform
• Evolution of the Platform
• Performance
• Integration and Interoperability

25
Pet Shop 2.0

• Evidence

26
Pet Shop revisited Middleware App. Server Web
Services Benchmark

• MiddleWare Co. re-test of J2EE vs. .NET
  Per./Scale
• Spent 4 months testing J2EE and .NET reference
  applications
• Developed new J2EE application optimized for
  performance
• Conducted new series of comprehensive benchmarks
• All results taken by and certified by Middleware
  Company
• Includes Web Application, Web Services and
  Distributed Transaction benchmarks
• Report available at http//www.middleware-company.
  com/j2eedotnetbench
• Downloadable code, test scripts, discussion forum
  also available

27
Web Application BenchmarkTests n-tier Web
application hosting
Windows Server 2003 outperforms J2EE by 339 on
the Web application benchmark
28
Developer Productivity Comparing .NET And J2EE
Implementations Based on new Middleware J2EE
Reference Application with EJBs and Equivalent
.NET Reference Application with C Components
Optimizing, configuring J2EE 10 man-weeks per
application server .NET  2 man-weeks
29
Project Cost ModelDevelopment Costs Dominate
Source Gartner, May 2002 The Cost and Risk of
Application Development DecisionsJoseph Feiman,
Tom Berg
30
.NET AdvantageDeveloper Productivity

• Use Customer Testimonials and Analyst Reports
  Practical Evals
• Nationwide Building Society - 90 reduction in
  code
• AON - brings solutions to market in half the time
• CafePress - 80 reduction in code
• UnumProvident - project time drops from 18 months
  to 6 months
• Zagat - developers are twice as productive
• Financial Technologies International -
  development time halved
• Bank of New York - time-to-market reduced 40
• Pfizer - 25-50 increase in developer
  productivity
• CNET Channel - 50 faster development
• Allstate - developers at least twice as
  productive as with J2EE
• 7-Eleven - development time went from 9 weeks on
  J2EE to 2 weeks in ASP.NET
• CafePress.com - development cycle times reduced
  75, as compared to Java

31
Agenda

• What is the Microsoft Platform
• Evolution of the Platform
• Performance
• Integration and Interoperability

32
Interoperability

• Using XML, integration with other systems is
  easy. (WS-I.org)
• Universal Data Access ODBC, OLEDB and ADO.NET
  Managed Providers (SQL, Oracle, DB2, )
• Interoperate with CICS, IMS, J2 COM/TI, .Net
  Remoting to RMI Bridge, MSMQ to MQ Bridge.
• .NET is not rip and replace its embrace and
  extend

33
Why .NET for Public Health

• Do more with less.
• Time to market.
• Vast pool of developer skills.
• Lower TCO

34
Questions