Business Constant: Change

Transcription

1 Overview of Service-Oriented Architecture Jason Bloomberg ZapThink, LLC Take Credit Code: HGOVER Copyright 2006, ZapThink, LLC 1 Business Constant: Change Competition Changing Marketplace Customer Demands Mergers & Acquisitions Business Partners CHANGE Optimizing Processes New Technologies A Business is Never STATIC Copyright 2006, ZapThink, LLC 2 1

2 IT: Fulfilling Business Requirements Business Requirements Service Customers Manage Operations Increase Worker Productivity Communicate with market Ensure reliable and secure operations Develop new products and services Respond to new business drivers IT Capabilities Implement CRM Systems Implement ERP Systems Manage desktop environments Manage server environments Manage systems and web sites Manage network and storage operations Develop applications Copyright 2006, ZapThink, LLC 3 However, it rarely works that way Business Requirements Requirements change? IT Interpretation Interpretations often inaccurate or limited Lengthy development cycles impervious to change Final Implementation Long development cycle Implementations cast in concrete Result: IT that places limitations on Business Copyright 2006, ZapThink, LLC 4 2

3 We ve had IT challenges for years Copyright 2006, ZapThink, LLC 5 but even after yesterday s promises Copyright 2006, ZapThink, LLC 6 3

4 we still have the same IT mess, only worse. Copyright 2006, ZapThink, LLC 7 The Integration Challenge The N-squared Integration Problem: B2B Exchanges NoN- or SEMI- STRUCTURED Web Site Office Documents Content Management ERP / CRM Systems RDBMS STRUCTURED Mainframe / Legacy Source: Copyright 2002 ZapThink, LLC File System Networked Devices Directory Copyright 2006, ZapThink, LLC 8 4

5 Made Worse by External Integration B2B Exchanges B2B Exchanges NoN- or SEMI- STRUCTURED Web Site Office Documents Content Management ERP / CRM Systems RDBMS STRUCTURED NoN- or SEMI- STRUCTURED Web Site Office Documents Content Management ERP / CRM Systems RDBMS STRUCTURED Mainframe / Legacy Mainframe / Legacy Source: Copyright 2002 ZapThink, LLC Source: Copyright 2002 ZapThink, LLC File System File System Networked Devices Directory Networked Devices Directory 70% of IT development budgets are spent on integrating different systems ZapThink Copyright 2006, ZapThink, LLC 9 What have you seen? Have you seen any issues similar to those just pointed out in your organization? The discrepancy between IT capabilities and business needs? IT challenges, new promises that turned out to create new problems? Integration challenges exacerbated by external B2B integration requirements? Copyright 2006, ZapThink, LLC 10 5

6 Integration Approaches of Yesterday Custom Integration: Coding to Interfaces APIs: COM, Java, COBOL, Assembly? Distributed Computing?: DCOM, CORBA Screen-Scraping and Emulation (3270 and HTML) Message-Queues EAI and B2Bi Middleware Automating interface-level integration Bus or hub-and-spoke architecture Fundamentally brittle approaches to integration Copyright 2006, ZapThink, LLC 11 There s Got to Be a Better Way! Rather than trying to simply throw more software and iron at the problem, we need a better way of organizing our IT resources Service-Oriented Architecture (SOA) represents a fundamental evolution in the IT industry The core business motivation is business agility. Rather than rip and replace old systems make them work better together We don t want more middleware for our middleware As fundamental a change as mainframe to client/server or client/server to the Internet Copyright 2006, ZapThink, LLC 12 6

7 SOA: Definition An approach to building and managing distributed computing infrastructures that considers IT resources as Services available and discoverable on a network. Copyright 2006, ZapThink, LLC 13 SOA Features SOA is architecture a set of best practices for the organization and use of IT Abstracts software functionality as loosely-coupled, businessoriented Services Services can be composed into business processes (which are also Services) in a declarative manner Copyright 2006, ZapThink, LLC 14 7

8 SOA: Implication Rather than dealing with isolated systems that must be integrated after the fact, Service Orientation provides business users with understandable Services they can call upon and compose into business processes as needed building systems that can adapt as the business changes. Copyright 2006, ZapThink, LLC 15 SOA: Benefit The Service Orientation vision is therefore one of providing the business values of agility and flexibility for users of technology, coupled with an abstraction layer that simplifies the complexity of today s heterogeneous IT environments from those users. Copyright 2006, ZapThink, LLC 16 8

9 Characteristics of SOA Services are loosely coupled making a change to a service provider does not mandate changing any service consumers. Business processes are composed of services, and are in turn exposed as services. Services are policy-driven business users can change how a service behaves. Systems are inherently integrated by virtue of composable services not through layers of middleware. Copyright 2006, ZapThink, LLC 17 Characteristics of SOA (Cont.) Services leverage legacy systems SOA does not mandate replacement of runtime infrastructure. In SOA, metadata controls how the system behaves instead of code business logic trumps application logic. In SOA, it s the contracted interface that matters, not the underlying runtime environment. Copyright 2006, ZapThink, LLC 18 9

