在Spring中，那些构成应用程序主干并由Spring IoC管理的对象 容器被称为bean。bean只是一个实例化、组装等的对象 由Spring IoC容器管理;

Spring beans are classes. Instead of instantiating a class (using new), you get an instance as a bean cast to your class type from the application context, where the bean is what you configured in the application context configuration. This way, the whole application maintains singleton-scope instance throughout the application. All beans are initialized following their configuration order right after the application context is instantiated. Even if you don't get any beans in your application, all beans instances are already created the moment after you created the application context.

你只理解了一部分。您必须根据需要定制bean，并通知Spring容器在需要时管理它，方法是使用Martin Fowler创造的通常称为IoC(控制反转)的方法，也称为依赖注入(DI)。

您以某种方式连接bean，这样您就不必关心实例化或计算bean上的任何依赖项。这就是众所周知的好莱坞原则。

谷歌是最好的工具，除了在这个问题中你会被淹没的链接之外，还可以探索更多关于这个问题的内容。：）

Spring bean只是由Spring容器管理的实例对象，也就是说，它们是由框架创建和连接的，并放入一个“对象袋”(容器)中，您以后可以从那里获取它们。

“连接”部分是依赖注入的全部内容，它的意思是你可以说“我将需要这个东西”，框架将遵循一些规则来为你获得适当的实例。

对于那些不习惯Spring的人来说，我认为Wikipedia Spring的文章有一个很好的描述:

Central to the Spring Framework is its inversion of control container, which provides a consistent means of configuring and managing Java objects using reflection. The container is responsible for managing object lifecycles of specific objects: creating these objects, calling their initialization methods, and configuring these objects by wiring them together. Objects created by the container are also called managed objects or beans. The container can be configured by loading XML files or detecting specific Java annotations on configuration classes. These data sources contain the bean definitions which provide the information required to create the beans. Objects can be obtained by means of either dependency lookup or dependency injection. Dependency lookup is a pattern where a caller asks the container object for an object with a specific name or of a specific type. Dependency injection is a pattern where the container passes objects by name to other objects, via either constructors, properties, or factory methods.

Bean是一个POJO(普通旧Java对象)，由spring容器管理。

默认情况下，Spring容器只创建bean的一个实例。
此bean被缓存在内存中，因此对该bean的所有请求将返回对同一bean的共享引用。

@Bean注释返回一个对象，spring在应用程序上下文中将该对象注册为bean。
方法内部的逻辑负责创建实例。

什么时候使用@Bean注释?

当没有自动配置选项时。 例如，当我们想从第三方库连接组件时，因为源代码不可用，所以我们不能用@Component注释类。

实时场景可能是某人想要连接到Amazon S3桶。 因为源不可用，所以他必须创建一个@bean。

@Bean
public AmazonS3 awsS3Client() {
    BasicAWSCredentials awsCreds = new BasicAWSCredentials(awsKeyId, accessKey);
    return AmazonS3ClientBuilder.standard().withRegion(Regions.fromName(region))
            .withCredentials(new AWSStaticCredentialsProvider(awsCreds)).build();
}

源代码以上的代码-> https://www.devglan.com/spring-mvc/aws-s3-java

因为我上面提到了@Component Annotation。

@Component表示带注释的类是一个“组件”。在使用基于注释的配置和类路径扫描时，这些类被认为是自动检测的候选类。

组件注释将类注册为单个bean。

首先让我们来了解一下春天:

Spring是一个轻量级且灵活的框架。

类比:

Java bean是将许多对象封装到单个对象(bean)中的类。“Bean”这个名称包含了这个标准，它旨在为Java创建可重用的软件组件。

Spring Bean:是一个对象，在Spring容器中创建、管理和销毁。我们可以通过元数据(xml或注释)将对象注入到Spring容器中，这称为控制反转。

类比: 让我们假设农民有一块种种子(或豆子)的农田。 在这里，农民是春天的框架，农田是春天的容器，豆子是春天的豆子，耕种是春天的加工者。

和豆类的生命周期一样，春豆也有自己的生命周期。

img源

下面是Spring中bean生命周期的序列:

Instantiate: First the spring container finds the bean’s definition from the XML file and instantiates the bean. Populate properties: Using the dependency injection, spring populates all of the properties as specified in the bean definition. Set Bean Name: If the bean implements BeanNameAware interface, spring passes the bean’s id to setBeanName() method. Set Bean factory: If Bean implements BeanFactoryAware interface, spring passes the beanfactory to setBeanFactory() method. Pre-Initialization: Also called post process of bean. If there are any bean BeanPostProcessors associated with the bean, Spring calls postProcesserBeforeInitialization() method. Initialize beans: If the bean implements IntializingBean,its afterPropertySet() method is called. If the bean has init method declaration, the specified initialization method is called. Post-Initialization: – If there are any BeanPostProcessors associated with the bean, their postProcessAfterInitialization() methods will be called. Ready to use: Now the bean is ready to use by the application Destroy: If the bean implements DisposableBean, it will call the destroy() method