Service Oriented Architecture

1. Service OrientedArchitecture Pooya Darugar Architect, Microsoft Gulf

2. Agenda • What is SOA, What isn’t SOA • The important A in SOA • Business Modeling • How to get started • The forgotten aspects of SOA

3. SOA is simply…. A design philosophy that leverages existing investments in the creation of flexible solutions that are more responsive to your business needs What about all those buzz words and complicated specs I keep hearing about??

4. Common Myths about SOA Facts Myths SOA is a design philosophy independent of any product, technology or industry trend SOAs may be realized via web services but using web services will not necessarily result in a SOA EDI and CORBA were early examples of SO SOA is not a methodology SOA should be incremental and build on your current investments SOA can be done in house SOA is a means, not an end Deliver a solution, not a SOA SOA is a technology SOA requires Web Services SOA is new and revolutionary SOA ensures the alignment of IT and business SOA requires a complete technology and business processes overhaul SOA requires an army of consultants We need to build a SOA

5. Traditional model User Data Entities LoB Systems Security LoB Systems Data Security Entities

6. SOA Applied User Adapter Adapter Billing Service Product Service Security Service BP Platform ID Service LoB Systems LoB Systems Customer Service Service Agent Data Services

7. How do you get there?

8. SOA Applied Step 2: Group Similar Functions, Expose as a Service Step 1: Ignore Solution Boundaries User Billing Service ID Service Data Entities LoB Systems Security LoB Systems Data Security Entities

9. SOA Applied Step 3: Hide data source behind services User Billing Service Data Services ID Service Data Entities LoB Systems Security LoB Systems Data Security Entities

10. SOA Applied Step 4: Expose Entities as Services for “Single View” of Customer, Product, others… User Billing Service Product Service ID Service Entities LoB Systems Security LoB Systems Security Entities Customer Service Data Services

11. SOA Applied Step 5: Hide security behind reusable services User Security Service Billing Service Product Service ID Service LoB Systems Security LoB Systems Security Customer Service Data Services

12. SOA Applied Step 6: Use service agents for dynamic assembly of rich user experiences across multiple devices User Security Service Billing Service Product Service ID Service LoB Systems LoB Systems Customer Service Data Services Service Agent

13. SOA Applied Step 7: Use a BP Platform for aggregating services into workflows and integration with legacy systems User Security Service Billing Service Product Service ID Service Adapter Adapter BP Platform LoB Systems LoB Systems Customer Service Data Services Service Agent

14. SOA Applied Step 8: Optimize infrastructure to take advantage of the services-based environment User Security Service Billing Service Product Service ID Service Adapter Adapter BP Platform LoB Systems LoB Systems Customer Service Service Agent Data Services

15. SOA – what will it deliver? • What have we really created: • Modeling the business • Re-usable components Agility

16. Modeling Systems - The Classic Way System Model (Classic Client-Server Based) TechnologyModel Business Model

17. Why Do Business and IT Miscommunicate? • Business people are not good at explaining what they do • Often fail to distinguish between what they do and how they do it • Use jargon and assume a level of basic knowledge • IT people are not good at explaining what they do • Often fail to express strategies in terms of business value • Use jargon and assume a level of basic knowledge • Important to finally fix this because the role of IT is changing: • Used to be cost reduction • Now it is a major business differentiator

18. Modeling Systems - The Modern Way System Model (Modern Service Based) Business Model ServiceModel TechnologyModel The service model is the common ground between business and IT

19. Modeling Systems Business Model Service Model Technology Model Service Interface What Capabilities Service Contract Service Implementation SLE SLA Service Host Orchestration Service Management How  Business Processes Orchestration Engine

20. Modeling Systems Business Model Service Model Technology Model Service Interface What Capabilities Service Contract Service Implementation SLE SLA Service Host Orchestration Service Management How  Business Processes Orchestration Engine

21. Microsoft Motion Business Architecture Modeling • Has two major constituents: • A capability map describing business capabilities • A simple, short, prescriptive process of analysis • Exploits insights: • Business capabilities are relatively stable and enduring • Helps address two fundamental problems: • IT projects constantly repeat themselves… • … and only rarely introduce true business innovation

22. Motion Overview • Motion is • Patent-pending business architecture model with tools • Set of heat mapping tools • Training classes for using the model and the tools • endorsed by the creators of Six Sigma and Business Process Reengineering • Motion delivers • Business architecture map (with properties) • Project recommendations – what to change in terms of people, process, and IT, in the context of cost, benefit, and risk • Several forms are available • 2-4 week business architecture training projects • Motion Methodology – one or all four phases, usually two weeks per phase • Not strategy consulting – it is business consulting • Proven • Mature

