Loose Coupling

Definitions

1. A design principle where components depend on each other through narrow, well-defined interfaces rather than concrete implementations, so that changes in one component do not cascade through the system. Typically achieved via dependency injection, events, or message passing.

   In plain English: Building parts of a system so they know as little as possible about each other, making it easy to change one part without breaking the rest.

   Example: "The payment service only knows about the order interface, not the order service itself — loose coupling means we can swap in the new order system without touching payments."

Related Terms

• Model-View-Controller
• Model-View-Presenter
• Model-View-ViewModel
• MVC
• MVP Pattern
• Plugin
• Plugin Architecture
• Presenter
• Provider
• Service Layer
• Tight Coupling
• Composite