SOA, Service-Orientation & Cloud Computing: The Connection Points

Transcription

1 SOA, Service-Orientation & Cloud Computing: The Connection Points Thomas Erl SOA Systems Inc.

2 Prentice Hall Service-Oriented Computing Series Started in 2003 Text Books are an Official Part of the SOACP Curriculum Each Book Complements the other to form an End-to-End Library Library of Text Books based on Consistent Definitions, Terminology, Conventions High Level of Community Involvement (over 25 Contributing Authors from major organizations such as Microsoft, Oracle, IBM, SAP, US DoD, etc. ) Visit: soabooks.com

3 Agenda SOA & Service-Orientation 101 (5 minutes) Cloud Computing 101 (5 minutes) The Connection Points: Overview Service-Oriented Computing Cloud Computing Benefits SOA Characteristics Cloud Characteristics Service-Orientation Principles Cloud Mechanisms SOA Types and Clouds

4 SOA & Service-Orientation 101

5 SOA & Service-Orientation 101 There is a set of strategic goals associated with service-oriented computing. These goals represent a specific target state. Service-orientation is the design paradigm provides a proven method for achieving this target state. When we apply service-orientation to the design of software, we build units of legitimately service-oriented logic called services. Service-oriented solutions are comprised of one or more services. To build successful service-oriented solutions, we need a distributed technology architecture with specific characteristics These characteristics distinguish the technology architecture as being service-oriented. This is SOA.

6 SOA & Service-Orientation 101 Services (top left) are delivered into a service inventory (right) from which service compositions (bottom left) are drawn. These basic elements establish the fundamental service-orientation dynamic which is supported by specific characteristics of technology architecture (which distinguish SOA).

7 Service-Oriented Computing Goals & Benefits Increased Intrinsic Interoperability Increased Federation Increased Business and Technology Alignment Increased Vendor Diversification Options Increased ROI Increased Organizational Agility Reduced IT Burden

8 Service-Oriented Computing Goals & Benefits The first four goals lead to the attainment of the latter three benefits.

9 Service-Orientation Principles & SOA Characteristics Service-Orientation Principles Standardized Service Contract Service Loose Coupling Service Abstraction Service Reusability SOA Characteristics Business-Driven Vendor-Neutral Enterprise-Centric Composition-Centric Service Autonomy Service Statelessness Service Discoverability Service Composability

10 SOA Types Service Architecture (inner circle) Service Composition Architecture Service Inventory Architecture Service-Oriented Enterprise Architecture (outer circle)

11 Cloud Computing 101

12 Cloud Computing Fundamental Terms & Concepts Service Service Consumer Service Provider Service Agent Cloud IT Resource Scaling Cloud Service Cloud Service Consumer Cloud Service Provider Cloud Provider Cloud Consumer Organizational Boundary Trust Boundary Virtualization

13 Cloud Computing Common Benefits & Challenges Benefits Reduced Investment and Proportional Costs Increased Scalability Increased Availability and Reliability Challenges Increased Security Vulnerabilities Reduced Operational Governance Control Limited Portability Between Cloud Providers Multi-regional Compliance and Legal Issues

14 Cloud Computing Mechanisms & Cloud Characteristics Cloud Computing Mechanisms Virtual Server Ready-Made Environment Automated Scaling Listener Failover System Multi-Device Broker Pay-for-Use Monitor State Management Database Resource Replication Cloud Characteristics On-Demand Usage Ubiquitous Access Multitenancy Elasticity Measured Usage Resilient Computing

15 Cloud Computing Delivery & Deployment Models Delivery Models Infrastructure-as-a-Service (IaaS) Platform-as-a-Service (PaaS) Software-as-a-Service (SaaS) Deployment Models Public Cloud Community Cloud Private Cloud Hybrid Cloud

16 The Connection Points: Overview

17 Overview Any distributed technology can be used as part of service-oriented architectures or they can be used as part of other types of distributed architectures. Some technology innovations are more suitable for SOA than others. Cloud computing introduces distributed technology innovations that can be used independent of SOA or together with SOA. The use of cloud technologies can directly help realize the strategic goals of service-oriented computing by extending and enhancing service-oriented architectures and SOA and the application of service-orientation can directly enhance the design quality of cloud-based solutions, especially those using shared services.

