Architecture
The Alauda Application Services platform is a robust, open-source service management solution built on Kubernetes (K8S), tailored for seamless Alauda Application Services operations. It serves as a centralized hub, efficiently orchestrating a diverse range of popular service components, including MySQL, Redis, Kafka, and RabbitMQ. Here's how it works:
-
Service Components: The platform supports key services like MySQL, Redis, Kafka, and RabbitMQ, ensuring stable, reliable operation across all components.
-
Common Services: It provides parameter templates, inspection, alert management, backup services etc, offering users a one-stop service management solution.
-
Operator Controller: The Operator Controller is an extension of Kubernetes, designed to simplify the deployment and management of applications. It extends the Kubernetes API through Custom Resource Definitions (CRD) to manage the lifecycle of applications.
-
Container Infrastructure: The Alauda Application Services platform is built on Kubernetes and leverages the underlying infrastructure it provides to offer foundational capabilities such as data persistence and external access.
Rich Services Support
The Alauda Application Services platform supports various types of services, including databases, caches, message queues, etc. The following are the main supported alauda application services versions and compatible storage class information:
| Alauda Application Services | Version | Data Persistence Compatible Storage Class | Backup Compatible Storage Class | Default Scheduling Rule (Single Instance) |
|---|---|---|---|---|
| MySQL-PXC | 5.7 | TopoLVM (recommended) | S3 (recommended), TopoLVM | At most (required) only one MySQL node can be scheduled on each node. |
| MySQL-MGR | 8.0 | TopoLVM (recommended) | S3 (recommended) | At most (required) only one MySQL node can be scheduled on each node. |
| Redis | 5.0, 6.0, 7.2 (recommended) | TopoLVM (recommended) | S3 (recommended), CephFS, NFS | Cluster mode: At most (required) only one Redis node can be scheduled on each node. Sentinel mode: At most (required) only one Redis data node or one Redis sentinel node can be scheduled on each node. |
| Kafka | 3.8 (recommended) | TopoLVM (recommended) | - | At most (required) only one Broker node can be scheduled on each node. |
| RabbitMQ | 3.8.16, 3.12.4 | TopoLVM (recommended) | - | At most (required) only one RabbitMQ node can be scheduled on each node. |
| PostgreSQL | 11, 12, 14 | TopoLVM (recommended) | S3 (recommended) | Strive to schedule one PostgreSQL node on each node. |