Making sense of the terminology soup Code/Detailed Design Design Design Patterns Architecture Architectural Patterns Architectural Styles
SOA vs. REST Pipes and Filters Client Server Uniform Interface Virtual Machine Distributed Agents Distributed Agents Layered System Layered System Replicated Repository Code On Demand Code On Demand Stateless Comm. Stateless Comm. Cacheable RESTSOA
REST = "Representation State Transfer" Dispatcher WebApp Cache (Resource) Cache (Resource) Put (New State in XML) OK Get (Latest State) Representation(JSON)
Layers should have some constraints on communications Layer?
Layer Layers should have some constraints on communications Component Layer Componet
Client/Server Client Server Capabilities (services) Requests initiator Request Reply
Replicated Repository is about having more than one copy providing the same service looks like one copy better performance and latency looks like one copy better performance and latency copy
321root /Sessions/Abcde/Efgh/Resources/Dispatchers/Xyz/ Example – Resource Manager
http://devrig:52141/RM/Sessions/abc/ ATOMPUB – Session details URI (ID) State (start/end/status etc.) Resources – Knows status – URI for the Resource representation on the RM – URI for the Resource itself
Your consent to our cookies if you continue to use this website.