18 Overview To better understand how cloud computing can relate to SOA, we need to study the following specific relationships: Service-Oriented Computing Benefits Cloud Computing Benefits SOA Characteristics Cloud Characteristics Service-Orientation Principles Cloud Mechanisms Additionally, we need to understand how service-oriented architecture implementations can relate to cloud environments.

19 Connection Points SOA & Service-Orientation Increased ROI Increased Organizational Agility Reduced IT Burden Business-Driven Vendor-Neutral Enterprise-Centric Composition-Centric Standardized Service Contract Service Loose Coupling Service Abstraction Service Reusability Service Autonomy Service Statelessness Service Discoverability Service Composability Cloud Computing Reduced Investment and Proportional Costs Increased Scalability Increased Availability and Reliability On-Demand Usage Ubiquitous Access Multitenancy Elasticity Measured Usage Resilient Computing Virtual Server Ready-Made Environment Automated Scaling Listener Failover System Multi-Device Broker Pay-for-Use Monitor State Management Database Resource Replication

20 Service-Oriented Computing Benefits Cloud Computing Benefits

21 Overview Service-Oriented Computing Benefits Increased ROI Increased Organizational Agility Reduced IT Burden Cloud Computing Benefits Reduced Investment and Proportional Costs Increased Scalability Increased Availability and Reliability

22 Service-Oriented Computing Benefit: Increased ROI ROI (return on investment) represents the tangible value and costsavings that something provides when compared to the cost of producing and governing it. The Reduced Investment and Proportional Costs benefit provided by cloud computing can help increase the ROI of service-oriented solutions. Some or all parts of a service-oriented solution and its underlying infrastructure can be designed to leverage leased cloud-based IT resources that incur costs proportional to their usage. This can reduce the risk of purchasing on-premise IT resources that may not be fully utilized or that may be over-utilized (both of which are situations that can reduce ROI).

23 Service-Oriented Computing Benefit: Increased Organizational Agility Agility is comparable to responsiveness, meaning that an organization that is more responsive can react and adapt to change more efficiently and effectively. The Reduced Investment and Proportional Costs benefit provided by cloud computing can help increase responsiveness by allowing organizations to more cost-effectively extend existing serviceoriented solutions or build new solutions without having to invest in and deploy upgraded or new on-premise IT resources. The Increased Scalability benefit provided by cloud computing enables service-oriented solutions to scale more responsively by leveraging several cloud mechanisms and characteristics that enable the elastic, on-demand scaling of IT resources.

24 Service-Oriented Computing Benefit: Reduced IT Burden Consistently applying service-orientation results in an IT enterprise with: reduced waste and redundancy reduced size and operational cost reduced overhead associated with its governance and evolution These results combined represent a reduction in the overall burden that the IT enterprise can impose upon the organization.

25 Service-Oriented Computing Benefit: Reduced IT Burden The ultimate goal of service-oriented computing is to create a leaner, more agile IT enterprise that is less of a burden on the organization and more of an enabling contributor to its strategic goals. The Reduced Investment and Proportional Costs benefit of cloud computing supports this by decreasing the up-front cost of service-oriented solution delivery and by tying the operation cost to the solution s actual usage. The Increased Scalability benefit of cloud computing supports this by enabling the organization to flexibly scale service-oriented solutions using cloud-based IT resources. The Increased Availability and Reliability goal of cloud computing supports this by allowing organizations to leverage large amounts of cloud-based IT resources that are further supported by failover systems.

26 SOA Characteristics Cloud Characteristics

27 Overview SOA Characteristics Business-Driven Vendor-Neutral Enterprise-Centric Composition-Centric Cloud Characteristics On-Demand Usage Ubiquitous Access Multitenancy Elasticity Measured Usage Resilient Computing

28 SOA Characteristic: Business-Driven The business-driven characteristic of SOA requires that the technology architecture be designed so that it can be kept in constant synch with how the business evolves over time. The following cloud computing characteristics can support the creation of a business-driven technology architecture by enabling the architecture to effectively scale and expand in response to changing business requirements: On-Demand Usage Multitenancy Elasticity Furthermore, the Ubiquitous Access characteristic can support business change by broadening access to cloud-based service-oriented solutions.

29 SOA Characteristic: Vendor-Neutral The vendor-neutral characteristic of SOA requires that the technology architectural model be designed independently from proprietary vendor technologies in order to maintain the freedom to diversify its implementation by leveraging multiple vendor technology innovations. Cloud providers only support this characteristic to the extent that they can support established industry standards. Because many cloud providers continue to impose proprietary requirements upon cloud-based solutions, this SOA characteristic is not widely supported.

