Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Service Oriented Architecture - SOA A New Paradigm for Developing ...

644 views

Published on

  • Be the first to comment

  • Be the first to like this

Service Oriented Architecture - SOA A New Paradigm for Developing ...

  1. 1. Service Oriented Architecture - SOA A New Paradigm for Developing Enterprise Software Systems
  2. 2. Outline <ul><li>Introduction </li></ul><ul><li>ESB implementation of SOA </li></ul><ul><li>Analysis of ESB implementation </li></ul><ul><li>Conclusion </li></ul><ul><li>References </li></ul><ul><li>Q & A </li></ul>
  3. 3. Introduction <ul><li>Organizations are increasingly collaborating and constitutes an enterprise. </li></ul><ul><li>Many organizations have pre-existing IT resources. </li></ul><ul><li>Not economical to dispose in favor of mutual interaction. </li></ul><ul><li>Must take another approach. </li></ul><ul><li>IBM invents SOA [IBM] . </li></ul>
  4. 4. Introduction <ul><li>At the highest level SOA consists of the following parts: </li></ul><ul><ul><li>A set of service providers. </li></ul></ul><ul><ul><li>A set of service consumers. </li></ul></ul><ul><ul><li>A discovery service. </li></ul></ul><ul><li>Uses XML–based technologies to achieve platform independence. </li></ul>
  5. 5. Introduction
  6. 6. Introduction <ul><li>Service providers makes a registration call to the service broker. </li></ul><ul><li>The service broker stores and maintains information about service ID and location. </li></ul><ul><li>The Service consumers queries service broker. </li></ul><ul><li>Service broker either: </li></ul><ul><ul><li>lets the consumer know about the location of the provider or, </li></ul></ul><ul><ul><li>dynamically discovers the provider location and lets the consumer know. </li></ul></ul><ul><li>The consumer interacts with provider. </li></ul>
  7. 7. Introduction <ul><li>Related functionalities are combined into cohesive software agents. </li></ul><ul><li>For pre–existing software agents a wrapper is required. </li></ul><ul><li>Each cohesive software agent can be used as a service by the consumers. </li></ul><ul><li>Overall enterprise application is a collection of such service providers and consumers. </li></ul>
  8. 8. Introduction <ul><li>[GUEDES] describes an application of SOA in a distributed data mining application. Please see article for more details. </li></ul><ul><li>Because of enterprise–wide exposure software vulnerabilities are more pronounced in SOA. </li></ul><ul><li>The authors in [EPSTEIN] mentions some pitfalls to be aware of when considering security in SOA implementations. </li></ul>
  9. 9. Outline <ul><li>Introduction </li></ul><ul><li>ESB implementation of SOA </li></ul><ul><li>Analysis of ESB implementation </li></ul><ul><li>Conclusion </li></ul><ul><li>References </li></ul><ul><li>Q & A </li></ul>
  10. 10. ESB Implementation of SOA <ul><li>Two approaches to implement SOA: </li></ul><ul><ul><li>Endpoint–based approach. </li></ul></ul><ul><ul><li>Bus–based approach (ESB). </li></ul></ul>
  11. 11. ESB Implementation of SOA <ul><li>Endpoint-based implementation: </li></ul>
  12. 12. ESB Implementation of SOA <ul><li>Bus-based implementation: </li></ul>
  13. 13. ESB Implementation of SOA <ul><li>The bus-based implementation – central component is the service bus called the enterprise service bus. </li></ul><ul><li>Can be described using the Publish Subscribe style [CLEMENTS] . </li></ul>
  14. 14. ESB Implementation of SOA <ul><li>Some ESB features that must be present [GENENDER] : </li></ul><ul><ul><li>Standard–based. </li></ul></ul><ul><ul><li>Orchestration. </li></ul></ul><ul><ul><li>Security. </li></ul></ul><ul><ul><li>Reliable. </li></ul></ul><ul><ul><li>Distributed and loosely–coupled. </li></ul></ul><ul><ul><li>Incremental adoption. </li></ul></ul>
  15. 15. ESB Implementation of SOA <ul><li>Two of the commercial implementations are available from: </li></ul><ul><ul><li>Sonic Software [SONIC] . </li></ul></ul><ul><ul><li>SUN Microsystems [SUN] . </li></ul></ul>
  16. 16. Outline <ul><li>Introduction </li></ul><ul><li>ESB implementation of SOA </li></ul><ul><li>Analysis of ESB implementation </li></ul><ul><li>Conclusion </li></ul><ul><li>References </li></ul><ul><li>Q & A </li></ul>
  17. 17. Analysis of ESB Implementation <ul><li>ESB Implementation is more scalable than the endpoint–based implementation. </li></ul>
  18. 18. Analysis of ESB Implementation <ul><li>In endpoint-based implementation: </li></ul>
  19. 19. Analysis of ESB Implementation <ul><li>N software systems. </li></ul><ul><li>Must interact with N–1 other systems. </li></ul><ul><li>Therefore requires O(N 2 ) connectors per software system. </li></ul><ul><li>To add 1 additional software system we need (N * N) that is, N 2 code points for implementing the connectors. </li></ul><ul><li>Similar order of effort is required for removing a single software system. </li></ul><ul><li>Becomes extremely tedious and error prone when N is large. </li></ul>
  20. 20. Analysis of ESB Implementation <ul><li>In ESB implementation: </li></ul>
  21. 21. Analysis of ESB Implementation <ul><li>N software systems. </li></ul><ul><li>Requires 2N connectors per software system. </li></ul><ul><li>Therefore requires O(N) connectors and a constant for implementing the bus itself. </li></ul><ul><li>To add 1 additional software system we need only 2N, that is, O(N) number of connectors. </li></ul><ul><li>Similar order of effort is required for removing a single software system. </li></ul><ul><li>More scalable than endpoint–based approach because of linear complexity in adding and/or removing software systems. </li></ul>
  22. 22. Outline <ul><li>Introduction </li></ul><ul><li>ESB implementation of SOA </li></ul><ul><li>Analysis of ESB implementation </li></ul><ul><li>Conclusion </li></ul><ul><li>References </li></ul><ul><li>Q & A </li></ul>
  23. 23. Conclusion <ul><li>Adoption of SOA encourages incremental system development for distributed system development. </li></ul><ul><li>Perfectly suitable for developing enterprise applications. </li></ul><ul><li>Allows easy migration of organizations to enterprise wide systems. </li></ul><ul><li>In particular the bus–based approach is better and more scalable. </li></ul>
  24. 24. Outline <ul><li>Introduction </li></ul><ul><li>ESB implementation of SOA </li></ul><ul><li>Analysis of ESB implementation </li></ul><ul><li>Conclusion </li></ul><ul><li>References </li></ul><ul><li>Q & A </li></ul>
  25. 25. References <ul><li>[IBM] IBM Service Oriented Architecture–SOA. http://www.ibm.com/soa . </li></ul><ul><li>[GUEDES] D. Guedes, W. Meira Jr., and R. Ferreira. “Anteater: A Service–Oriented Architecture for High–Performance Data Mining.” IEEE Internet Computing , vol. 10, pp. 36–43. IEEE Computer Society. July–August 2006. </li></ul><ul><li>[EPSTEIN] J. Epstein, S. Matsumoto, and G. McGraw. “Software Security and SOA: Danger, Will Robinson!” IEEE Security and Privacy Magazine , vol. 4, pp. 80–83. IEEE Computer Society, January–February 2006. </li></ul><ul><li>[CLEMENTS] P. Clements, F. Bachmann, L. Bass, D. Garlan, J. Ivers, R. Little, R. Nord, and J. Stafford. Documenting Software Architecture: Views and Beyond . Addison-Wesley Professional, Springfield, Massachusetts, 1st edition, 2002. </li></ul><ul><li>[GENENDER] J. Genender. “The Buzz About Enterprise Service Bus (ESB).” http://www.virtuas.com/files/genender%20j-f.pdf . </li></ul><ul><li>[SONIC] Sonic ESB. http:// www.sonicsoftware.com/products/sonic_esb/index.ssp . </li></ul><ul><li>[SUN] SUN Microsystems OpenESB. http:// java.sun.com/integration/openesb/index.jsp . </li></ul>
  26. 26. Outline <ul><li>Introduction </li></ul><ul><li>ESB implementation of SOA </li></ul><ul><li>Analysis of ESB implementation </li></ul><ul><li>Conclusion </li></ul><ul><li>References </li></ul><ul><li>Q & A </li></ul>
  27. 27. Q & A

×