17 applied architectures
16 de Feb de 2011•0 gostou•889 visualizações
Baixar para ler offline
Denunciar
Tecnologia
Majong DevJfuSeguir
Recomendados
Cs 1023 lec 13 web (week 4)stanbridge
Session19 GlobusISSGC Summer School
Eclipse IoT Summit 2016: In The Age of IoT Think Data-CentricToby McClean
QoA4ML – A Framework for Supporting Contracts in Machine Learning ServicesHong-Linh Truong
Sharing Blockchain Performance Knowledge for Edge Service DevelopmentHong-Linh Truong
K8s dds meetup_presentationItay Shakury
Mais conteúdo relacionado
Mais procurados
RDA-DCAM and Application ProfilesMikael Nilsson
Grid protocol architecturePooja Dixit
Globus toolkit in gridDeevena Dayaal
DCMI Keynote: Bridging the Semantic Gaps and InteroperabilityMike Bergman
Linked Data Driven Data Virtualization for Web-scale Integrationrumito
IEEE 2014 DOTNET CLOUD COMPUTING PROJECTS Distributed -concurrent--and-indepe...IEEEMEMTECHSTUDENTPROJECTS
Similar a 17 applied architectures
REST & RESTful APIs: The State of ConfusionGlenn Antoine
Yii Framework in the RAD context + Mashup demo built on YIIGeorge-Leonard Chetreanu
Secc tutorials development and deployment of rest web services in java_v2.0Aravindharamanan S
Actively looking for an opportunity to work as a challenging Dot Net DeveloperKarthik Reddy
Actively looking for an opportunity to work as a challenging Dot Net DeveloperKarthik Reddy
Data Services and the Modern Data Ecosystem (ASEAN)Denodo
Mais de Majong DevJfu
9 - Architetture Software - SOA CloudMajong DevJfu
8 - Architetture Software - Architecture centric processesMajong DevJfu
7 - Architetture Software - Software product lineMajong DevJfu
6 - Architetture Software - Model transformationMajong DevJfu
5 - Architetture Software - Metamodelling and the Model Driven ArchitectureMajong DevJfu
4 - Architetture Software - Architecture PortfolioMajong DevJfu
Último
Meetup_adessoCamunda_2023-09-13_Part1&2_en.pdfMariaAlcantara50
Take Control of Podcasting thanks to Open Source and Podcasting 2.0🎙 Benjamin Bellamy
Need for Speed: Removing speed bumps in API ProjectsŁukasz Chruściel
V3Cube Gojek Clone - Rebrand With SuperiorityV3cube
Product Listing Presentation-Maidy Veloso.pptxMaidyVeloso
Common WordPress APIs - Options APIJonathan Bossenger
17 applied architectures
- 1. Applied Architectures Software Architecture Lecture 17
- 12. An Instance of REST
- 16. An Instance of REST
- 18. Derivation of REST (cont’d) Software Architecture: Foundations, Theory, and Practice ; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; © 2008 John Wiley & Sons, Inc. Reprinted with permission.
Notas do Editor
- Process view of a REST-based architecture at one instance in time. A user agent is portrayed in the midst of three parallel interactions: a, b, and c. The interactions were not satisfied by the user agent’s client connector cache, so each request has been routed to the resource origin according to the properties of each resource identifier and the configuration of the client connector. Request (a) has been sent to a local proxy, which in turn accesses a caching gateway found by DNS lookup, which forwards the request on to be satisfied by an origin server whose internal resources are defined by an encapsulated object request broker architecture. Request (b) is sent directly to an origin server, which is able to satisfy the request from its own cache. Request (c) is sent to a proxy that is capable of directly accessing WAIS, an information service that is separate from the Web architecture, and translating the WAIS response into a format recognized by the generic connector interface. Each component is only aware of the interaction with their own client or server connectors; the overall process topology is an artifact of our view.
- Process view of a REST-based architecture at one instance in time. A user agent is portrayed in the midst of three parallel interactions: a, b, and c. The interactions were not satisfied by the user agent’s client connector cache, so each request has been routed to the resource origin according to the properties of each resource identifier and the configuration of the client connector. Request (a) has been sent to a local proxy, which in turn accesses a caching gateway found by DNS lookup, which forwards the request on to be satisfied by an origin server whose internal resources are defined by an encapsulated object request broker architecture. Request (b) is sent directly to an origin server, which is able to satisfy the request from its own cache. Request (c) is sent to a proxy that is capable of directly accessing WAIS, an information service that is separate from the Web architecture, and translating the WAIS response into a format recognized by the generic connector interface. Each component is only aware of the interaction with their own client or server connectors; the overall process topology is an artifact of our view.