Cacheable Responses

Study Notes

REST provides a coordinated set of constraints for designing components in a distributed hypermedia system, leading to a more scalable and maintainable architecture.
Communication occurs through HTTP using the same HTTP methods (GET, POST, PUT, DELETE, etc.).
REST interfaces communicate with external systems using resources identified by URI (Uniform Resource Identifier).

Client-Server: Uniform interface separates clients from servers, allowing for better scalability and performance.
Stateless: Communication between client and server is further constrained by the fact that the server does not maintain any context information between requests.
Cacheable: Responses must define whether they are cacheable or not, to prevent clients from using outdated or inappropriate data.
Layered System: Clients typically cannot detect whether they are connected directly to the end server or to an intermediary on the way.
Code on Demand (optional): Servers can temporarily extend or customize the functionality of a client by transmitting executable code.

Services as Building Blocks: SOA divides application functionality into individual services, each providing a specific function or operation.
Standardized Communication: SOA uses standardized protocols and interfaces for communication between services, such as SOAP or REST.

Independent Deployment and Scaling: Each microservice can be deployed independently of other services, allowing for faster deployment and scaling.
Decentralized Management: Each microservice is responsible for a specific part of the system's functionality, reducing complexity and allowing for greater specialization.
Communication through APIs: Microservices communicate with each other using well-defined APIs, often through HTTP and REST.

Values: Communication, simplicity, feedback, and courage.
Principles: Pair programming, continuous integration, and refactoring.
Test-Driven Development: Write tests before writing code, and refactor code to make it as simple as possible.
Iterative Development: Break down development into small, manageable iterations, with frequent feedback and integration.

Formal Specification: OCL provides a framework for specifying constraints on a model in a formal way.
Declarative Language: OCL is a declarative language, meaning that it does not have side effects and does not change the state of the system.
Expression Language: OCL is used to specify constraints, queries, and derived attributes in a model.