Service-Oriented Architecture (SOA)
5 likes11,717 views
The document presents a webinar on Service-Oriented Architecture (SOA) by Dassana Wijesekara from WSO2, outlining SOA's principles, value propositions, and relevant concepts like loose coupling and service discoverability. It emphasizes the advantages of SOA, such as business agility, reduced integration costs, and increased asset reuse, while also noting scenarios where SOA may not be ideal. Additionally, it discusses the importance of standards in SOA projects to ensure interoperability and quality of service.
Service-Oriented Architecture (SOA)
- 1. WSO2 Webinar Series SOA : Cure for Corporate Arthritis Dassana Wijesekara 3rd Sep. 2015
- 2. About Me Dassana Wijesekara • Solutions Architect – WSO2 • 13+ experience in software development and architecture • Architect, Evangelist, Consultant and Trainer • Contact : dassana@wso2.com
- 3. Agenda • What is SOA ? • SOA Value Proposition • SOA Concepts • ESB
- 4. Brief History of Architectures
- 5. What is SOA ? • A set of principals and practices for modeling enterprise business functions as services or micro services which has following attributes. • Standardized • Loosely coupled • Reusable • Composable • Autonomic • Stateless • Abstract • Discoverable
- 6. SOA Value Proposition Change is inevitable, the only guarantee of the continuity of a business is its ability to anticipate and adapt to changes : Business Agility. • Reducing Integration Expense § Reduce both development and maintenance cost by isolating components and systems through well-defined interfaces and proper architecture layering. • Increasing Asset Reuse § Self contained services will be reused across the platform • Reducing Business Risk § Established services are being used • Faster Time to Market § Promote flexibility, which provide more space to innovate
- 7. 7 Is SOA Always a Better Solution ? There are special situations where SOA becomes a liability. • Homogeneous IT Environment • True Real-time Systems • Static System with No Evolution • Tight Coupling is Required
- 8. 8 SOA Concepts • The Service ² A service is a business function that is well defined, self contained and does not depend on the context or state of other services. • Web Services : REST, SOAP • Data Services : JDBC • JMS Services • Legacy systems via Adaptors • The Message Exchange • Implementation agnostic message : XML
- 9. 9 SOA Concepts • The Service Contract § Service and usage is described.
- 10. 1 SOA Concepts • Loose Coupling
- 11. 1 SOA Concepts • Functional Autonomy
- 12. 1 SOA Concepts • Service Abstraction
- 15. 1 SOA Concepts • The Self-describing Interface ² A service is self described using service signature : WSDL / WADL • The Service Orchestration and Composition ² BPEL/BPMN process orchestration ² Composite APIs
- 16. 1 SOA Postulates
- 17. 1 XML in SOA • XML is the foundation for virtually all web services standards, such as XML schema, SOAP, Web Services Description Language (WSDL), and Universal Description, Discovery, and Integration (UDDI). These standards leverage the core concept of XML-based representations, a worldwide supported format that carries out information interchange between service providers and requesters in an SOA.
- 18. 1 Role of Standards in SOA • SOA projects are highly reliant upon standards, and leverage them because of these critical benefits: u Standards ensure interoperability across system and partners. u Using standards speeds up development and delivery through processes and tools. u Standards enable better management and visibility of IT assets. u Standards ensure quality of service (QoS). u Standards help with flexibility by reducing dependencies on a specific implementation.
- 20. 2 DNA of SOA
- 22. 2 General ESB Component Architecture
- 23. 2 SOA Tools : ESB
- 24. 2 WSO2 ESB Component Architecture
- 25. 2 SOA Life Cycle
- 26. Contact us !