Alibaba Cloud Knative is developed based on open source Knative and enhanced for Alibaba Cloud services. This topic compares Alibaba Cloud Knative and open source Knative in terms of O&M, ease of use, elasticity, Ingresses, eventing, monitoring, and alerting.
Item | Alibaba Cloud Knative | Open source Knative | References (Alibaba Cloud Knative) |
Cost of platform development and O&M |
| You need to purchase resources to develop a platform, and platform upgrades and maintenance require manpower. | |
Ease of use | Provides rich features and an easy-to-use comprehensive monitoring system. | You need to manually develop and maintain the components in your monitoring system. This requires technical expertise. | |
Elasticity | Supports the following scaling features:
| Supports KPA and HPA. | |
Ingresses | Supports open source Ingresses such as Kourier and Alibaba Cloud Ingresses provided by Application Load Balancer (ALB), Microservices Engine (MSE), and Alibaba Cloud Service Mesh (ASM). | Supports only open source Ingresses, such as Kourier and Istio. You need to manually maintain these Ingresses. | |
Eventing | Supports integration with EventBridge. | Supports integration only with open source Knative Eventing. | Use EventBridge to trigger Knative Services to consume events |
CI/CD | Supports integration with Apsara Devops services. | You need to manually develop a CI/CD platform. | - |
Monitoring and alerting | Supports a variety of metrics, including the QPS, response time, and service success rate metrics, and allows you to create custom alert rules and send alerts through DingTalk messages, phone calls, or text messages. | Supports only basic metrics. You need to manually develop an alerting system. | |
Alibaba Cloud service integration | Supports integration with Elastic Container Instance (ECI), Container Registry, Application Real-Time Monitoring Service (ARMS), and Simple Log Service to provide one-stop experience. | Does not support integration with Alibaba Cloud services. | - |