What is the difference between loosely coupled and tightly coupled in java

This list will sure help us to do the best for our own business. Thank you to all.. If have any doubts, please send email to anilnivargi49 gmail. Thanks for sharing such a nice info with us. Fantastic writing skills. I appreciate this blog. It's highly changeable.

Thanks for this great watch prison school season 2 information. It is really useful. I got cleared doubts Your article is such an informative article. It is glad to read such those articles. Thanks for sharing. Your article is such an informative article audiobook torrents. Thank you for sharing such valuable information, it seems to be very useful for at.

First to understand what is Loose coupling and Tight coupling and also to know the advantage of loose coupling. In short Loose coupling means reducing dependencies of a class that use different class directly. Tight coupling means classes and objects are dependent on one another.

In general tight coupling is usually not good because it reduces flexibility and re-usability of code and it makes changes much more difficult and not easy to test. We will create a class for Extraordinary Worker like below. And we can add one more object in Manager class. We will change the constructor code and in method ManageWork , we will add code to make a call for ExtraordinaryWorker like below.

You saw that Manager class was modified at three places. Add extra object of extraordinary worker, modified constructor, and manageWork method too. You can read open closed oops design principle. NOTE: Note that the loosely coupled code should not be modified or has minimal modification. Disadvantage of above tightly coupled code is that it required modification and testing. In other words, it took effort, testing and time. This is the simple program, but, consider it is in large project and Manager class is very complex and have tons of operations to perform.

In real time no product is released without testing. As a conclusion, tightly coupled code takes maintenance time and huge efforts. We can make the tightly coupled code to loosely couple by using an interface instead of using concrete classes directly.

Loosely coupled code reduces the cost of maintenance and efforts. Below is the same example implemented as a loosely coupled code using interface. I will recommend to read Interface example in java oops. Tight Coupling creates some difficulties. Here, the task of the control object, the object needs to be able to television, the television remote control is dependent on the other phrase.

So, what's the harm of the following dependencies:. TV without a remote control does not work. TV changes the control directly affected by this change.

The Control can only control the TV, cannot control other devices. Loose Coupling. Loose coupling is a design goal that seeks 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.

Loose coupling is a much more generic concept intended to increase the flexibility of a system, make it more maintainable, and makes the entire framework more "stable". WriteLine "Television is started!

We need a managing class that will produce an instance. The instance is generated from the implemented class. The Management Class constructor needs an interface which implements to any Class.

Instance ; remote. Run ; Console. It will save you a lot of time for any project that isn't trivially small, where I define trivially small as less than a couple thousand lines of code depending on the language.

The reason is that once you get past super small projects, each change or update gets harder the more tightly coupled it is. Being loosely coupled enables you to keep moving forward, adding features, fixing bugs, etc. At a certain point I think any program becomes a nightmare to maintain, update and add on to.

The more loosely coupled the design is, the further that point is delayed.