1 / 31

Service Oriented Architecture

Session 50. Service Oriented Architecture. Terry Woods. Agenda. The Problem What is Service-Oriented Architecture? Change is Inevitable What is an Enterprise Service Bus? Summary. The Problem. Legacy Business Process. Architectural Choke Point. Monolithic Extremely complex

vesta
Download Presentation

Service Oriented Architecture

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. Session 50 Service Oriented Architecture Terry Woods

  2. Agenda • The Problem • What is Service-Oriented Architecture? • Change is Inevitable • What is an Enterprise Service Bus? • Summary

  3. The Problem

  4. Legacy Business Process

  5. Architectural Choke Point • Monolithic • Extremely complex • Very tightly coupled • Difficult to find clean integration points • Lack of standards makes it difficult to integrate • Rigid architecture makes even small changes complex and costly

  6. SOA Business Process

  7. What is Service-Oriented Architecture?

  8. What is Service-Oriented Architecture? • Service-Oriented Architecture (SOA) is an architectural style. Applications built using an SOA style deliver functionality as services that can be used or reused when building applications or integrating within the enterprise or trading partners.

  9. What is a Service? • A service provides a discrete business function that operates on data. Its job is to ensure that the business functionality is applied consistently, returns predictable results, and operates within the quality of service required.

  10. Characteristics of a Service • Supports open standards • Loose coupling • Stateless • Location agnostic

  11. Change is Inevitable

  12. COBOL C++ Java J2EE Networks TCP/IP Web Service Mid-Tier Servers .NET Messaging HTML Operating Systems CICS Routers Databases Mainframes IT is like an Ecosystem

  13. Technology Management Product duplication Standards Product/Vendor lock-in Support skill sets Version Management Managed Evergreening Limited versions in production Managing the Ecosystem

  14. Legacy Integration

  15. SOA Integration

  16. Integration Stack • Industry Standards • Language Standards • Custom API’s • Native Interfaces

  17. Enterprise Service Bus

  18. What is an Enterprise Service Bus (ESB)? An ESB implements an SOA through middleware that offers virtualization and management of service interactions between communication participants. Thus, this flexible connectivity layer could help connect and integrate an organization's IT infrastructure across many differing systems and locations reliably and securely while reducing the number, size and complexity of application interfaces. ComputerWorld (http://www.computerworld.com/developmenttopics/development/webservices/story/0,10801,108478,00.html)

  19. Key Characteristics of an ESB • Streamlines development • Supports multiple binding strategies • Performs data transformation • Intelligent routing • Real time monitoring • Exception handling • Service security

  20. Mediation Source: Getting Started with WebSphere Enterprise Service Bus V6 http://www.redbooks.ibm.com/redbooks/SG247212/wwhelp/wwhimpl/java/html/wwhelp.htm

  21. Manage Subscriptions to Organization Data

  22. Distribute New Organization Data

  23. Distribute New Organization Data with Human Interaction

  24. Service Enablement of Managed File Transfer

  25. Schema Validation Approaches

  26. Understanding the Technology Stack

  27. ESB Conceptual Architecture

  28. Describing Services to Machines • Web Services Description Language • Open Standard for describing Interfaces to Services (http://www.w3.org/TR/wsdl) • Characteristics • Describes data expected to be sent and received • Describes what the service can do • Describes how to reach the service • WSDL description is an XML document

  29. ESB Summary • Loose Coupling • Location Transparency • Transport Neutral

  30. Summary • The Problem • What is Service-Oriented Architecture? • Change is Inevitable • What is an Enterprise Service Bus? • Summary

  31. Contact Information I appreciate your feedback and comments. I can be reached at: Name: Terry Woods Phone: 202-377-3023 Email: Terry.Woods@ed.gov

More Related