Welcome to this lesson! So far, you have explored the foundational structure of a Spring Boot project. In this lesson, you'll delve into a crucial aspect of Spring Boot — Spring Beans. You'll learn how to create, manage, and utilize Spring Beans. Together, we'll understand dependencies, manual dependency management, Inversion of Control (IoC), and Dependency Injection (DI). We'll explore annotations like @Component and @Bean and see how they simplify dependency management using Spring Context. By the end of this lesson, you'll be equipped to leverage Spring's capabilities for effective bean management.

Before diving into Spring Beans, let's clarify what a dependency is. Imagine you're building an application to prepare a sandwich. You can create a few classes like Bread, Lettuce, Tomato, and Cheese. Obviously, you'll also need a Grill class. Lastly, you'll need a skilled person to put all these ingredients together — the sandwich maker. The sandwich maker requires all the ingredients and a grill to prepare the sandwich, so all these objects are dependencies of the sandwich maker.

Now, let's understand the complication of manually managing object dependencies. Imagine you need to grill a sandwich and you manually create all ingredients and the grill. Here’s a simplified code snippet to demonstrate this:

In this example, you manually handle all dependencies. While it looks simple, you need to ensure that you create all objects without dependencies first (bread, lettuce, tomato, and cheese) before constructing the more complex sandwichMaker object that requires these dependencies. Now, imagine you're working on an application for car manufacturing, where you try to assemble a car with thousands of components. As the number of dependencies grows, managing them manually becomes increasingly cumbersome.

This is where Inversion of Control (IoC) and Dependency Injection (DI) come into play. IoC is a broad principle or design pattern that inverts or delegates the control of object creation, configuration, and management from the class itself to an external framework. DI is a specific form of IoC, where dependencies are injected by the framework.

Spring manages objects in an IoC container called the Spring Context. Objects managed by the Spring Context are known as beans. The Spring Context is aware of all available beans and can determine the order and manner in which objects should be created.

Think of @Component as a special label that you put on a class to tell Spring, "Hey, this class should be managed by you!" By annotating a class with @Component, Spring will create a single instance of that class and manage it as a bean:

This automatically allows Spring to manage Grill as a bean within the context.

Let's break down what @Component does:

• Discovery: When you run your Spring application, it will look through the code for classes labeled with @Component.
• Creation: Spring will automatically create an instance (object) of each class it finds with this label. This means you don't have to manually create these objects yourself.
• Management: Spring takes responsibility for these objects. It ensures they are created, configured, and provided wherever needed in your application.

This is useful for multiple reasons:

• Reduces Manual Work: You don't need to write code to create objects of these classes repeatedly. Spring handles that for you.
• Centralized Management: Spring keeps track of all these labeled classes, making it easier to manage dependencies and configurations.
• Dependency Injection: Spring can automatically provide these objects to other parts of your application that need them.

The process where Spring searches for classes labeled with the @Component annotation, or other specific stereotype annotations like @Service and @Repository, is called component scanning.

It is essential to understand that Spring Boot scans only the base package of your application—where the bootstrap class is located—and its subpackages. For instance, if your bootstrap class is in the src/main/java/com/codesignal/todo-app folder, all your components should be within this folder or its subfolders. If you place a component class in src/main/java/com/codesignal/some-other-folder, it will be ignored.

In addition to @Component, you can explicitly define beans using the @Bean annotation inside a configuration class. This offers you fine-grained control over bean creation.

This allows you to manage and configure beans with more flexibility and precision.

For better organization, you can extract configurations to separate files using the @Configuration annotation:

Spring will scan all classes, and if it finds classes annotated with @Configuration, it will scan the methods. For methods annotated with @Bean, it will instantiate beans. Configuration classes make sense if you want to have separate configurations for different domains of your application. For example, you can have a separate configuration class for instantiating objects related to database connection: DatabaseConfiguration, and another for security-related objects: SecurityConfiguration.

In this lesson, you learned how to create and manage Spring Beans using @Component and @Bean annotations. Starting with the concept of dependencies and the challenge of manual dependency management, you were introduced to Inversion of Control (IoC) and Dependency Injection (DI). You saw how the Spring Context manages dependencies and how @Component enables automatic bean management. The @Bean annotation offers more control, while @Configuration aids in organizing beans in separate configuration files. Now, you’re ready for hands-on practice to solidify your understanding. Happy coding!