Where should W3C be in 2010?

Download Report

Transcript Where should W3C be in 2010?

Enterprise
Software
Productivity
Eric Newcomer, CTO
IONA Technologies
Eric Newcomer
Chief Technology Officer, IONA Technologies
Joined IONA in November 1999, after 16 years at
Digital/Compaq, mostly in DB and TP
Responsible for IONA's technology and standards strategies
Involved in Web services from the beginning:
Co-submitter of SOAP and founder of the XML Protocols Working
Group at W3C
Editor of the W3C Web Services Architecture specification
Co-author and editor of the Web Services Composite Application
Framework (WS-CAF) at OASIS
Co-author of WS-Transactions specifications & co-chair of OASIS WSTransactions technical committee
Co-author of Principles of Transaction Processing (1997),
author of Understanding Web Services (2002), co-author of
Understanding SOA with Web Services (2004)
New Book
Now Available!
… at a glance
Customers include world’s largest firms



80% of Global Telecom
70% of Financial Services in Global 100
Blue Chip System Integrator Partners
Solid business with a history of profitable growth




Founded in 1991
Publicly traded since 1997
$50+ million cash on hand
No debt
NASDAQ:IONA
Our Approach: Making Software Work Together™

Worldwide presence



EMEA HQ in Dublin, Ireland
US HQ in Massachusetts
APAC HQ in Tokyo, Japan


Deliver high performance integration
software for mission critical applications
Make heterogeneity an asset, not a liability
Deliver on the value proposition of standards
Software is a craft industry
Relying on the skills of
individuals
Creating applications
one by one
Stitching integration
solutions by hand
Labor the biggest cost
Software needs mass production
How can this be accomplished?
Very simple answer but
The industry has been trying unsuccessfully for years
[The answer is standardization]
Standard
Application
Programming
Interface
[WSDL]
Application Service
Standard
Network
Interconnect
Protocol
[SOAP]
Underlying Platform
Network
Learning from the Success of the Web
Human to computer
interactions resolved
Standards in place for
programming (HTML) and
interoperability (HTTP)
Highly productive, low cost
Software added at the
network endpoints
Web of Services Not Yet Complete
CICS
IMS
C, C++, COBOL, PL/I, Java, C#
Industry and business
requirements not yet
met
What needs to happen
to make this a reality?
How can we apply
lessons from the Web?
To improve software
inside the company or
between companies
Pioneer of SOA
1500 services in
production
100,000+ users
1B txns/year, 5M/day
73% cost reduction for
systems development and
integration
Reuse of 70% of services
Secure / Reliable
Proves it works
SOA Is Technology Neutral
Home Grown
MQSeries
Architecting SOA has historically meant trade-offs
•
CORBA – Well defined contracts, Auto-generate proxies/skeletons, Multilanguage bindings, Open standard, Enterprise QoS out of the box, CORBA
required at both ends
•
MQ – Low coupling, Enterprise QoS, Not designed as a service platform,
Proprietary
•
J2EE – No contract language, Uni-lingual, Open standard, Enterprise QoS,
Large developer community, Java required at both ends
•
HomeGrown – “Have it your way”, Ranges from Useless to Comprehensive,
Always expensive
Web services and SOA Infrastructure have emerged
to address these issues
WSDL as the Unifying Standard
Extensibility
Handles Both Internet and
Existing Networks
Strong Developer Interest /
Multi-vendor support
Designed for multi protocol,
multi data
WSDL
CORBA IDL
PortType
Interface
Operation
Method
Message
in/out/inout
Part
Parameter
XML Data Type
Class/Type
Logical
Contract
Binding
Physical
Contract
Port
IIOP
(not in IDL)
Service
WSDL - Web Services Definition Language
Home Grown
MQSeries
Add services to the endpoints
Where applications
need to share data
Use service enablement
Reuse existing data
formats and
communication
protocols
Then bridge qualities of
service:
CICS
IMS
Security
Transactions
Reliability
Availability
Endpoint Oriented Infrastructure
Standardize on
Service Interactions
Lower cost of entry
Faster time to ROI
Adaptable
infrastructure
Fully Distributed
Architecture
Services reside within
applications
Endpoints are
configurable
Endpoints are dynamic
Enterprise Qualities of Service
.NET Client
Java Client
Mobile Device
Reliability Services
H/A Services
Transaction Services
Systems Management
Security Services
Directory Services
C++
Java Server
CORBA Server
C++ Server
Mainframe
Broad Platform Support
Web Service Consumers
Existing Enterprise System
IMS
OS390
SOAP
SOAP
SOAP
SOAP
CORBA
TIBCO
JMS
CICS
Existing Enterprise System
Web Service Consumers
Microsoft.NET Client
MQ
CORBA
TIBCO
JMS
MQ
J2EE Application Server
CORBA
Leave and Layer Existing Applications
Leave existing assets in place and include them as part of a SOA
Eliminates the disruption and upfront costs
Allows organizations to move forward and benefit from the
efficiency and agility of a SOA
Multi-Protocol Compatibility
Distributed Services
Routing
WSDL
Transformation
WSDL
Security
Management
WSDL
Directory Services
H/A Services
WSDL
WSDL
WSDL
J2EE or
.NET
Services
Celtix
Services
COTS
Services
Application Endpoints
Example: Standalone Switch
WSDL
IDL
Eclipse
Designer
Design Time
Runtime
Other ESB
MQSeries
CORBA
Tuxedo
Tibco
Artix
Intermediary
Switch
Example: Co-Located Switch
WSDL
IDL
Eclipse
Designer
Design Time
Runtime
Other ESB
MQSeries
CORBA
Tuxedo
Tibco
Artix Co-Located
Example: Generic Web Services
WSDL
IDL
Eclipse
Designer
Design Time
Runtime
Web Services
Artix
Intermediary
Switch
(Can also be
co-located)
Industry and Open Source Initiatives
Complete Web Services standardization
E.g. WS-Policy, WS-Transactions
Service Component Architecture (SCA)
Java Business Integration (JBI)
Developer tooling with Eclipse SOA Tools
Project
Support open source projects for SOA
Celtix
Geronimo
ActiveMQ
Future Directions: Moving SOA into the Network
Consumers
SOA Tools Project
SOA Business Store
Repository
Meta Data Model Services
Service Intermediaries
Business
Services
Data
Services
Business
Processes
Composite
Services
Reliability
Services
Transaction
Services
Location
Services
Management
Services
Security
Services
Policy
Config
Contracts
Artix
Artix
Artix
Mainframe
Transactions
CORBA /
J2EE
Systems
MOM Based
Systems
Service Endpoints
Celtix
JAVA / J2EE
Systems
Summary
SOA
XML/ Web Services
Supported By
Software Tools, Fasteners & Glue
Productivity