Inversion of Control is the principle that gives Spring its name and its power. Rather than each object reaching out to build the things it depends on, control over construction and wiring is inverted and handed to a container. Dependency Injection (DI) is the concrete technique Spring uses to deliver that principle: dependencies are supplied to an object from the outside instead of created within it.
The practical payoff is enormous. Objects that receive their collaborators rather than building them are easier to test, easier to reconfigure, and free of tangled setup code. In this lesson you will learn what a bean is, how the container builds and connects beans, the injection styles available, and why constructor injection is the recommended default in modern Spring.
We continue the cricket league example: a `MatchService` that needs a `PlayerRepository` and a `ScoringService` to do its job. By the end you will see exactly how those three collaborators find each other without a single `new` call in your business code.
Analogy🏏Cricket
🏏 Think of it like cricket: Just as the single main gate of a stadium checks every ticket, directs each spectator to the right stand, and turns away anyone without valid entry — so the stands inside never need their own turnstiles — an API gateway is the one entry point that authenticates, routes, and limits before traffic reaches the services. Consider the alternative to see what the single gate buys: a ground where every stand runs its own turnstile needs ticket staff at each one, and each crew applies the rules slightly differently — one accepts a crumpled ticket another refuses — which is exactly the drift you get when every microservice implements its own authentication and CORS handling. The single gate also concentrates useful knowledge: the stewards there know today's stand closures and redirect spectators smoothly (routes over discovery to healthy instances), and they can throttle entry when the concourse crowds (rate limiting) before congestion reaches the seating. The insight is that concentrating entry control at one gate keeps every stand simpler and the whole ground consistent.
🏏 Showing the Cricket analogy — a Cricket version isn’t available for this concept yet.