Deployment Description

WAAS Booster is a dynamic load-based scheduling tool designed for containerized environments. Depending on deployment environments, WAAS Booster can be deployed using either RPM or Kubernetes pods. The following describes the differences between the two deployment modes and their application scenarios.

1. Using RPM
   1. Applies to environments with a small number of service nodes, such as small enterprises or startups. In these environments, complex resource management and scheduling are usually not required.
   2. Applies to environments where Kubernetes is not adopted for containerized management. These environments may use traditional VMs or physical machines to deploy applications.
   3. Applies to scenarios where the O&M automation requirements are not high and manual maintenance and debugging are not frequent. RPM physical machine deployment reduces the dependency on automatic O&M tools and simplifies O&M.
2. Using Kubernetes pods
   1. Applies to environments with many service nodes, such as large enterprises or Internet companies. These environments usually require efficient resource management and scheduling capabilities.
   2. Applies to environments where Kubernetes is adopted for containerized management. In these environments, Kubernetes' automatic deployment, expansion, and management functions can be utilized.
   3. Applies to scenarios where high O&M automation is required. This deployment mode allows for centrally creating, managing, and deleting WAAS Booster service pods on primary nodes, improving system reliability and availability.

When selecting a deployment mode, you should consider the preceding features and application scenarios based on your service requirements, technology stack, and O&M capabilities.

Primary nodes refer to the management nodes in a Kubernetes cluster, and service nodes refer to the nodes deployed with specific services in a Kubernetes cluster.