Java and.net: You Can't Pick a Favorite Child

Transcription

1 Java and.net: You Can't Pick a Favorite Child Mark Driver Research VP Notes accompany this presentation. Please select Notes Page view. These materials can be reproduced only with Gartner's official approval. Such approvals may be requested via vendor.relations@gartner.com. 1

2 The Big Picture 80% of large mainstream IT organizations rely on both.net and Java technologies 2

3 Microsoft.NET 3.0 Emerging Now C# 2.0 Visual Studio 2005 XAML ASP.NET 2.0 Windows Forms 2.0 Windows Presentation Foundation (WPF) Windows Cardspace Windows Communication Foundation (WCF) Windows WorkFlow Foundation (WF).NET FRAMEWORK 2.0 Base Class Library 3

4 .NET Programming Language Market Share Through 2010 Opportunistic AD Systematic AD 5% 5% 10% 30% 65% 65% 20% Visual BASIC.NET C# C++ Other 4

5 Microsoft and Open Source: Mixed Messages The increased competition resulting from the proliferation of OSS has been constructive for the industry as a whole (MSDN). Linux is a cancer that attaches itself in an intellectual property sense to everything it touches (Steve Balmer) 5

6 The Open Source.NET Equation Supported By Microsoft? NO WAY, NO HOW! However, over 400 developers have delivered an independent open source implementation of.net. Mono currently supports 90%+ of.net Framework 2.0 API s. 6

7 Novell and Microsoft: A Match Made In Heaven Or Hell? 1. Sales Collaboration: 5 year deal wherein Microsoft resells SUSE Enterprise Linux 2. Technology Interoperability Collaboration 1. Virtualization interoperability 2. Document format interoperability 3. Mixed environment management interoperability 3. Intellectual Property Agreement: Neither Microsoft or Novell will sue each others customers over IP infringement issues. 7

8 Java 2 Enterprise Edition Version 5: Focusing On Simplification Source Code Annotations Instead of Deployment Descriptors Simplified EJB Software Development Use Dependency Injection to Access Resources Java Persistence API Model Simplified Web Services 8

9 The Open Source Java Equation Sun has recently open sourced most of the core JDK and virtual machine. Apache s Project Harmony is well under way to provide a truly independent implementation. Sun retains control over the Java trademark and compatibility test kits. 9

10 Are 64-Bit Applications In Your Future? Both Java and.net Support 64-bit OS Architectures Today. Real world feedback shows typically 5% or less performance improvement for today s applications running under a 64-bit runtime. However 64-bit provides access to much larger memory addresses (16 TB vs. 4G) 64-bit provides a more efficient runtime engine for computationally intensive applications. 64-bit can provide a mechanism for next generation application designs. 10

11 A Technology Reality Check stronger Microsoft.NET vs. Java EE stronger Security Scalability and QOS RAD Productivity Enterprise Flexibility Rich Client Service-Oriented Legacy Integration Open-Source Support Enterprise ISV Support Perception Reality 11

12 Market Segmentation Mission-Critical Increasing complexity and scalability requirements Increasing multivendor and cross-platform appeal Enterprise Scale Departmental Scale Java s Market Penetration Increasing volume of applications Decreasing time to market Workgroup Scale Microsoft s Market Penetration Increasing RAD appeal Process-Critical Personal Scale 12

13 The OLTP Gap Is Closing New Transactional 2006 Applications % 90% 80% 70% 60% 50% 40% 30% 20% 10% 0% OSS JEE Microsoft Application Platform Closed source JEE ,000 10,000 Concurrent Users OSS JEE Microsoft Application Platform Closed source Extended JEE ,000 10,000 Concurrent Users 100% 90% 80% 70% 60% 50% 40% 30% 20% 10% 0% MSAP (.NET, COM+) Closed source J2EE (WebSphere, WebLogic, Oracle AS J2EE, SAP WAS) Open-Source J2EE (Tomcat, JBoss, JOnAS, Geronimo, Glassfish) Other I (PHP, Perl, Forms, PL/SQL, CF) Other II ( CICS, IMS, ABAP, Tuxedo) 13

14 Typical AD Platform Commitment Trends By Organization Size 90% 25% 15% 25% 70% 50% 70+% 60% 25% 30% 50% 10% <5% 25% Small Medium Large Other (4GL, Legacy, etc.) Microsoft Java 14

15 Differences Are Technical And CULTURAL Java Microsoft Technology Designed to be generally consistent across a great number of platforms. Designed to fully exploit the synergy of a single integrated platform. Process Heavily influenced by systematic development processes from OO environments. Heavily influenced by opportunistic development processes from RAD 4GL environments. Organization Historically leveraged by centralized and highly trained IT staff exclusively. Historically leveraged by decentralized business unit developers. 15

16 Microsoft s March Into BIG Enterprise AD Mission-Critical Increasing complexity and scalability requirements Increasing multivendor and cross-platform appeal Inhibitors OS Platform breadth limitations Sins of the father perceptions Enterprise ISV Support Culture and Politics Proprietary Lock in Increasing volume of applications Decreasing time to market Increasing RAD appeal Process-Critical Drivers Increasing Quality of Service Developer Productivity Application Lifecycle Management Focus SOA Interoperability 16

17 Bottom Line: Flexibility Versus Productivity Microsoft.NET sacrifices technical flexibility in favor of developer productivity Java sacrifices developer productivity in favor of technical flexibility. Flexibility Productivity Flexibility Productivity 17

18 Summary Trends For Java Java technology commitments become slightly more vendor proprietary over the next 3 years but openness continues to drive overall adoption This is mitigated somewhat by investments in open source tools and frameworks. Java productivity increases as a result of less flexibility and simplified Java EE 5 but continues to lag.net for small and medium scope projects. Java adds multi-language capabilities as it expands to support dynamic languages to better address next generation AD concepts. 18

19 Summary Trends For Microsoft.NET.NET takes an increasing role in systematic enterprise development efforts. Microsoft s Team Server tools take a dominant role in.net application lifecycle management roles..net 3.0 emerges as strong technology advances but is slow to be adopted until Vista reaches critical mass adoption. 19