1 / 49

Comparative Integrated Systems CIS007-3

Comparative Integrated Systems CIS007-3. Week 13: Service-Oriented Architecture (Overview). Sue Brandreth. Current Environment?. Problems addressed by SOA…. Purpose of Architecture – To Manage Interdependencies. Direction of System Architecture. Topics covered.

nga
Download Presentation

Comparative Integrated Systems CIS007-3

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Comparative Integrated SystemsCIS007-3 Week 13: Service-Oriented Architecture (Overview) Sue Brandreth

  2. Current Environment?

  3. Problems addressed by SOA….

  4. Purpose of Architecture – To Manage Interdependencies

  5. Direction of System Architecture

  6. Topics covered • What is a Services-Oriented Architecture (SOA)? • What is a Service? • What is SOA? • When and why do we need a SOA? • SOA architecture? How does a SOA work? • Traditional architecture vs SOA architecture • Key standards and technology of SOA • What makes a SOA different? • Challenges? • When and why would you use SOA? • How does SOA support business application flexibility, agility, scalability and quality?

  7. Topics covered • Who should adopt SOA? • What kind of business and people would take advantages of SOA? • Who adopted SOA? Different implementations of SOA

  8. Why Service Oriented Architecture (SOA)?

  9. What is a Service Oriented Architecture (SOA)? • A means of developing distributed systems where the components are stand-alone services. • Services may execute on different computers from different service providers. • A service changes business data from one state to another. • Standard protocols have been developed to support service communication and information exchange.

  10. What is a Service Oriented Architecture (SOA)? IBM Definition: Service-Oriented Architecture is a business-driven IT architecture approach that supports integrating a business as linked, repeatable business tasks, or services. SOA helps today’s business innovate by ensuring that IT systems can adapt quickly, easily and economically to support rapidly changingbusinessneeds. SOA helps customers increase the flexibility of their business processes, strengthen their underlying IT infrastructure and reuse their existing IT investments by creating connections among disparateapplications and informationsources.

  11. What is a Service Oriented Architecture (SOA)? • A set of components which can be invoked, and whose interface description can be published and discovered (W3C definition). • Service-oriented architecture is a client/server design approach in which an application consists of software servicesand software service consumers (also known as clients or servicerequesters). • SOA differs from the more general client/server model in its definitive emphasis on loose coupling between software components, and in its use of separately standing interfaces

  12. What is a Service Oriented Architecture (SOA)?

  13. What is a Service Oriented Architecture (SOA)? • A service can be defined as: • A loosely-coupled,reusablesoftwarecomponentthat encapsulates discretefunctionalitywhich may be distributed and programmaticallyaccessed. • A web service is a service that is accessed using standard Internet and XML-based protocols. • A critical distinction between a service and a component as defined in component-based software engineering is that services are independent. • Services do not have a ‘requires’ interface. • Services rely on message-based communication with messages (usually) expressed in XML.

  14. What is a Service Oriented Architecture (SOA)? • A method of design, deployment, and management of both applications and the software infrastructure where: • All software is organized into business services that are network accessible and executable. • Service interfaces are based on public standards for interoperability.

  15. SOA and Web Services • Service-oriented architecture is an architectural style • Derived from the client-server architectural style. • Clients (service consumers or requesters) and servers (service providers) connected by a service “bus”. • Services defined using formal interfaces (contracts). • Service bus supports point-to-point and messaging styles of communication. • Support for system qualities, ie. security and transaction management. • Web services • Services provided in a SOA deployed over the web.

  16. Key Characteristics of SOA • Protocols used are open industry standards. • Fosters inherent reusability • Fosters interoperability • Emphasizes extensibility • Quality of service, security and performance are specified. • Services (and data) are cataloged and dynamically discoverable. • Fundamentally autonomous • Promotes architectural composability • Promotes loose coupling • Supports incremental implementation

  17. Key Characteristics of SOA • Services are platform independent, self describing interfaces(XML) • Messages are formallydefined • Services can be discovered • Services have qualityof service characteristics defined in policies • Services can be provided on anyplatform • Can be governed

  18. Potential Benefits of SOA • Efficient and effective usage of ‘Business Services’ • Improved integration, intrinsic interoperability • Loosely-coupled with reusable assets and services • Drives business processes closer to end users • Leverage and integrate existing applications • Organizational flexibility and agility

  19. Potential Benefits of SOA • Services can be provided locally or outsourced to external providers. • Services are language-independent. • Investment in legacy systems can be preserved (by migration). • Inter-organizational computing is facilitated through simplified information exchange. • Provide standard connections between systems • Abstract complexity for developers

  20. Potential Benefits of SOA

  21. Types of SOA Services • Business Services / Application Services For example, a retail enterprise might have an “InventoryService,” “CustomerManagementService,” and  “ShippingService” in its repository of business services. Business Services can be further divided into EntityServices, CapabilityServices, ActivityServices, and ProcessServices. • Infrastructure Services Part of a centrally managed infrastructure component ie. the EnterpriseServiceBus (ESB). Examples of Infrastructure Services include SaaSIntegrationServices, AuthenticationServices, EventLoggingServices, and ExceptionHandlingServices. Infrastructure Services are further divided into CommunicationServicesand UtilityServices.

  22. SOA in terms of abstract layers Enterprise Layer (the end-user’s point of access to the composite enterprise application) Process Layer (realizes and automates a business process) Service Layer (carry out business functions) Component Layer (enterprise components are responsible for realizing the functionality of services) Object Layer (legacy systems, including custom-built applications and databases that contain business functionalities)

  23. Types of Services

  24. Examples of Services • Creating a purchase order inside a mainframe application • Requesting and reserving a room in a hotel • Applying for a loan by filling out a loan request form • Search books/music based on keywords

  25. Evolution of SOA

  26. Problems before SOA? Interoperation issues • Heterogeneous network protocols • Heterogeneous hardware platforms • Heterogeneous operating systems • Heterogeneous application formats ETC NOW THERE IS: • Increase in organisational competition • Enhancement of business capabilities THEREFORE: • There must be consensus on Interoperability

  27. Shift to SOA

  28. Application Centric Business scope Narrow Consumers Limited Business Processes Finance bound to EAI vendor Integration Architecture Supply Redundancy Distribution Manufacturing Overlapped resourcesOverlapped providers EAI ‘leverage’ application silos with the drawback of data and function redundancy. Business functionality is duplicated in each application that requires it.

  29. Service Centric

  30. Traditional Architecture vs Service Oriented Architecture

  31. Traditional Architecture vs Service Oriented Architecture

  32. Before SOA – After SOA

  33. SOA Architecture

  34. How Does SOA Work?

  35. Elements of a SOA

  36. SOA Platform

  37. Enterprise Service Bus (ESB) • The infrastructure is the technical part of SOA that enables high interoperability. The principal infrastructure of a SOA landscape is called an Enterprise Service Bus (ESB). This term is taken from Enterprise Application Integration, where it was called the EAI Bus or just Enterprise Bus. • The key feature of the ESB is that it enables you to call services between heterogeneous systems. Its responsibilities include data transformation, (intelligent) routing, dealing with security and reliability, service management, monitoring, and logging.

  38. Enterprise Service Bus (ESB) • Enterprise Service BUS (ESB): It is defined as a set of software components that manage the message routing and transmission from one software component to another.

  39. Enterprise Service Bus (ESB) • The Enterprise Service Bus concept is not a product, but an architectural best practice for implementing a service-oriented architecture. • It establishes an enterprise-class messaging bus that combines messaging infrastructure with message transformation and content-based routing in a layer of integration logic between service consumers and providers.

  40. Enterprise Service Bus (ESB) • The main aim of the Enterprise Service Bus is to provide virtualization of the enterprise resources, allowing the business logic of the enterprise to be developed and managed independently of the infrastructure, network, and provision of those business services. • Resources in the ESB are modelled as services that offer one or more business operations.

  41. Enterprise Service Bus (ESB) Implementing an Enterprise Service Bus requires an integrated set of middleware services that support the following architecture styles: • Services oriented architectures, where distributed applications are composed of granular re-usable services with well-defined, published and standards-compliant interfaces • Message-driven architectures, where applications send messages through the ESB to receiving applications • Event-driven architectures, where applications generate and consume messages independently of one another

  42. Key Components of Service Oriented Architecture

  43. Associated Terminology

  44. Associated Terminology BPO Business Process Outsourcing BPM Business Process Management ESP Enterprise Service Provider GDM Global Delivery Model SOA Service Oriented Architecture SODA Service Oriented Development of Applications SOBA Service Oriented Business Applications SOE Service Oriented Enterprise WS Web Services

  45. Key Standards and Terminology of SOA

  46. Challenges of SOA Technical Challenges • Security challenges - loosely coupled environment • Performance - XML brings robustness not speed • Optimization • Organizing the services – registry and repository • Finding the right services and right interfaces • Transaction management is complex in interactions between logically separate system

  47. Where SOA has made a difference eBay • Abstracting enterprise information • Helped to mange more than 2 perabytes of data IBM • 77 shareable and reusable services in production • Reduced application inventories Hewlett Packard • Reuse across services • Cutting operational costs Amazon.com • Handle 60 million customers and one million partners • Handle growing Transactional load Citi Group • Governance • Enable “separation of powers” among corporate, divisions, departments DreamWorks • Simplify and consolidate key business operations • Use SOA to make movies a easier process Volvo • Better customer service by linking all dealership in Belgium

  48. Summary • Adopting SOA is essential to deliver the required business agility and IT flexibility. • SOA enables dynamic collaboration among loosely coupled, reusable software components through standard open protocols. • SOA not only has many potential benefits to business and IT model but also holds several challenges that need to be solved in future improvement. • SOA made differences to many entrepreneurs including IT, Sales, Finance and Manufacture. • SOA needs a bunch of standards and technologies for support which are widely deployed and acceptable

More Related