1 / 23

Service Oriented Architecture

Service Oriented Architecture. Concepts, Principles, Facts, Myths, Hype, Reality… Part 1 Adomas Svirskas Vilnius University September 2005. Agenda. SOA as a moving target SOA from corporate point of view BEA SOA Domain Model and Strategy SOA from technical point of view. SOA is….

lowri
Télécharger la présentation

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. Service Oriented Architecture Concepts, Principles, Facts, Myths, Hype, Reality… Part 1 Adomas Svirskas Vilnius University September 2005

  2. Agenda • SOA as a moving target • SOA from corporate point of view • BEA SOA Domain Model and Strategy • SOA from technical point of view

  3. SOA is… • The latest fashion in IT architecture • “SOA represents the biggest change in enterprise IT since the advent of the Internet.” Infoworld SOA Executive Forum • "Service-Oriented Architecture is an IT strategy that organizes the discrete functions contained in enterprise applications into interoperable, standards-based services that can be combined and reused quickly to meet business needs.“ Bill Roth, BEA Systems • “SOA is a specific architectural style that is concerned with loose coupling and dynamic binding between services” [5]

  4. SOA is... …a new approach to developing applications [4]

  5. SOA Benefits (Promised) [6] • Allows IT to deliver services faster and align closer with business • Leverage existing assets • Improved productivity, agility and speed for Business & IT • Reduced development times and costs through re-use • Decreased integration costs and risks • Lower maintenance costs and higher data integrity • Allows business to respond quicker and deliver enhanced user experience • Enables new ways to relate to employees, partners and customers

  6. SOA Expectations [4] More flexible architecture Integration to existing applications Tech points of pain Data integration Business process implementation Enterprise portal initiatives Custom application development Composite applications More effective integration with business partners Business pointsof pain Customer service initiatives Employee self service Streamlined supply chain More effective use of external service providers Global sourcing Q: What are the critical business or IT problems your company hopes to address using SOA? Base: 261 respondents (those personally involved with SOA in their company) Source – BEA sponsored research with InfoWorld, [4]

  7. SOA Roots • SOA has emerged as a consequence of business and IT drivers of the past decade • Business factors • Outsourcing of non-core operations • Business process re-engineering • IT factors • Importance of universal middleware • The Internet

  8. SOA from Business Perspective • Business processes (BP) of any company prescribe how products are manufactured and offered to the clients • Speed of change in BP domain corresponds to the speed of change in product offers, i.e. affects chances of survival in highly dynamic markets • Flexibility is reflection of company’s ability to adapt its BPs quickly

  9. The Services • The business partners offer their resources in the form of services • A service is: • Some sort of publicised package of functionality • Composable • Discoverable based on describing metadata • Usable by a mutually agreed contract

  10. The Services Taxonomy • Component services: Simple atomic services potentially acting on single enterprise resource (e.g., database, code, etc) • Data services: Service providing data querying, combination and transformation for multiple data sources. • Business services: Atomic services composed of combinations of component services and rules. • Workflow services: Long lived business processes coordinating other services with external interactions

  11. Virtual Enterprises (Organisations) • The need for speed and flexibility forces to outsource parts of the business, find the best partners on demand and manage a network of collaborations • A company becomes a virtual organisation in its essence • Mergers/acquisitions also create VOs • Complex VOs are tricky to manage and operate without suitable framework

  12. Virtual Enterprises (Organisations) • VOs can exist inside a large company as well as cross company boundaries • The partners inside a VO have no direct authority to control each other, as a rule • The partners offer their resources (forms vary greatly) to other partners • The collaborations between the partners include a number of business transactions • The partners are loosely coupled

  13. VO Lifecycle

  14. Data Data WSRP WSRP Identity/ Policy Identity/ Policy Data Layer Mainframes Process Data Databases Data Legacy App Data Service Infrastructure Management Process Service Registry MonitoringServices BusinessProcessServices UserInteractionServices CompositionTools MessagingServices Meta-data Repository To Function Well SOA Needs… Clients Logic Presentation Process Portal Browser Web Services Web Services ApplicationClient Web Services Web Services Mobile WebApp DataServices SecurityServices … an infrastructure [4]

  15. User Interaction Portal Multi-channel Collaboration Interaction Management Process Orchestration Business Process Management Update Business Rules Enterprise Connectivity Business Activity Management Security Services Preview Federated Identity Management Integrated Composition Environment Distributed Application Security Management Data and Information Services Compose Business Intelligence Composite Data Management Unified Data Modeling Unified Meta Data Repository Monitor Message Services Service Manager Message Management Service Registry SOA Infrastructure Process Orchestration User Interaction Security Services Integrated Composition Environment Data and Information Integration Message Services more details [4]

  16. SOA Solution Components [3] • Producers: A producer is an entity that offers a specific service or functionality • Consumers: A consumer is an entity that makes use of the service offered by the producer • Services: A service is an entity that performs a specific task when invoked • Contract: A contract or an interface specifies a format in which the data needs to be provided to the service to perform the specific task • Repository: A repository is a glorified version of a registry and includes the metadata relevant for the solution, namely service, service contract, data/object model, and so on

  17. SOA in IT Context From Paul Lipton, Web Services Journal, August 2005

  18. Governance • Governance is the management of development artefacts (or assets), such as Java code, HTML, XML, deployment descriptors, WSDL, etc. • Governance is primarily about tracking and controlling development artifacts through their life cycles; from creation to archiving (it is usually not a good idea to destroy an artefact).

  19. Debunking SOA Myths [3] • Myth #1: SOA is a solution (panacea, silver bullet) to all software problems • Myth #2: SOA is like a product, and can be downloaded for trial • Myth #3: SOA is a complete, off-the-shelf solution • Myth #4: SOA software always needs to be developed using Web services

  20. Debunking SOA Myths [3] • Myth #5: Any software development using Web services is aligned with SOA • Myth #6: Each service is always atomic in nature • Myth #7: SOA is not aligned with any standards • Myth #8: SOA is the same as EAI • Myth #9: SOA is a very expensive solution

  21. Debunking SOA Myths [3] • Myth #10: SOA solution components (services, contracts) are completely reusable • Myth #11: Services in the context of SOA are not explicit • Myth #12: SOA is applicable only to specific industrial domains • Myth #13: SOA can be sold to customers as is

  22. Conclusions • SOA has many shapes and forms • Domain Models, patterns and best practices for SOA start to emerge • The first SOA-based corporate solutions go live • SOA will attract more attention in the next few years

  23. References • [1] Foster, I. et al. Open Grid Services Architecture V1. 2004. • [2] Booth, D., et al. Web Services Architecture. W3C, Working Draft http://www.w3.org/TR/2003/WD-ws-arch-20030808/, 2003. • [3] Anantharangachar, R. Myths About Service-Oriented Architecture, Web Services Journal, August 2005 • [4] Carges, M. Taking SOA from "Pilot to Production" with Service Infrastructure http://www.infoworld.com/event/soa/InfoWorld_SOA_Mark_Carges.ppt • [5] Curbera, F. et al., Web Services Platform Architecture: Soap, WSDL, WS-Policy, WS-Addressing, WS-Bpel, WS-Reliable Messaging and More, Prentice Hall PTR, 2005 • [6] Kamdal, M. SOA – Taking a Structured approach. BEA Architects Summit, http://ftpna2.bea.com/pub/downloads/architectsummitpresentations/SOA_Taking_A_Structured_Approach.pdf • [7] Roth, B. Service-Oriented Architecture Best Practices, http://java.sys-con.com/read/48032.htm

More Related