Skip to main content

components

The role of a component is to enable developers to define the deployment pattern of a business unit without paying attention to the underlying infrastructure, and a component describes a functional unit that can be instantiated as part of a larger distributed application.For example, each microservice in an application is described as a component.Another example is Wordpress+Mysql business system Wordpress and Mysql are described as components respectively.

The component model has the following main properties：

  • Build source defines the construction method of components, mainly including source code class, image class and application model class.
  • Component type defines the deployment mode of the component. Currently, Rainbond supports single-instance stateless, multi-instance stateless, single-instance stateful, and multi-instance stateful types, and later supports Operator-based mode for component type expansion.
  • Environment configuration Define the component running environment configuration, including environment variables and configuration files.
  • storage defines the persistent storage requirements of the component.
  • Port defines the ability of the component to provide services to the outside world.
  • Resource assignment and number of instances Define the scale of the component deployment.
  • Dependencies Define inter-component communication dependencies and variable injection configuration.

How to make good use of "components"​

The division of components is a crucial thing, and developers need to master the following principles：

  • One component and one service;

  • One component and one main process;

  • A component has a clear business boundary;

  • Stateful and stateless separation;

In Rainbond, one component is one container, so if it is a custom image scene, the idea of image creation should be consistent with the idea of component division.In Kubernetes-native scenarios, there is often a pattern of multiple containers in the same Pod.In general, it is composed of a main business container plus some operation and maintenance feature containers, such as Mysql+Mysql monitoring container, API service plus log collection container, etc. There are main and secondary containers. The main container is for business, and the secondary container is for general operation and maintenance. Therefore, in Rainbond, the Pod multi-container capability is used as a component +plug-inmode.The component defines the main business, and the plug-in defines the operation and maintenance characteristics and is general.

Make external services a Rainbond component​

The Rainbond platform manages the business system of the enterprise in a unified manner. It is inevitable that some businesses may not be able or necessary to migrate to the Rainbond cluster, but the existing components in the cluster may need to communicate with it or want to manage the external network traffic through the Rainbond gateway.For such scenarios Rainbond extends a special "component" type,third party components.By specifying the communication address of the third-party component, it is brought into the scope of Rainbond unified management.