Tight Coupling:
- A Tightly Coupled Object is an object that needs to know about other objects and are usually highly dependent on each other's interfaces. When we change one object in a tightly coupled application often it requires changes to a number of other objects. There is no problem in a small application we can easily identify the change. But in the case of a large applications these inter-dependencies are not always known by every consumer or other developers or there is many chance of future changes.
- Traditionally, connections between applications or between applications and services have been tightly coupled, as with CORBA (Common Object Request Broker Architecture).
- Tightly coupled systems are usually fast and safe, and the risk of transmission errors is very low.
- Tight coupling tends to make component maintenance and reuse much more difficult, because a change in one component automatically means changes in others. Similarly, tight coupling makes extra work when an application has to adapt to changing business requirements, because each modification to one application may force developers to make changes in other connected applications.
Loose Coupling:
- Loose coupling is a design strategy which allows us to reduce the inter-dependencies between components of a system with the goal of reducing the risk that changes in one component will require changes in any other component. It’s all about thinking a problem in generic manner and which intended to increase the flexibility of a system, make it more maintainable, and makes the entire framework more stable.
- One key feature of SOA is the use of loosely coupled connections.
- Loosely coupled systems, on the other hand, are usually more error-prone but also more flexible.
- Being loosely coupled enables you to keep moving forward, modifying/adding features, bugs fixing, etc.
No comments:
Post a Comment