1 / 32

SOA In Practice

Explore the transformative potential of Service-Oriented Architecture (SOA) in streamlining software integration for global enterprises. Founded in 1991 and publicly traded since 1997, IONA delivers high-performance integration solutions that address future challenges in IT environments. By adopting SOA principles such as loose coupling, reusability, and discoverability, businesses gain the flexibility to adapt and enhance operational efficiencies. With a worldwide customer base, including leading firms in telecom and financial services, IONA exemplifies how strategic architecture leads to seamless integration and sustained growth.

ansel
Télécharger la présentation

SOA In Practice

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. SOA In Practice Oisin Hurley, IONA

  2. … at a glance Customers include world’s largest firms Solid business with a history of profitable growth • 80% of Global Telecom • 70% of Financial Services in Global 100 • Blue Chip System Integrator Partners • Founded in 1991 • Publicly traded since 1997 • $50+ million cash on hand • No debt NASDAQ:IONA Our Approach: Making Software Work Together™ • Deliver high performance integration software for mission critical applications • Make heterogeneity an asset, not a liability • Deliver on the value proposition of standards Worldwide presence • EMEA HQ in Dublin, Ireland • US HQ in Massachusetts • APAC HQ in Tokyo, Japan

  3. SOA • Architectural Principle • Define how a community engages • Enterprise Strategy • Flexibility from the business standpoint • Technology • No, it’s not Yet Another Integration Technology • It’s got very little to do with that at all

  4. SOA Principles • Formal Contract • Terms of engagement for use • The design is an investment • Requires maintenance • “Loose Coupling” • Soft landing for unforeseen changes • Less dependencies between consumers and service implementations • Contributes to organizational flexibility

  5. SOA Principles • Abstraction of underlying logic • Only the contract is visible • Implementation is black-box • Autonomy • Service should have full control of its resources to realise repeatable scaling • In real life, resources are generally shared • Possibilities in greenfield developments

  6. SOA Principles • Reusable • Service should have repeatable value • Building less new stuff is good • Business-oriented, unlike OO-style interface reuse • Composable • To allow us to chain services together to provide new services • This is different from reusable as it informs the design of operations, message formats • Building new stuff quickly is good

  7. SOA Principles • Stateless • This means a service must do its best to hold onto state information pertaining to an interaction for as small a duration as possible, e.g., do not retain awareness of a message once it is processed • This helps with concurrent access scaling • Discoverable • Helps to prevent the development of redundant services and logic • Implies that community organizes itself around and maintains service metadata

  8. What does SOA help solve? • Future integration challenges • SOA helps reduce the number of moving parts • Future infrastructure flexibility • SOA helps codify the use of applications rather than focussing on the applications • Salve for complexity in IT environments • Decompose the environment • Incrementally address different issues • Reduce the fear

  9. Use Case 1 Pick The Best Technology

  10. Use case 1: BSS integration solution • Integration solution for mobile provider in middle-east • Links ordering to third-party provisioning system, payment system and financial institution.

  11. Use Case 2 Dealing With Interesting Decisions

  12. Use case 2: OSS integration solution • Integrate network events from Cisco Information Centre to backend systems of UK mobile operator. • Cramer, ServiceView, CRM (Vantive, Clarify and Remedy) • Modular architecture. • Flexible deployment with pluggable back-ends for alternate CRM instances.

  13. IDL WSDL WSDL Use case 2: OSS integration solution <<remedy>>:ARServer <<artix>>:Osiris ARAPI <<cic>>:CorbaProbe proprietary <<j2ee>>:Clarify IIOP A Java A RMI/IIOP IIOP <<amdocs>>:Vantive <<cic>>:SocketProbe proprietary A <<db>>:Cramer Name-Value/TCP DBSchema JDBC

  14. Use Case 3 Sudden Value!

  15. WSDL Use case 3: OSS integration solution Engineer arrives at a base station, and needs fault information. He sends an SMS to the man-on-site short code. • Send inventory notifications to on site engineers via SMS, for UK mobile operator SMS <<artix>>:ManOnSite <<servlet engine>>:Tomcat :SCAP A SOAP/HTTP HTTP XML/HTTP

  16. WSDL Use case 3: OSS integration solution SCAP box sends SOAP/HTTP to service endpoint, and acknowledges receipt of SMS. <<artix>>:ManOnSite <<servlet engine>>:Tomcat :SCAP A SOAP/HTTP HTTP XML/HTTP

  17. WSDL Use case 3: OSS integration solution Service delegates call to a back-end system. <<artix>>:ManOnSite <<servlet engine>>:Tomcat :SCAP A SOAP/HTTP HTTP XML/HTTP

  18. WSDL Use case 3: OSS integration solution Service parses HTTP response and sends a sequence of SMS messages to the engineer. <<artix>>:ManOnSite <<servlet engine>>:Tomcat :SCAP A SOAP/HTTP HTTP XML/HTTP

  19. WSDL Use case 3: OSS integration solution Engineer receives SMS notifications and carries out work. <<artix>>:ManOnSite <<servlet engine>>:Tomcat :SCAP A SOAP/HTTP HTTP XML/HTTP

  20. Use Case 5 Wrapping COTS Applications

  21. <<remedy>> <<service>> A SOAP/HTTP WSDL 2. createTroubleTicket() WSDL WSDL <<HPOV>> <<service>> <<service>> <<cramer>> Use case 5: OSS Integration solution COTS applications are wrapped with rich WSDL interfaces providing business service functionality. 1. getInventoryInfo() A A

  22. Use Case 6 Tailoring Services

  23. <<linux>> <<linux>> Use case 6: service provisioning for healthcare professionals • Integration bridge between national health-care system • Providing patient care data to medical professionals on PDA. • Supporting synchronous, asynchronous and reliable asynchronous message exchange patterns. Presentation Layer Hot replica SPINE

  24. Use case 6: Service Provisioning for Healthcare Professionals

  25. Use Case 7 Real World Intervention

  26. <<linux>> <<linux>> <<linux>> <<location>>:replica1 <<location>>:replica1 Use case 7: server farm for insurance rating app • Legacy rating engine, distributed over a farm of processors • C++ DLL exposed as a web service, clustering provided • Session management used to ensure consumer stickiness. • Services accessed via Tomcat presentation layer. <<servlet engine>>:Tomcat <<servlet engine>>:Tomcat

  27. BIG SOA

  28. SOA in The LARGE • Previous cases are real, but small, tactical integrations that use SOA principles • There is also SOA in the LARGE • Vast projects • Cross-cutting in a business • The intent is to introduce long-term efficiencies • Generally means replacing silo efforts as much as possible

  29. Duplicated operations Diverse protocols Slow service development Siloed vs. Service-Oriented Networks PLMN PLMN Service PSTN/ISDN PSTN/ISDN Service Data / IP Networks Data/IP Networks Service CATV CATV Service GW GW GW GW Today Future Applications / Content IT Network Access APIs Backbone Network • Integrated operations • Standard protocol • Rapid service development

  30. Non-SOA IT System Silos

  31. SOA IT System

  32. 32

More Related