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.

Explaining the SOA/REST impedance mismatch

1,401 views

Published on

Published in: Career, Technology, Business
  • Be the first to comment

  • Be the first to like this

Explaining the SOA/REST impedance mismatch

  1. 1. William Martínez Pomares<br />Explaining the SOA/REST Impedance Mismatch<br />
  2. 2. Agenda<br />2011 William Martínez Pomares Avantica Technologies UCR<br />2<br />
  3. 3. Concepts. Names.<br />2011 William Martínez Pomares Avantica Technologies UCR<br />3<br />
  4. 4. Needs anD Architectural Styles<br />2011 William Martínez Pomares Avantica Technologies UCR<br />4<br />
  5. 5. Application types<br />2011 William Martínez Pomares Avantica Technologies UCR<br />5<br />
  6. 6. Distributed application<br /><ul><li>Application as a Whole
  7. 7. Tight connections
  8. 8. High speed communication
  9. 9. Strong coupling
  10. 10. Reuse of Parts Optional</li></ul>2011 William Martínez Pomares Avantica Technologies UCR<br />6<br />
  11. 11. Networked application<br />Application as a Composition of Nodes<br />Weak coupling<br />High cost communication<br />User aware of composition<br />Reuse of Parts is common<br />2011 William Martínez Pomares Avantica Technologies UCR<br />7<br />
  12. 12. Integrated Application<br />Application as an Integration of Whole Applications<br />Standard Interfaces<br />Low frequency of interaction<br />Higher level processes<br />Reuse of Parts is rule<br />Large distribution<br />2011 William Martínez Pomares Avantica Technologies UCR<br />8<br />
  13. 13. SOA solves…<br />2011 William Martínez Pomares Avantica Technologies UCR<br />9<br />*Nicolai M. Josuttis, SOA in Practice, OREILLY<br />
  14. 14. Rest solves<br />2011 William Martínez Pomares Avantica Technologies UCR<br />10<br />*Roy Thomas Fielding, Architectural Styles and the Design of Network-based Software Architectures, 4<br />
  15. 15. SOA SOLUTION<br />2011 William Martínez Pomares Avantica Technologies UCR<br />11<br />Service<br />Flow<br />Client<br />Service<br />Client<br />Service<br />Repository<br />
  16. 16. REST SOLUTION<br />2011 William Martínez Pomares Avantica Technologies UCR<br />12<br />Server<br />Client<br />Server<br />Client<br />Server<br />
  17. 17. Comparing… Mismatch!<br />2011 William Martínez Pomares Avantica Technologies UCR<br />13<br />
  18. 18. REST – SOA Match up <br />2011 William Martínez Pomares Avantica Technologies UCR<br />14<br />
  19. 19. SOA and REST Web Services <br />2011 William Martínez Pomares Avantica Technologies UCR<br />15<br />
  20. 20. REST and Service as A Resource<br />2011 William Martínez Pomares Avantica Technologies UCR<br />16<br />
  21. 21. Conclusion<br />2011 William Martínez Pomares Avantica Technologies UCR<br />17<br />
  22. 22. 2011 William Martínez Pomares Avantica Technologies UCR<br />18<br />Questions?<br />
  23. 23. 2011 William Martínez Pomares Avantica Technologies UCR<br />19<br />Contacts<br />wmartinez@acoscomp<br />iasahome.org Costa Rica<br />Twitter @wmartinez<br />http://wmp-archi.blogspot.com/<br />

×