How alibaba/higress works
Main components
• Core Gateway: The primary service that interacts with clients, handles HTTP/HTTPS routing (listening on ports like 8080/8443) and provides the UI console (port 8001). Look into the “cmd/higress” for the main entry point.
• Control Plane: This includes configuration management, dynamic updates, and distribution of settings. The “pkg/config”, “pkg/cmd”, and parts of “client” help manage how gateway configurations are formed and distributed. The existence of “istio” and “envoy” directories indicates tight integration with these data/control plane components.
• Wasm Plugin Framework: There is an extensive plugin directory (under “plugins/”) that contains many sub‑directories for plugins in Go, Rust, AssemblyScript, and C++, which indicates that the system has a plug-in architecture for extending functionality.
• Auxiliary CLI Tools: Specifically “hgctl” acts as a command line tool for controlling, installing, performing configuration updates, and managing flows.
• Kubernetes/Helm Integration: The “helm” directory, and associated CRD configurations in the “api” and “client” folders, add an extra layer for Kubernetes deployments and interactions.
• Test and CI/CD: Directories like “.github” and “test” provide CI/CD and end‑to‑end testing which indicate continuous integration but are less part of runtime architecture.
• UI Console component as a separate service/module that interacts with the core (e.g., via API calls or configuration management) and listens on Port 8001.
• An “API/Configuration Management” component that integrates with the “client”, “api”, and “pkg/config” areas. This component can be shown interacting with both the core gateway and the CLI tool.
• Integration with service registries (Nacos, ZooKeeper, Consul, Eureka) as part of the microservice or security gateway functionalities. This can be depicted as external systems that the core gateway queries for service discovery.
• An “Observability & Monitoring” block (which can cover metrics/logs from Envoy, Istio, and plugins) as indicated by the project’s emphasis on high-availability and observability.
Architectural patterns and technologies
• Microservices and cloud‑native: Clearly separate the data plane (the actual ingress data flow) from the control plane (configuration, management, and dynamic updates).
• Plugin-based extensibility: Use a layered approach where the core gateway handles traffic, while Wasm-based plugins (with support for multiple languages) sit in an extensible chain.
• API-driven configuration (via CRDs and CLI “hgctl”): Emphasize the API endpoint for configuration distribution.
• Use of standard tools and integrations: Show that the gateway is built on top of Istio/Envoy and deployable via Kubernetes (Helm charts, CRDs, etc.).