Software Design Architecture Style

Components (services) are designed to perform specific tasks and communicate over a network, enabling reusability and flexibility.

• Architectural style for distributed systems using HTTP. 
• In theory, REST services expose just the data and the data structures (uniquely identified) and allow simple operation over these structures (GET, PUT, POST, DELETE).

Small, focused components communicating over lightweight protocols (e.g., REST).

• Mediator for component communication, managing requests and responses.
• We know everything we want to do, but we do not know who can do it and how we can contact them.

• (P2P): Direct communication and resource sharing among all components (peers).
• The data is not centralized, but everyone can have all the data.

The master component delegates tasks to slave components, improving performance. We have a large task, which can be divided and shared.

Organization of components into tiers, each with specific functionality.

Central server providing services to one or more clients.

Components communicate via events, promoting loose coupling.

Collaborative problem-solving using a shared knowledge base (blackboard).

• Separation of application logic, UI, and data management.
• –Model layer: responsible for data.
• –View layer: responsible for the representation.
• –Controller layer: responsible for the logic.

Hierarchical organization of components by responsibility.

Sequential data processing with components (filters) connected by pipes.

Single unit combining all components, less flexible and harder to maintain.