> For the complete documentation index, see [llms.txt](https://www.pranaypourkar.co.in/the-programmers-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.pranaypourkar.co.in/the-programmers-guide/spring/core-concepts/spring-beans.md). # Spring Beans ## About **Spring Beans** are the central components of a Spring application. In the Spring Framework, a *bean* is simply an object that is managed by the Spring *Inversion of Control (IoC)* container. When you use Spring, instead of manually instantiating objects with `new`, Spring creates and manages those objects for you. These objects are called **beans**. Think of a Spring bean as a **building block** of your application: it could be a service, a data access object, a utility class, or even a controller - anything that Spring manages and wires into other parts of your code. ## Why Spring Beans Matter ? Spring’s entire architecture revolves around beans: * They **promote loose coupling** through dependency injection. * They **centralize object management**, improving testability and reusability. * They allow **configuration flexibility** using Java config, XML, or annotations. * Beans form the **backbone of Spring modules** like Spring MVC, Spring Data, Spring Security, and more. Without understanding beans, you miss the core benefit Spring provides: **object management with minimal boilerplate**. ## How Spring Creates and Manages Beans ? When Spring starts up, it: 1. Scans for classes annotated with bean-related annotations (like `@Component`, `@Service`, etc.). 2. Instantiates those classes and registers them in the **ApplicationContext**. 3. Resolves dependencies between beans and injects them where needed. 4. Manages their **lifecycle**, including initialization and destruction (optional hooks like `@PostConstruct`, `@PreDestroy`). ## Use Cases of Spring Beans ? * Defining **services** that contain business logic * Managing **repositories** for database access * Creating **configuration beans** for third-party integrations * Injecting **utility components** across multiple classes * Ensuring **reusability** and **testability** by letting Spring manage objects --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://www.pranaypourkar.co.in/the-programmers-guide/spring/core-concepts/spring-beans.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.