Inheritance (IS-A relationship)
<ul>
<li>Might violate encapsulation
</li>
<li>Turns out bad when it comes to maintenance of code
</li>
<li>Code duplication across subclasses
</li>
<li>Changes in parent class affect the child classes
</li>
<li>Less flexible
</li>
</ul>
Composition (Has-A relationship)
<ul>
<li>Provides a lot of flexibility for changes in behavior
</li>
<li>Encapsulate a family of algorithms into their own set of classes (sounds similar)
</li>
</ul>
To summarize - referring to Strategy Design Pattern.



**Inheritance (IS-A relationship)**

- 
Might violate encapsulation

- 
Turns out bad when it comes to maintenance of code

- 
Code duplication across subclasses

- 
Changes in parent class affect the child classes

- 
Less flexible

**Composition (Has-A relationship)**

- 
Provides a lot of flexibility for changes in behavior

- 
Encapsulate a family of algorithms into their own set of classes (sounds similar)

To summarize - referring to Strategy Design Pattern.

OO Design: What should I choose - Composition vs Inheritance? and why?

👨‍💻 Software Engineer @ServiceNow | Blogs about Backend Development, API Design, Design Patterns, Caching, Java | Might also blog about #Astrophysics ( This is to just show my love for Physics)
