SOA Service Oriented Architecture l Evolution of Architecture

  • Slides: 20
Download presentation
SOA (Service Oriented Architecture) l Evolution of Architecture. l What is SOA? l SOA

SOA (Service Oriented Architecture) l Evolution of Architecture. l What is SOA? l SOA Concepts l Evolution of SOA l Why SOA? l SOA – Real World Application l Benefits of SOA

Evolution of Architecture

Evolution of Architecture

Evolution of Architecture (Contd. . ) l Monolithic: Processing, data and the user interface

Evolution of Architecture (Contd. . ) l Monolithic: Processing, data and the user interface all reside on the same system l Client/Server: Architecture which separates a client from a server, and business is almost always implemented over a computer network l 3 -Tier/N-Tier: Architecture in which the user interface, business logic, computer data storage and data access are developed and maintained as independent platforms l Components and Objects (EAI): Architecture which is built as components and modular logical units with communication done through an integration mechanism l Services: Architecture that leverages open standards to represent software assets as services with a focus on application assembly

What is SOA? Service Oriented Architecture ¡ Flexible method of structuring and managing component-based

What is SOA? Service Oriented Architecture ¡ Flexible method of structuring and managing component-based systems ¡ Architectural approach to define integration architectures based on the concept of a service. Applications collaborate by invoking each others services and services can be composed into larger sequences to implement business processes. l Information technology architecture that enables distributed computing environment with many different types of computing platforms and applications l Supports a business driven approach to architecture development in line with current business needs rather than a technology based approach l Services in an SOA are: l Loosely-coupled l Used to compose multiple applications l Discovered and invoked dynamically l May feature standard interfaces or a common format l

Key terms in SOA l l l Service ¡ Reusable piece of functionality Service

Key terms in SOA l l l Service ¡ Reusable piece of functionality Service Consumer ¡ Client/Application which invokes the functionality Service Producer ¡ Client/Application which provides the functionality Message ¡ Information served/invoked Dynamic Discovery ¡ Registry Web Service

Key terms in SOA l Service l l encapsulate reusable business functions are defined

Key terms in SOA l Service l l encapsulate reusable business functions are defined by explicit, implementation-independent interfaces are invoked through communication protocols that stress location transparency and interoperability. can be dynamically located and invoked Directory Service available

Key terms in SOA l Message Mode of communication between service consumer and service

Key terms in SOA l Message Mode of communication between service consumer and service provider l Typically constructed using XML documents that conforms to defined XML schema (WSDL) l Dynamic Discovery l Directory services to list the services where service consumers can query for service details and contact service provider l Advantages of dynamic discovery: l Scalability – Services can be added incrementally l Consumer and provider decoupling l Allows implementation updates l Can chose provider at run time rather than hard coding l

SOA and Web Services are a specialized implementation of Services. l Web services play

SOA and Web Services are a specialized implementation of Services. l Web services play major enabling role in SOA l Web services are built on top of well-known and platformindependent protocols. l l l HTTP XML UDDI WSDL SOAP Interoperability Platform independent interface contract Dynamic Discovery and Invocation Standard Messaging

SOA Concepts in the Real World - Cable l l l l A cable

SOA Concepts in the Real World - Cable l l l l A cable TV company (a service provider) has the capacity (the underlying capability) to collect and distribute content (services) Wiring from the cable TV company makes a distribution grid (the service bus) to supply the content (the services) The distributed TV signal (the service) Is available for the typical usage in a residential consumer’s house (service consumer)

SOA Concepts • A consumer accesses a program by connecting a device to an

SOA Concepts • A consumer accesses a program by connecting a device to an outlet (service interface) • Service delivery (service invocation) occurs when a device is connected to the interface.

Cable TV Model Service Provider Service Bus Consumer Interface

Cable TV Model Service Provider Service Bus Consumer Interface

SOA Concepts ü The consumer can connect different devices (TV, VCR, DVR, etc. )