23. Customer-Facing Channel Partners Customers Develop Products & Services Generate Demand Logistics Providers Collaborate Suppliers Deliver Products & Services Plan and Manage the Enterprise Governments (regulation and infrastructure) Financial Providers Capability Maps

24. Customer-Facing Channel Partners Customers Develop Products & Services Generate Demand Logistics Providers Collaborate Suppliers Deliver Products & Services Plan and Manage the Enterprise Governments (regulation and infrastructure) Financial Providers Capability Maps • 3.3 Procurement • Sourcing and Supplier Contract Management • Purchasing • Receiving of Indirect/ Capital Goods • 3. Deliver Products and Services • Provide Service • Advanced Planning • Procurement • Produce Product • Logistics • 3.3.2 Purchasing • Request Resources • Acquire/Purchase Resources • Manage Suppliers • 3.3.2.1 Request Resources • Create Purchase Requisitions • Manage Requisition Approval Process • Perform Encumbrance Check • Create Auction Bids

25. Anatomy of a Capability Start Technology Procedures People

26. Value proposition Operating model Customer-Facing Channel Partners Customers Capabilities Develop Products & Services Generate Demand Partnerships Metrics IT project portfolio Outsourcing Collaborate Logistics Providers Suppliers IT projects Offshoring Plan and Manage the Enterprise Deliver Products & Services SOA Self-service Governments (regulation and infrastructure) Financial Providers What Use is a Business Architecture Model?

27. Ways to approach SOA • Top Down – eg. Motion • Bottom Up

28. Moving to SOA: The Top-Down Approach How it works: Define a business architecture Using, for example, Microsoft’s Motion methodology Discover what services are required Create service-oriented apps based on this Pros: It’s elegant, clean, and sensible Cons: It’s very difficult in most organizations Getting the up-front funding and business buy-in is tough Keeping up with business change is also tough

29. Moving to SOA: The Bottom-Up Approach How it works: Build a service-oriented app Then build another one Next, work on central SOA issues, e.g., security and management Then build another service-oriented app . . . Pros: It’s the only approach that has worked in most organizations Cons: It’s an inelegant, piecemeal way to address the problem

30. SOA ApproachMiddle-out (Real World SOA) SOA is about Agility Agile principles Requirements will change Feedback, feedback, feedback! Measurement and Adjustments Get good people to work together effectively SOA center of excellence Holistic view but choose part of the business Start small then scale-up Pragmatism Oscillate top down/bottom up

31. Things to Consider

32. Service-Oriented Analysis Issues Entity Identification Entity Factoring Service Identification Service Factoring Process Specification Endpoint (Touchpoint) identification Role Mapping SLAs … Clients and Agents Technology Architecture Process Services Infrastructure Services Activity Services Entity Services Information Architecture

33. Service-Oriented Design Issues Schema definition Message definition Contract definition Message handling Process management Transaction model Operational compliance Exception handling Message to Object mapping Refinement of Analysis … Service Process Service DocumentA DocumentC-1 DocumentC-2 Contracts EitherC-1 or C-2 DocumentB Process

34. Service Operations Issues Security Access control Monitoring Management QoS and SLA enforcement Versioning Scalability Dealing with unreliability Exception routing Caching Service Log Sign Message Processing Infrastructure Service Serialize Reliable messaging Encrypt Authorize Audit Message Processing Infrastructure Deserialize Authenticate

35. Deciding Which Services to Expose This is the hardest aspect of building a service-oriented application And almost nobody has much experience The goal: define the right use cases for future apps that will use these services Some suggestions: Expose business logic via a services wrapper Don’t expose objects directly Expect to make mistakes And be supportive when your customers screw up Don’t let developers decide which services to expose Start with the Contract and Schema Use industry standards if available

36. What About Business Analysts? Some organizations have people in a business analyst role In a service-oriented world, they’ll matter more Where BAs can potentially help: Defining services Creating and updating process logic (orchestrations) Defining and modifying business rules

37. SOA – Organizational Commitment SOA and Web Service Advantages are Not Automatic Reality is, benefits are often only realised when combined with Change in culture Investment in future needs, not just today’s short term issues Proper understanding of business requirements (today and tomorrow) Careful analysis and system design Flexible and agile implementations using appropriate technology and componentization Business Process Re-engineering Business commitment and involvement Adequate funding recognising changes in ownership and responsibility

38. Summary • SOA is about Architecture • Service Oriented Infrastructure make the plumbing for SOA easier • This is the part you can buy from a vendor • SOA - business modeling, service modeling • Motion • Real World SOA – middle out approach • It doesn’t end there • Developing services is the easy part • Managing and governing them in a loosely coupled world is much more complex

39. Thank YOU Pooya Darugar pooyad@microsoft.com http://blogs.msdn.com/pooyad