30 SOA Characteristic: Enterprise-Centric The enterprise-centric characteristic of SOA requires that the technology architecture support services that span traditional application silos. This primarily pertains to shared services that can be reused as part of different solutions that automate different business processes. The IT resource allocation to enable the reuse of shared cloud-based services is directly supported by the On-Demand Usage, Multitenancy, Elasticity, Measured Usage characteristics of clouds. Enterprise-centricity is further supported by the Ubiquitous Access characteristic which can broaden the reuse of cloud-based shared services to new cloud service consumers.

31 SOA Characteristic: Composition-Centric This composition-centric characteristic of SOA refers to the ability of the technology architecture to accommodate constant change via the repeated composition of shared services. The Multitenancy and Elasticity characteristics of cloud computing support the continual recomposition of services by providing flexible IT resource allocation. The Resilient Computing characteristic of cloud computing supports recomposition by increasing the reliability and availability of recomposed services.

32 Service-Orientation Principles Cloud Mechanisms

33 Overview Service-Orientation Principles Standardized Service Contract Service Loose Coupling Service Abstraction Service Reusability Service Autonomy Service Statelessness Service Discoverability Service Composability Cloud Computing Mechanisms Virtual Server Ready-Made Environment Automated Scaling Listener Failover System Multi-Device Broker Pay-for-Use Monitor State Management Database Resource Replication

34 Service-Orientation Principle: Standardized Service Contract Services within the same service inventory are in compliance with the same contract design standards. This design principle applies to the design of cloud-based service contracts the same way it does to the service contracts of on-premise services. The extent to which this principle can be applied depends on the extent to which cloud providers support industry standards that pertain to service contracts (such as interface definition and messaging), and the extent to which cloud consumers can apply their own design standards to service contracts (such as establishing canonical data models among a collection of services). The cloud mechanism primarily affected by this principle is the Multi- Device Broker, as it is responsible for providing service contracts for multiple cloud service consumer devices.

35 Service-Orientation Principle: Service Loose Coupling Service contracts impose low consumer coupling requirements and are themselves decoupled from their surrounding environment. Cloud-based services with service contracts are commonly based on a technology architecture wherein the contract is decoupled from the service implementation. This principle requires that the service contract itself be further designed to ensure that it does not relate to proprietary characteristics of the underlying implementation, so as to not impose negative coupling upon service consumers. Therefore, as with the Standardized Service Contract principle, this principle is applied to cloud-based services in the same manner as it is to on-premise services and primarily affects the usage of the Multi-Device Broker mechanism.

36 Service-Orientation Principle: Service Abstraction Service contracts only contain essential information and information about services is limited to what is published in service contracts. The goal of this principle is to hide information in order to allow a service to change its implementation with minimal impact on service consumers. Cloud platforms (especially public clouds) normally hide the backend implementation from cloud consumers, which means this principle is often naturally applied as a result of building cloud-based solutions. The Service Abstraction principle does not relate directly to any cloud computing mechanisms, but it does affect the design of cloud service contracts and the authoring of SLAs.

37 Service-Orientation Principle: Service Reusability Services contain and express agnostic logic and can be positioned as reusable enterprise resources. This principle pertains to SaaS offerings and any shared cloud service with a published service contract. Any cloud service can be designed with an agnostic functional context, independent of the cloud deployment or delivery model. The cloud mechanisms primarily related to the Service Reusability principle are Automated Scaling Listener, Failover System, Multi- Device Broker, Pay-for-Use Monitor, and State Management Database.

38 Service-Orientation Principle: Service Autonomy Services exercise a high level of control over their underlying runtime execution environment. If a service has exclusive control over underlying resources, the predictability of the service behavior is optimized. The applicability of this principle is within cloud platforms is dependent on where the underlying IT resources are located. Virtualized IT resources are not naturally autonomous because they rely on shared underlying physical resources. Therefore, applying the Service Autonomy principle within cloud environments can be more challenging than in on-premise environments. Related cloud mechanisms are Virtual Server and Resource Replication.

