The document discusses the differences between service-oriented architecture (SOA) and representational state transfer (REST) architectural styles. It explains that SOA solutions emphasize services, service flows, and service repositories, while REST solutions focus on servers and clients directly communicating. The document notes there is an "impedance mismatch" between SOA and REST, as they have differing needs and architectural styles. It aims to analyze where SOA and REST align and differ to understand how to better combine the two approaches.
10. Reuse of Parts Optional2011 William Martínez Pomares Avantica Technologies UCR 6
11. Networked application Application as a Composition of Nodes Weak coupling High cost communication User aware of composition Reuse of Parts is common 2011 William Martínez Pomares Avantica Technologies UCR 7
12. Integrated Application Application as an Integration of Whole Applications Standard Interfaces Low frequency of interaction Higher level processes Reuse of Parts is rule Large distribution 2011 William Martínez Pomares Avantica Technologies UCR 8
13. SOA solves… 2011 William Martínez Pomares Avantica Technologies UCR 9 *Nicolai M. Josuttis, SOA in Practice, OREILLY
14. Rest solves 2011 William Martínez Pomares Avantica Technologies UCR 10 *Roy Thomas Fielding, Architectural Styles and the Design of Network-based Software Architectures, 4
15. SOA SOLUTION 2011 William Martínez Pomares Avantica Technologies UCR 11 Service Flow Client Service Client Service Repository
16. REST SOLUTION 2011 William Martínez Pomares Avantica Technologies UCR 12 Server Client Server Client Server