Service Oriented Architecture: Right on Track

Transcription

1

2 Service Oriented Architecture: Right on Track

3 Agenda Defining SOA SOA, Service Orientation, Connected Systems and how they relate Benefits of SOA M icrosoft s vision for S O A Why Microsoft provides the best platform for building your SOA today, and in the future

4 Defining SOA

5 Cutting through the SOA Hype Myth SO is a technology or set of technologies SO is revolutionary SO is the end goal SO requires business and technology overhaul SO is complex and requires an army of consultants Reality SO is an architectural paradigm for building distributed systems SO is evolutionary SO is a means to an end SO can and should be an incremental process SO is easy and can be done inhouse T he only w ay you can use S O A for everything is to renam e everything to S O A Roy Schulte, Gartner

6 Services, Service Orientation and SOA Service An endpoint that reacts to messages Service Orientation An architectural paradigm that employs the following four tenets: Boundaries are explicit Services are autonomous Services share schema and contract, not class Service compatibility is determined based on policy Service Oriented Architecture (SOA) Any architecture the adheres to the Four Tenets of Service Orientation

7 Tenet 1 Boundaries are Explicit Services interact by exchanging messages Each message exchange traverses boundaries and may have costs SO formalizes intentional, and explicit interaction

8 Tenet 2 Share Schema and Contract, Not Types Services expose schemas defining data structures and contracts defining available operations Contracts and schema may be independently versioned over time

9 Tenet 3 Policy defines Service Compatibility Policy is the statement of communication requirements necessary for service interaction Service capabilities and requirements are expressed in terms of a policy expression A policy can contain multiple assertions

10 Tenet 4 Services Are Autonomous A utonom y Indepen dence Topology of a system evolves over time Unlike OO, services do not share behavior Services gracefully handle failure

11 Web Services and SOA Web Services EAI Messaging EDI/B2B Web Site/Portal Distributed Computing Technology Realization SOA Policies Practices Frameworks Standard Protocols Universal Support Existing Assets Low Cost Best Practice Approach

12 Service Orientation Big Picture Business Process View Coarse Grained Web Service Operations Finer Grained Internal Service Operations Fine Grained Object and database calls Business Component Business Component Composite Application Business Process

13 Composite Applications Applications composed of multiple service building blocks Composed, not built Cut across functional silos Portal Devices Office Other Composite Application Composition Platform Existing Systems

14 Benefits of SOA

15 Today Business Issues Increased Customer Focus Outdeliver the Competition Get the most value for your investment Technical Issues Integration costs Development time Future proof against new technologies Heterogeneous environment Support new devices

16 Shift To Service Orientation From Connections = cost Function oriented Build to last Prolonged development Application silos Tightly coupled Object oriented To Connections = value Process oriented Build for change Incrementally deployed Orchestrated solutions Loosely coupled Message oriented

17 Decreased cost SOA Business Benefits Cost Reduces TCO and increase ROI on evolving systems Add value to core investments by leveraging existing assets New systems can be built faster for less money because existing services can be more easily reused Built for flexibility Long term value of interoperability

18 SOA Business Benefits Productivity Increased employee productivity Unlock data Built on existing skills Consolidate Duplicate Functionality

19 SOA Business Benefits Partnership Built for partnerships Standards based Business relationships expressed via service interactions Integration is driven by what is needed, not what is technically possible.

20 SOA Business Benefits Agility Agility - Built for change Helps applications evolve over time and last Abstract the backend and replace over time Access to the business value, no matter what technology delivers it. Focusing on core-competencies Incremental implementation approach is supported.

21 Microsoft leading the way with SOA

22 Microsoft and SOA Connected Systems is the moniker we use to describe the eco-system of SOA enabled applications SOA enables integration Web Services is the messaging fabric for SOA.NET is the programming model for Services Windows and server platform is the hosting platform for Services

23 Microsoft SOA Business Value XML and Web Services Built in from the ground up Servers have had XML objects since 2000 versions.net Framework built for web services More productive development environment Fewer lines of code Larger Ecosystem Faster time to market Integrated Application Environment Developer tool built for the Framework Framework integrated into the OS OS services optimized for the Framework The Application Server is built-in and evolving

24 M icrosoft s S O A S trateg y Leading the charge with Web Services Building Connected Systems Best platform to realize service orientation Visual Studio ASMX, WSE SQL XML Smart Client Office, Windows Mobile Committed to open standards, interoperability WS-I, W3C, OASIS, HL7, AIAG, SWIFT Perceived as leaders even before w e started

25 Visual Studio Team System Edition for Software Architects

26 Application Designer (AD)

27 Endpoints WebServiceEndpoint WebContentEndpoint GenericEndpoint Applications WindowsApplication ASP.NETWebService ASP.NETWebApplication OfficeApplication ExternalWebService ExternalDatabase BizTalkWebService GenericApplication Endpoints and Application Prototypes

28 Defining Web Service Operations

29 Implementing the Application

30 Implementing the Application Application architects and/or developers can implement one or more of the applications on the diagram Implementing is the process of creating the Visual Studio projects (similar to File > New) Generates starter source code, content, and config files based on Visual Studio templates Implementing requires the Team Edition for Software Architects or Team Suite

31 Connected Systems User Interaction Workflow and Process Federated Data Identity and Access Messaging and Services Create seamless, rich user experiences Compose and integrate business processes Provide seamless access to multiple data stores Provide seamless and integrated security Connect heterogeneous systems

32 Microsoft SOA Enablement Visual Studio 2005 BizTalk Server Office and VSTO MOM Active Directory Windows Communication Foundation Architectural Guidance SQL Server

