Web Services as a mechanism for exposing smart services. Brasche Program Director gobrasch@microsoft.com

Transcription

1 Web Services as a mechanism for exposing smart services Dr GötzG tz-philip Brasche Program Director gobrasch@microsoft.com

2 Agenda Why Web Services? Where are we today? Where are we heading? What are we doing?

3 Service Orientation Microsoft believes in an approach to building systems using services which adhere to the 4 tenets of Service Orientation Boundaries are explicit Services are autonomous Share schema/ contract, not class Compatibility via policy Developers opt-in to consuming, exposing, and defining public-facing service façade Services and consumers are independently versioned, deployed, operated, and secured Types are structural or behavioral, never both. Objects are a local phenomenon Capabilities/requirements represented by name & used to establish service suitability

4 Microsoft s s Bet: Services Everywhere Personal Networks Government Networks Social Networks Business Networks Customer Relationship Networks HR Purchasing Value Chain Networks Scientific Networks Fulfillment

5 Microsoft s s Bet: Services Everywhere HR Purchasing New York Operations Fulfillment Web Frontend Mobile SQL Cluster

6 Microsoft s Bet: Services Everywhere Scales Away spans organizations and geographies Scales Out by adding machines Scales Up on large systems Scales In on a machine Scales Down to devices

7 Web Services Ambitions Make distributed computing significantly faster, easier and cheaper Make service orientation mainstream Provide single universal model for all interactions Provide a general-purpose, composable protocol framework Provide flexibility by metadata-driven driven description policy Provide security with a capabilities-based based security model

8 Agenda Why Web Services? Where are we today? Where are we heading? What are we doing?

9 The Evolution to Web Services Web application technology = Web services Late 1990s Web technologies appear e.g. HTTP, HTML, XML Pre-1990s Custom, static B2B Integration Early 1990s Application integration technologies appear Business Benefit

10 Web Services Architecture BPEL4WS Service Composition Security Reliable Messaging Transactions Composable Service Assurances XSD, WSDL, UDDI, Policy, MetadataExchange Description XML, SOAP, Addressing Messaging HTTP, HTTP, SMTP Transports From joint IBM/MSFT WS Whitepaper at /en-us/dnwebsrv/html/wsoverview.asp

11 Web Services Today Web services is currently an early majority market Many successful deployments A 1 st or 2 nd focus for CIOs and architects Web services add immediate value to a broad range of scenarios Base infrastructure SOAP and WSDL have broad adoption and tool integration Great progress toward enabling security, reliability, and transactions "Web services development projects are at the top of the list of company priorities and one of the last budgets to be raided when budget cuts are made." - Gartner survey of 111 North American Companies B-to-B ecommerce Supply Chain CRM B-to-C ecommerce ERP Other 6% 15% 24% 33% 33% 70% InfoWorld CTO Survey "In what areas will web services be most effective for your company?"

12 WS-* * Specifications Timeline

13 Microsoft Products Implement Web Services Today BizTalk Server 2004.NET Framework Web Services Enhancements v2 SharePoint Windows Server 2003 Indigo Platform Infrastructure Developer Tools Information Bridge Framework Information Worker Tools & Office Web Infrastructure Services Toolkit Dynamic Systems Initiative Business Apps Operations Infrastructure MS CRM Great Plains 8.0 Microsoft Operations Manager 2005 Services MapPoint Web Service Devices Architectural & Prescriptive Guidance.NET Compact Framework

14 Agenda Why Web Services? Where are we today? Where are we heading? What are we doing?

15 Web Services Technology Roadmap Today Windows XP, 2003,.NET Visual Studio 2003, ASMX WSE 1.0, 2.0 Office System 2003 Windows Server 2003 BizTalk Server 2004 SQL Server 2000 Next Indigo (Beta) WSE 3.0 (Tech Preview) Visual Studio 2005 (Beta) Longhorn (Beta) Windows Server (Beta) Future Indigo Longhorn Identity Windows Server Fed Server Visual Studio 2005 WS-I Compliance SQL Server 2005

16 Microsoft Web Services Tools Roadmap V1.0 SOAP Tool Kit V2.0 V3.0 V1.0.NET Framework V1.1 V2.0 SDK Web Services Enhancements V1.0 V2.0 Indigo V3.0 Beta 1 Beta 2 (? Go Live) V1.0 Longhorn

17 Agenda Why Web Services? Where are we today? Where are we heading? What are we doing?

18 European MSFT Innovation Center Web Services Research WS infrastructure for GRID computing Web services security glue and customisation supporting security services + resource-specific specific security mechanisms semantic-aware aware security, consistent across layers dynamic security management Service design and service level agreements Make it easy to Make it easy to create and consume commercial web services

19 Resources Learn more about Web Services Whitepapers Participate in the workshop process Search for each specification by name at Download WSE WS-I

20 Summary "Honestly, in my ideal future, people will no longer think about Web Services as being novel or an end unto itself. Ultimately, Web Services are just the next evolutionary step in software integration. If we do our jobs well and make Web Services an intrinsic part of the platform, then developers can go back to focusing primarily on building applications. I do believe that those applications will be considerably more interesting in a Web Service-based universe, primarily due to the decentralized nature of integration and development." Don Box, Architect, Microsoft Web Services

21 2004 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.