Architectural Styles

A software architecture structured into distinct layers (tiers), each with a specific responsibility (e.g., Presentation, Domain, Data Source). Layers interact linearly, typically only with adjacent layers (layers directly above or below).

• Key Benefits:

  • Separation of Concerns: Clear division of responsibilities.

  • Modularity: Independent development, testing, and maintenance of layers.

  • Ease of Testing: Layers can be tested in isolation.

  • Maintainability: Changes in one layer minimally affect others.

A network-based model where clients request services/resources from centralized servers. Clients handle user interfaces, while servers manage data, logic, and resource processing.

• Key Benefits:

  • Scalability: Horizontal (adding servers) or vertical (upgrading server hardware) scaling.

  • Centralized Security: Consistent security controls on servers.

  • Resource Optimization: Servers handle heavy computations, keeping clients lightweight.

An architecture where the application is divided into small, independent services (each running a distinct Process (Task)). Services communicate via lightweight protocols (e.g., HTTP/REST).

• Key Benefits:

  • Independent Scaling: Services scale based on individual needs.

  • Technology Flexibility: Use different languages/frameworks per service.

  • Faster Development: Parallel work by teams on different services.

  • Maintainability: Smaller, focused codebases.

Components communicate via messages (e.g., commands, data) using middleware like message queues. Producers send messages, and consumers process them.

• Key Benefits:

  • Loose Coupling: Producers/consumers operate independently.

  • Asynchronous Processing: Non-blocking operations improve efficiency.

  • Scalability: Horizontal scaling of message producers/consumers.

  • Complex Workflows: Supports event-driven processes and orchestration.