Core answer
Start here. This is the direct spoken answer to practice first.
Overview
Lazy creation moves bean cost and failure from application startup to the first path that needs the bean.
With lazy initialization, Spring creates many beans only when they are first requested instead of eagerly during context startup. This can reduce startup time and avoid creating unused components. The trade-off is that a missing dependency, invalid configuration, or expensive initialization may surface on the first request rather than during deployment. It can also move latency and memory growth into live traffic, so faster startup is not automatically faster readiness.