Quiz 2 REST Notes

Architecture: how to:
- partition a system
- components identify / communicate
- elements evolve independently
Style: named set of architectural constraints

scalability of component interactions
generality of interfaces
independent deployment of components
intermediary components to
- reduce interaction latency
- enforce security
- encapsulate legacy systems

abstract representation of runtime elements of software systems during its operation phases
Many layers, many kinds BOI
entails
- identity of elements
- allocation of elements
- interaction of elements
- communication (amount, granularity) of elements
- interfaces used by elements for ^ communication

Coordinated set of architectural constraints that restrict roles and features of architectural elements
Relationships permitted among elements
REST is a style
- hybrid style
- “representation” of a resource to transfer resource state which lives on the server into application state on the client

Root is NULL (allow anything)
Client server
- evolve independently
Client stateless server
- client side maintains state
- pros:
  - firewall can inspect request details
  - reliability since state is all on client
  - scalability since less resource consumption
- cons:
  - more data sent over network RIP nexus5x’s (mobile phones)
  - consistency across versions
Caching
- Minimize response time
- Reliability decreases if cache is stale
- Response has to indicate cache-bility
Uniform interface
- dynamic content
- cons
  - transform data to match uniform style
Layered system
- most widespread is 3-tier architecture
  - presentation
  - application processing
  - data management
- layers evolve independently
- Overhead might increase crossing layers
- This + #6 allows for intermediaries(proxies, caches, firewalls)
Code on demand
- clients can download code and run applets/scripts