10 SOA is Enterprise Architecture What is Architecture? The fundamental organization of a system embodied by its components, their relationships to each other and to the environment and the principles guiding its design and evolution. (IEEE P1471/D5.3) Enterprise architecture includes: An aggregated architecture of all the individual IT systems within an organization The human element within the enterprise Systems, people, and organizational constructs at other companies that have relationships with the enterprise Individual consumers who are that enterprise s customers Corporate governance Copyright 2006, ZapThink, LLC 19 SOA is a discipline Implementing a Service-Oriented Architecture is a journey Moving from proprietary interfaces to standards-based ones is just the first step SOAs require a combination of security, management, governance, integration, process, and architecture tools What are the right steps to guarantee overall success? How can you guarantee an ROI while reducing risk? Copyright 2006, ZapThink, LLC 20 10

11 Abstraction? ESB? Service Network? Fabric? Don t Get Lost in the Terminology EAI? EDA? Service Grid? SOA Infrastructure? SOA? There are many styles for SOA implementation Focus on your goals: Reuse? Governance? Reduced integration cost? Agility? Copyright 2006, ZapThink, LLC 21 SOA s Little Secret You can build SOA with whatever software you already have (for the most part) When considering purchasing software for your SOA initiative, look to fill the functionality gaps in your current portfolio Don t just add middleware for your middleware! Copyright 2006, ZapThink, LLC 22 11

12 SOA: A Technology View Composite Application Delivery Business Services Business Processes SOA Fabric Atomic Services Data Integration Legacy Applications and Middleware Databases Rich Clients Security Discovery Management A B C D E Composite Apps Messaging Routing Transform A B C D E Governance and Security Infrastructure Source: MW2 Consulting Copyright 2006, ZapThink, LLC 23 Have We Been Here Before? Service-Oriented Architectures have been around a while CORBA (Common Object Request Broker Architecture) and DCOM (Microsoft Distributed Component Object Model) two familiar examples What s new this time? Copyright 2006, ZapThink, LLC 24 12

13 The Difference is Web Services WS-Policy WS-MessageData UDDI WS-AtomicTransaction Web Services Coordination WS-Transfer Web Services for Remote Portlets Web Services Transaction WS-BusinessActivity WSDL Web Services Metadata Exchange WS-Addressing BPEL and BPELJ WS-Coordination Web Services Eventing WS-Choreography Interface SOAP WS-Trust WS-Federation Web Services Business Activity Framework WS-CallBack Web Services Dynamic Discovery WS-SecureConversation WS-Acknowledgement WS-ReliableMessaging Copyright 2006, ZapThink, LLC 25 Web Services = SOA? SOAP wrappers / Web Services adapters Replace proprietary APIs with standards-based APIs Still fine grained, may still be tightly coupled n-tier architecture with addition of Web Services interface Less secure and more verbose Problem: Same cake with new frosting Copyright 2006, ZapThink, LLC 26 13

14 SOA vs. Web Services Standard architecture with Web Services SOA leveraging Web Services Transactions Messaging Security Transactions Messaging Security Messaging Security Management Business Services Data Services Discovery SOA Abstraction Layer Transactions Messaging Security Monitoring Web Services Web Services Web Services EIS Custom App Mainframe Logic Web Services EIS Web Services Custom App Web Services Mainframe Logic Source: HP Copyright 2006, ZapThink, LLC 27 Web Services are the Trees. Service Orientation is the Forest Copyright 2006, ZapThink, LLC 28 14

15 Service orientation the next big thing? Approach Timeframe Programming Model Business Motivations Mainframe timesharing 1960s 1980s Procedural (COBOL) Automated business Client/server 1980s-1990s Database (SQL) and fat client (PowerBuilder, Visual Basic) Computing power on the desktop n-tier/web 1990s-2000s Objectoriented (Java, COM) Internet/eBusiness Service orientation 2000s Serviceoriented (SOAP, WSDL, UDDI) Business agility Copyright 2006, ZapThink, LLC 29 The Business Benefits IT resources are available as needed to businesses as Services Business users empowered to create and manage business logic The Service-oriented abstraction layer enables companies to run their operations and conduct business with each other in a dynamic and automated fashion Business drives IT, and agile IT enables agile businesses Copyright 2006, ZapThink, LLC 30 15

16 Business Agility What companies require is Business Agility»Responding quickly to change, and»leveraging change for competitive advantage J Copyright 2006, ZapThink, LLC 31 SOA Hotspots Four key areas of SOA investment Reduction in integration expense Increase in Service / asset reuse Increase in business agility Enablement of governance & compliance Key Problem areas EAI replacement Legacy enablement/migration Shared Service development Governance Embedding processes in the extended enterprise Copyright 2006, ZapThink, LLC 32 16

17 Thank You! Copyright 2006, ZapThink, LLC 33 Photos Lisa Polucci 17