SOA Concepts ü The consumer can connect different devices (TV, VCR, DVR, etc. ) to the interface; ü The provider is not concerned with how the service is used. ü The provider can send different types services (satellite signal, broadcast signal, DVD, etc); ü The consumer is not concerned with the service’s source. ü Therefore … the end points are said to be Loosely Coupled. ü The service provider creates a list of available services (shows available). ü Also provided any information needed to use the service is (time, channel, duration, etc. ) ü Service consumers can browse the list to determine what service they want to consume. ü This is the Registry ü The Service Provider and the Service Consumer have a agreement or contract (Service Level Agreement) which sets the monthly fee for a specified number of available channels.

Evolution of SOA l Service-Based Integration l l Heterogeneous systems sharing data and functionality

Evolution of SOA l Service-Based Integration l l Heterogeneous systems sharing data and functionality using a standard message format Legacy Systems “wrapped” by a service Service Consumers SOAP/HTTP Service Providers SOAP/MQ Service Providers Legacy Systems

Why SOA? DISADVANTAGES of TRADITIONAL APPROACHES • Tight Coupling • Distributed and soiled applications

Why SOA? DISADVANTAGES of TRADITIONAL APPROACHES • Tight Coupling • Distributed and soiled applications • Integration Nightmare • Distributed platforms • Varying Protocols • Varying Devices • Application/functionality Redundancy • Application centric and not business centric Why SOA? • Loosely Coupled • Every Application able to communicate seamlessly • No P 2 P (Point-to-Point) integration (API based). • Based on open standards with wide support from industry • “Retain and reuse” rather than “rip and replace” • Paradigm Shift • With SOA, businesses can use existing assets to accommodate changed business requirements and be flexible to adapt

SOA – Real World application l Client Profile: Leading Credit Card Company l Business

SOA – Real World application l Client Profile: Leading Credit Card Company l Business Issue: ¡ Member banks had to process cardholder disputes via a paper system. ¡ Automating the process was difficult because the banks had incompatible back-end and legacy systems. l How SOA Helped: ¡ SOA allows direct communication between member banks and the back -end systems, simplifying transaction research, dispute case search and retrieval, and requests for copies of original paper receipts. ¡ Savings are said to total $52 million a year in direct operating costs and $300 million in ancillary savings. ¡ What's more, new projects have been able to reuse services from this project, helping to reduce development time and risk

SOA – Layered Architecture • Object Oriented technology can be used to implement Components.

SOA – Layered Architecture • Object Oriented technology can be used to implement Components. • Services can be used to access components

Main SOA Standards Policy • Set of conditions or rules under which service provider

Main SOA Standards Policy • Set of conditions or rules under which service provider makes service available to consumers Security • Identification, authorization and access control Transaction • Conditions applicable for a group of services to deliver consistent result Management • Administration of services

SOA Standards l l l Transport l Mechanism used to move service requests Service

SOA Standards l l l Transport l Mechanism used to move service requests Service Communication Protocol l Agreed mechanism for communication Service Description l Agreed schema for service description, invocation mechanism and input/output data Service l Reusable Business process Business Process l Collection of services, invoked in a particular sequence with a particular set of rules, to meet a business requirement. Business process could be considered a service in its own right. Service Registry l Repository of service and data descriptions

Benefits of SOA l l l l Leverage Existing Assets and ability to integrate

Benefits of SOA l l l l Leverage Existing Assets and ability to integrate with future assets Easier to integrate and manage complexity Measurable business value: increased business agility and flexibility, and faster time-to-market and time-to-value Reduce IT development cost and increase reuse Reduced complex integration and maintenance costs (integration is typically one of the larger headaches for IT departments) Integrate disparate IT systems so they can communicate with each other, reducing the need for multiple systems that do different things in isolation Extend the life of their current IT assets, while still adding needed functionality Create an expandable IT architecture that meets current business needs, while ensuring long-term expandability and flexibility to meet future business needs as they arise

SOA : Business Centric SOA is not a One-stop Solution

SOA : Business Centric SOA is not a One-stop Solution