Loose coupling
Description
Components and services should have minimal dependencies on each other. Standardised, business-oriented APIs make sure consumers are not impacted by changes to services. This allows service owners to change implementation, switch out components, or modify data records behind the APIs without downstream impact to end users. This principle ties in with the modularity and resilience principle.
Loose coupling allows service owners to change implementation, switch out components, or modify data records without downstream impact to end users. It hence enables flexibility, scalability and maintainability, and allows for easier system integration.
Loose coupling means components interact with each other with minimal dependencies, allowing changes to one component without significantly affecting others. Loosely coupling ensures better flexibility, easier maintenance, and scalability. Systems can evolve independently without major disruptions.
Risks:
- Requires careful design and implementation to ensure effective communication between loosely coupled components.
- Potential for increased latency or decreased performance due to the need for additional communication.
- Difficulty in debugging or troubleshooting issues that arise from interactions between loosely coupled components.
| Non-Functional Requirement | Issue ID: SIMPL-11049 | Status: Proposed |
Detailed Non-Functional Requirements
Loose coupling and modular architecture
Simpl-Open shall ensure loose coupling between components, allowing ...API-First development approach
Simpl-Open's development methodology shall adopt an API-First ...