> 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.md).

# Core Concepts

## About

This section focuses on the fundamental principles and mechanisms that form the foundation of the entire Spring Framework. Before diving into advanced modules like AOP, Security, or Data Access, it's essential to understand how Spring manages objects, configurations, environments, and behaviors under the hood.

This section explains how Spring works internally, covering topics like:

* The core container and bean lifecycle
* Dependency injection and Inversion of Control (IoC)
* Profiles to manage environment-specific configurations
* The role of annotations in defining behavior and wiring components

These are the **building blocks** that power every Spring application from a basic REST API to complex enterprise-level systems.

## Why This Section Matters ?

Understanding core concepts allows us to:

* Use Spring more effectively and confidently
* Debug unexpected behavior with clarity
* Customize application behavior through configuration, not code
* Avoid misusing Spring features or writing unnecessary boilerplate

If we only rely on Spring Boot auto-configuration without understanding the core ideas, we may struggle when customization or deeper control is needed.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.pranaypourkar.co.in/the-programmers-guide/spring/core-concepts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
