Instead of building its own tools, a piece of code waits for someone else to give them to it. This makes the code much more flexible and easier to change later.

The Hand-it-to-me Rule

This is a special coordinator that delivers the right tools to the right parts of the program. It acts like a waiter who brings exactly what you ordered to your table.

The Delivery Service

This allows you to give a tool to a piece of code later on, only when it is needed. It is like adding a new attachment to a vacuum cleaner for a specific task.

The Optional Upgrade

This is a single location where the program stores and manages all its different tools. It keeps everything organized so the delivery service knows exactly where to find things.

The Central Supply Room

You can swap a real, complex tool for a 'fake' toy version to check if your code works safely. This allows you to practice without making permanent changes to a real database.

Testing with Toy Tools

Since tools are provided from the outside, you can change them without rewriting the entire program. It is like replacing a lightbulb instead of replacing the whole lamp.

Swapping Parts Easily

Code can ask for a general type of tool rather than a specific brand. This makes it easy to switch between different versions of a tool whenever you want.

Using General Blueprints

By letting something else handle the tools, the main code stays clean and simple. It can focus entirely on its own job without worrying about how tools are made.

What is Dependency Injection?