39 Service-Orientation Principle: Service Statelessness Services minimize resource consumption by deferring the management of state information when necessary. The retention of state data in memory is a primary concern to the scalability of a cloud platform. This principle shares that concern and therefore supports the cloud s goal of maximizing available IT resources in order to maximize scalability potential. The Service Statelessness principle is directly related to the State Management Database mechanism.

40 Service-Orientation Principle: Service Discoverability Services are supplemented with communicative meta data by which they can be effectively discovered and interpreted. This principle is applied to the service contracts and associated SLAs of cloud-based services as it is to on-premise services. There are no cloud mechanisms directly related to the Service Discoverability principle.

41 Service-Orientation Principle: Service Composability Services are effective composition participants, regardless of the size and complexity of the composition. This principle is primarily related to the design of SaaS offerings and shared cloud services, although it can also have an effect on the complexion of PaaS and IaaS environments. The following cloud mechanisms can be utilized to support the repeated composition of cloud-based services: Virtual Server, Automated Scaling Listener, Failover System, Pay-for-Use Monitor, State Management Database, Resource Replication

42 SOA Types and Clouds

43 SOA Type: Service Architecture A service architecture is a technology architecture limited to the physical design of a software program designed as a service. The example shows a high-level service architecture view for a Web service, depicting the parts of the surrounding infrastructure utilized to fulfill the functional requirements of all capabilities.

44 SOA Type: Service Architecture The following variation of the service architecture positions the database for the user directory and the shared databases installed on virtual servers located in a cloud.

45 SOA Type: Service Composition Architecture The fundamental purpose of delivering a series of independent services is so that they can be combined into service compositions. Each service composition has a corresponding service composition architecture. The diagram shows a service composition viewed from a physical architecture perspective illustrating how each composition member s underlying resources provide the functionality required to automate the process logic for a single service capability.

46 SOA Type: Service Composition Architecture The services within a service composition can be distributed, as follows: 1. The service composition architecture can reside inside the organization. 2. The service composition architecture can reside inside the cloud. 3. The service composition architecture can span the organization and the cloud. The example depicted on the next page shows a variation of the previously shown service composition architecture that positions all IT resources accessed by the three services in a cloud.

47 SOA Type: Service Architecture

48 SOA Type: Service Inventory Architecture A service inventory is a collection of independently standardized and governed services delivered within a pre-defined architectural boundary. This collection represents a meaningful scope that exceeds the processing boundary of a single business process and ideally spans numerous business processes. Similar to a service composition architecture, a service inventory architecture can reside in a cloud, in an on-premise environment, or it can span both.

49 SOA Type: Service-Oriented Enterprise Architecture A service-oriented enterprise architecture represents all service, service composition, and service inventory architectures that belong to a specific IT enterprise. It often is defined as a documentation of the parts of the IT enterprise that have adopted SOA, in which case it may exist as a subset of the parent enterprise technology architecture. Since a service-oriented enterprise architecture encompasses all other SOA types, it would further encompass any SOA types residing fully or partially within cloud platforms.

50 SOASchool.com SOA Certified Professional (SOACP) De facto Vendor-Neutral Industry Accreditation Program 26 Course Modules, 10 Certifications ( World-Wide Prometric Testing ( Some Exams Apply to Multiple Certifications (see matrix at Curriculum Overseen by SOA Education Committee (

51 Certifications Each certification represents an area of specialization that relates to a common role on a typical SOA project team. Course modules and exams can be mapped to project roles in order to allocate resources based on proven skillsets. All certifications are based on the same vendor-neutral foundation of knowledge: concepts, terminology, patterns, principles, practices, technologies, etc. Upcoming certifications include: SOA Java Developer SOA Quality Assurance Specialist

52 How to Get Trained & Certified Public Workshops Regular workshops open for public registration and taught by Certified SOA Trainers On-Site Training A Certified SOA Trainer can travel to your location to deliver a custom workshop info@soaschool.com Self-Study Self-paced training program for remote study anywhere in the world Exams & Testing Exams available world-wide via the Prometric testing network. Discounted exam vouchers available when attending public or private workshops ( Self-Study Kits include pre-paid Prometric Exam Vouchers.

53 Contact General information: For information about the Prentice Hall Service-Oriented Computing Series: For information about SOA Certified Professional Self-Study Kits and Programs: For the current calendar of instructor-led certification workshops: To view the monthly online SOA Magazine: The SOA Manifesto ( and the Annotated SOA Manifesto ( Questions?