1.Service Oriented Architecture(SOA)@saeed_shargi

2. Architecture 3. Architecture Definition in IEEE1471 Architecture :The fundamental organization of a systemembodied in its components, their relationshipsto each other, and to the environment, and theprinciples guiding its design and evolution Architect :The person, team, or organization responsible fordesigning systems architecture 4. Software Architecture What is Software Architecture? The software architecture of a program or computing system is a depiction of the system that aids in the understanding of how the system behave Serves as blueprint for both the system and the project developing The primary carrier of system qualities An artifact for early analysis Set of structures needed to reason about the system Documentation of a system 5. SOA 6. SOA An architecture style that model systems informationinto services Old division between business and IT Basic understanding of SOA development as aapplication that describe web services Logical evolution of the softwares modeling Not a new concept 7. SOA Definition from variousviewpointsSOA is a journey that promises to : reduce the lifetime cost of theapplication portfolio Maximize RIO in both applicationand technology resource Reduce lead times in deliveringsolutions to business 8. SOA Definition from variousviewpointsSOA is a set of services that can be: Exposed to their customers ,partnersand other part of organization Business capabilities , function , andbusiness logic can be combined Application serve the business 9. SOA Definition from variousviewpointsSOA is a way of unlocking value 10. SOA Definition from variousviewpoints SOA is a means to create dynamic ,highly configurable and collaborativeapplication built for change SOA reduce IT complexity andrigidity SOA becomes the solution to stopthe gradual entropy SOA reduces lead times and costs 11. SOA Definition from variousviewpointsSOA is the architectural solution forintegrating diverse systems byproviding an architectural style thatpromotes loose coupling and reuse 12. SOA Definition from variousviewpoints SOA is a programming model or paradigmwhere web services and contracts becomesa dominate design for interoperability Use WSDL or equivalent specificationfor describing the service 13. SOA DefinitionDelivering on the promises of SOA : Improved business agility Maximized ROI Reduce IT complexity and rigidity Reduce costs Reduce lead times Reduce risk New opportunities to deliver value Increased participation in value networks Incremental implementation 14. Is SOA an Architectural Style? 15. What Are The Fundamental Constructs Of SOA? 16. What Are The Fundamental Constructs Of SOA? The most basic construct or building block of SOA is aservice Service consumer, service provider, servicedescription, service broker, and a registry are all part ofthe DNA of SOA A service in SOA is the logical, self-contained businessfunction 17. What Are The FundamentalConstructs Of SOA? Services in SOA have the following attributes: Stateless Discoverable Self-describing Compostable Loose coupling Governed by policy Independent location, language, and protocol 18. What Are The Fundamental Constructs Of SOA? Services in a service-oriented architecture typicallyhave the following characteristics: Coarse-grained Asynchronous 19. What Are The Fundamental Constructs Of SOA? 20. What Are The Fundamental Constructs Of SOA? 21. SOA Terms Service-Orientation Services Service-Models Service Composition Service Inventory Service-Oriented Analysis Service Candidate Service-Oriented Design Service Contract Service-Related Granularity 22. Service-Orientation design paradigm intended for the creation of solution logicunits As a design paradigm for distributed computing, service-orientation can be compared to object-orientation 23. Service-Orientation 24. Services A unit of solution logic to which service-orientationhas been applied to a meaningful extent. As a physically independent software program withspecific design characteristics Each service is assigned its own distinct functionalcontext and is comprised of a set of capabilities relatedto this context Considered a container of capabilities associated witha common purpose 25. Services Service capabilities declare in service contract 26. Services Three common service implementation is : Services as Components Services as Web Services Services as REST Services 27. Services as Component A software program designed to be part of adistributed system It provides a technical interface comparable to atraditional API have typically relied on platform-specific developmentand runtime technologies 28. Services as Web Services Is a body of solution logic that provides a physicallydecoupled technical contract consisting of a WSDLdefinition and one or more XML Schema definitionsand also possible WS-Policy expressions Web service contract exposes public capabilities asoperations Service-orientation can be applied to the design ofWeb services 29. Services as Web Services 30. Services as REST Services Are designed in compliance with the RESTarchitectural style Focuses on the resource as the key element ofabstraction Can be further shaped by the application of service-orientation principles 31. Services Models Is a classification used to indicate that a servicebelongs to one of several predefined types Three service models are common to most enterpriseenvironments and therefore common to most SOAprojects: Task Service Entity Service Utility Service Play an important role during service-orientedanalysis and service oriented design phases 32. Services Composition Is an aggregate of services collectively composed toautomate a particular task or business process To qualify as a composition, at least two participationservices plus one composition initiator need to bepresent Can be classified into primitive and complex variations 33. Services Composition 34. Services Inventory Is an independently standardized and governedcollection of complementary services within aboundary that represents an enterprise or ameaningful segment of an enterprise When an organization has multiple serviceinventories, this term is further qualified as domainservice inventory 35. Services-Oriented Analysis Represents one of the early stages in an SOA initiativeand the first phase in the service delivery cycle The service-oriented analysis process is commonlycarried out iteratively, once for each business process A key success factor of the service-oriented analysisprocess is the hands-on collaboration of both businessanalysts and technology architects 36. Services-Oriented Analysis 37. Services Candidate Is used to help distinguish a conceptualized service from an actual implemented service 38. Services-Oriented Design Represents a service delivery lifecycle stage dedicatedto producing service contracts in support of the well-established contract-first approach to softwaredevelopment The typical starting point for the service-orienteddesign process is a service candidate There is a different service-oriented design process foreach of the three common service models 39. Services Contract Is comprised of one or more published documents thatexpress meta information about a service The fundamental part of a service contract consists ofthe documents that express its technical interface When services are implemented as Web services, themost common service description documents are theWSDL definition, XML schema definition, and WS-Policy definition 40. Services Contract 41. Services Contract 42. Services Contract 43. Services-Related Granularity there are different granularity levels as follows: Service Granularity Capability Granularity Constraint Granularity Data Granularity 44. Services-Related Granularity 45. What Is The Difference Between aWeb Service and an SOA Service? 46. Benefits Of SOA New products or processes simply execute Flexible systems are not obstacle to changing and rapid evolution of processes 47. Benefits Of SOA Solving complex integration problem of large systems 48. Benefits Of SOA Divided of project into smaller components that canbe done independent is simply Control of progress in each subproject is calculated 49. Benefits Of SOA Integration and connecting to other systems is dominant approach 50. Benefits Of SOA Systems easily meet the requirements of users The problem of data transfer between systems issolved with integration Complexity of systems hidden from users 51. Benefits Of SOA Enterprise architects believe that the SOA can help thebusiness to response faster and more cost-effective tomarket conditions changing This style of architecture use reusability in macro levelinstead micro level 52. Orchestration and Choreography Without process engine Sequence of transactionmessages register andcontrolled by playersHave a process engineCall set of services to completeprocessMaybe call external servicesSample of this system isBPMS 53. Principles of SOA Loose coupling Service contract to communications agreement Encapsulation of internal implementation Reusability Composability Statelessness Services Discoverability Services Autonomy Services 54. SOA ToolsCompany Tools Name OracleOracle SOA SuiteMicrosoft BizTalk Server - WCFIBM WebSphere