Mastering Spring Boot: Deep Dive into Core Extension Points

Spring/Spring Boot Core Extension Points Overview

Spring’s power lies in its highly extensible architecture, allowing precise intervention at various container lifecycle stages.

1. ApplicationContextInitializer

Timing : Before container refresh, the earliest hook.

Purpose

Modify Environment, dynamically add configuration sources.

Activate or switch profiles.

Customize ApplicationContext configuration.

Best practice : Register in spring.factories to run earlier than auto‑configuration.

2. BeanFactoryPostProcessor

Timing : Before bean instantiation, during BeanDefinition modification.

Purpose

Uniformly modify property placeholders (e.g., PropertySourcesPlaceholderConfigurer).

Dynamically modify or register Bean definitions.

Best practice : Use for global Bean definition adjustments without depending on concrete instances.

3. BeanPostProcessor

Timing : After bean instantiation and dependency injection, before/after init methods.

Purpose

AOP proxies (transactions, async).

Custom annotation processing.

Bean instance enhancement (performance monitoring, logging).

Best practice : Be aware of global impact; keep performance and scope in mind.

4. FactoryBean

Timing : Bean retrieval stage, replaces complex object creation.

Purpose

Encapsulate third‑party object construction (e.g., MyBatis SqlSessionFactoryBean).

Hide intricate creation logic.

Best practice : Access the FactoryBean itself via &beanName.

5. Advisor (AOP)

Timing : Method invocation (before, after, around).

Purpose

Transactions (@Transactional).

Security checks.

Logging, performance monitoring, retry mechanisms.

Best practice : Prefer Spring’s declarative annotations to avoid reinventing the wheel.

6. HandlerInterceptor

Timing : Web request lifecycle – before/after controller, after request completion.

Purpose

Authentication/authorization.

Logging and monitoring.

Pre‑process request parameters (multi‑tenant, i18n).

Best practice : Register via WebMvcConfigurer for web‑level interception.

7. @RestControllerAdvice

Timing : When a controller throws an uncaught exception.

Purpose

Uniform JSON error response.

Distinguish business vs system exceptions.

Centralized exception logging.

Best practice : Combine with @ExceptionHandler to provide safe, user‑friendly error messages.

8. CommandLineRunner / ApplicationRunner

Timing : After the application has fully started.

Purpose

Cache warm‑up.

Data initialization.

Service registration.

Best practice : Use @Order to control execution order of multiple runners and ensure idempotency.

9. @Import and ImportSelector

Timing : During configuration class parsing.

Purpose

Auto‑configuration – core of Spring Boot.

Modular feature toggles (e.g., @EnableXXX).

Best practice : Essential when developing a starter; combine with conditional annotations such as @ConditionalOnClass.

Mastering these extension points moves you from a Spring user to an architecture‑level driver, enabling fine‑grained customization across container startup, bean management, web layer, and runtime.