Dependency injection for beginners
•
9 likes•2,188 views
Dependancy Injection in its simplest form. Helpful for beginners.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Dependency injection for beginners
Similar to Dependency injection for beginners (20)
More from Bhushan Mulmule
More from Bhushan Mulmule (16)
Recently uploaded
Recently uploaded (20)
Dependency injection for beginners
- 1. Dependency Injection for Beginners Bhushan Mulmule bhushan.mulmule@gmail.com www.dotnetvideotutorial.com
- 3. Dependency Injection is a software design pattern that allows the removal of hardcoded dependencies and makes it possible to change them, whether at run-time or compile-time.
- 4. Let us try to understand using simple example
- 5. We are developing bus ticket reservation system for client BigBus.
- 6. When development started client had pretty simple requirements
- 7. One of the requirement was: System should able to book seat. And after booking confirmation email should go to customer.
- 8. To send emails we have created class EmailNotification with a method SendEmail()… SendEmail()…
- 10. And to Book Tickets Created Booking class with a method Book()
- 11. To send notification; Book() method is calling SendEmail() method of EmailNotification class.
- 12. Here Booking class internally use EmailNotification class. Such classes are said to be tightly coupled. [Change in one class can break other]
- 13. Booking class can be consumed in application as follow...
- 14. And the output will be…
- 15. And we had happy client !!!
- 16. But requirements keep changing…
- 17. Now client wanted to send Booking details to cell phone via SMS .
- 18. To fulfill this requirement we need to create new class SMSNotification with method SendSMS()
- 20. And also need to modify class Booking to use SMSNotification instead of EmailNotification
- 22. And System is up again with new changes in place... Output
- 23. Will be dealing with such change requests that easy in real life?
- 24. System can have hundreds of tightly coupled classes. Because of that accommodating such changes can be time consuming and frustrating.
- 25. How to write loosely coupled System?
- 26. Classes should always communicate With each other via Interfaces
- 27. Let us write an interface INotification with a method declaration SendMessage()
- 28. Implement interface in EmailNotification.
- 29. Call method of EmailNotification from Booking using reference of INotification interface
- 30. Using interfaces we have Decoupled Booking and EmailNotification classes.
- 31. Still there is dependency of EmailNotification in Booking class. As we are creating object of EmailNotification inside Booking class.
- 32. Can we move this dependency out of Booking class?
- 33. And the answer is
- 34. Inversion of Control (IoC) or Dependency Injection
- 35. Instead of creating object of EmailNotification in Booking class we will pass it via constructor
- 36. Constructor of Booking class accepts object of class that implements INotification
- 37. We have moved out dependency of Booking class outside of it. And we will inject it to Booking class while creating its object.
- 38. We are injecting object of EmailNotification to Booking class via constructor while creating its object.
- 39. Now Booking class is completely independent of any implementation of INotification
- 40. Congratulations you have just done something known as Dependency Injection Note: This was constructor injection same thing can also be achieved using property injection.
- 41. Now if client will come to us with SMS requirement.
- 42. We just need to create SMSNotification class, implementing INotification interface
- 43. To use SMSNotification we just have to create object of Booking as follow…
- 44. Now we are free to use any implementation of INotification without single modification in Booking class.
- 45. Now Object of Booking class can be created...
- 47. DI is also very helpful for unit testing. If we wanted to test Booking class and don’t want to worry about EmailNotification or SMSNotification we can create mock implementation of INotification and pass it to Booking class object during the test. Will discuss it in Unit Testing session.
- 49. Dependency Injection is a software design pattern that allows the removal of hardcoded dependencies and makes it possible to change them, whether at run-time or compile-time.
- 50. In Part – 2 we will see what is Dependency Injection Container and how to use it to move all the dependencies to it.