33 Windows Communication Foundation

34 Windows Communication Foundation Th e u n ified program m in g m odel for rapidly buildin g service-orien ted application s on th e W in dow s platform Unification U nifies today s distributed technology stacks Composable functionality Appropriate for use on-machine, cross machine, and cross Internet Interoperability & Integration WS-* interoperability with applications running on other platforms Interoperability w ith today s distributed stacks Productive Service-Oriented Programming Service-oriented programming model Supports 4 tenets of service-orientation Maximized developer productivity

35 U n io n of Today s S tacks Windows Communication Foundation (WCF) (formerly Indigo) Attribute- Based Programming Message- Oriented Programming WS-* Protocols Composability Extensibility Service- Oriented Programming Interop

36 WCF Windows Communication Foundation Class TradeApp { } [WebMethod] message ExecuteTrade(); [ServiceContract] Class EnterpriseTradeApp { [ServiceOperation] message ExecuteTrade (); }

37 Composability in Action Service Model Layer Messaging Layer CLR Type Integration Transaction Behavior Instancing Behavior Reliable Messaging Security Channel Custom HTTP TCP Transport Channel Behaviors Channels Metadata Behavior Instancing Behavior Security Channel HTTP Transport Error Handling Behavior Transaction Behavior Reliable Messaging TCP Transport Concurrency Behavior CLR Type Integration MSMQ Integration Named Pipes Custom Behavior Throttling Behavior Custom Channel Queue Transport

38 Feature Overview Security, Reliability, Transactions End-to-end Security Confidentiality, integrity, authentication, authorization X509, Username/Password, Kerberos, SAML, custom End-to-end Reliable messaging In-order guarantees Exactly once guarantees Transactions Guaranteed atomic success or failure across services

39 Development Productivity Using Visual Studio.NET 2003 class HelloService { } [WebMethod] public String Hello(String Greeting) { } X509CertificateCollection collection = new X509CertificateCollection(); IntPtr blob = Marshal.AllocHGlobal(Marshal.SizeOf( typeof(cryptoapi_blob))); IntPtr data = (IntPtr)((int)blob + Marshal.SizeOf(typeof(CRYPTOAPI_BLOB))); SeqAckRange range = new SeqAcknRange(id, low, high ); SeqAckRange[] ranges = { range }; ReliableQueue.ProcessAcks( ranges ); hr = pitxdispenser->begintransaction (NULL, ISOLATIONLEVEL_SERIALIZABLE, 0, pitxoptions, &pitransaction); return Greeting; 20,379 lines security 5,988 lines reliable messaging 25,507 lines transactions 4,442 lines infrastructure Total lines 56,296

40 Development Productivity Using Visual Studio.NET 2003 and WSE class HelloService { } [WebMethod] public String Hello(String Greeting) { } foreach ( SecurityToken tok in requestcontext.security.tokens { X509SecurityToken token = tok as X509SecToken } SeqAckRange range = new SeqAcknRange(id,low,high ); SeqAckRange[] ranges = { range }; ReliableQueue.ProcessAcks( ranges ); hr = pitxdispenser->begintransaction (NULL, ISOLATIONLEVEL_SERIALIZABLE, 0, pitxoptions, &pitransaction); return Greeting; 10 lines security 1,804 lines reliable messaging 25,507 lines transactions Total lines 27,321

41 Development Productivity Using Visual Studio 2005 and WCF (Indigo) [ServiceContract(SecureChannel, SecurityMode = Windows")] [Reliability(Guarantees.ExactlyOnce Guarantees.InOrder)] [ServiceContract] class HelloService { [ServiceOperation(TransactionFlowAllowed = true)] String Hello(String Greeting) { return Greeting; } 1 lines security 1 lines reliable messaging 1 lines transactions Total lines 3

42 How WCF implements the tenets of SOA Application Code [FederatedSecurity] [Discoverable] [TcpTransport] [ServiceContract] Class MyService { } [ServiceOperation] int MyMethod(string arg) { } What is Exposed Contract Schema (WSDL + XSD) Requires message body <arg> string <arg> Service reply message body <return> int <return> Autonomy (WS-Security Security family, WS-Discovery) Nothing! Boundaries are explicit Assume any messages received are rogue A utom atically announces the service s existence on startup, optionally to central directory Exposes endpoint that responds to Find requests Nothing about implementation/platform exposed. Find and call the service using public standards with any implementation. Contract Policy (WS-Policy) Requires WS-Security, Security, Trust, SCT Requires use of TCP SOAP binding

43 Roadmap Provides Continuity WSE1 WCF will supersede existing connected systems technologies. Other technologies continue to co-exist, interoperate and be supported via support policy WSE2 WSE-n WCF ASMX ASMX Enterprise Services.NET Remoting Com(+) MSMQ

44 Designing for WCF Build services using ASMX Use WSE for WS-* support Keep components within your service boundaries Use System.Messaging for async queued messaging Use Enterprise Services when transactions, activation required Avoid or abstract low-level.net Remoting extensibility such as sinks, channels

45 Summary Service Orientation is an architectural paradigm, conforming to the four tenets Service Orientation reflects the realities of building heterogeneous distributed systems Service Orientation enables agility and the ability to leverage existing assets, without having to rip-and-replace The Microsoft platform provides the best tools to enable you to build Service Oriented systems today and leads the industry in innovation for the future

46 CALL TO ACTION Learn about SOA Ask questions Use Visual Studio 2005 create web services (if you h aven t already, an d see h ow easy it is) Visual Studio 2005 Express (CD in your bags) K eep u p to date w ith M icrosoft s A rch itectu re Vision Sign up for the Architecture Journal