“APISIX meets our requirement on speeding development and iteration. What distinguishes APISIX is its rich plugins, visible configuration, fine-grained verification, abundant features, active community, and high performance.”
Xin Zhang
,
Cloud-Native Development Engineer at Horizon Robotics
after using APISIX
at a time in AI model training
Horizon Robotics is a leading advanced driver assistance systems and autonomous driving solutions provider for passenger vehicles, empowered by cutting-edge algorithms, purpose-built software, and state-of-the-art processing hardware.
As a key enabler for smart vehicle transformation and commercialization, it has established cooperation with more than 100 ecosystem industry partners and over 30 automotive companies.
Difficulties are encountered when attempting to achieve fine-grained configuration management in Traefik 1.x. Routing rules are configured through Ingress, and certain plugins require configuration via annotations. This approach is limited to the addition of plugins to rules within Ingress.
Traefik 1.x doesn't support the visual configuration of specific rules and cannot directly locate a specific service by accessing the request URL through web browsers.
Traefik only provides a limited number of default configuration files, ConfigMap, thereby necessitating developers to refer to the official documentation for configuration details. In addition, some parameters are inconsistent with the NGINX's default configuration, which can make maintenance more cumbersome.
Horizon Robotics has selected APISIX Ingress Controller as its traffic management gateway to provide unified service delivery.
All the plugins supported by APISIX can be configured declaratively using apisix-ingress-controller, and the plugins can be customized for a single backend under ApisixRoute.
One major advantage for customers is the visual configuration feature. By utilizing the APISIX Dashboard, customers can view each APISIX route. In the event of a conflict arising from configuring the same domain in multiple namespaces or YAML files, customers can quickly locate the path prefix by searching with the APISIX Dashboard.
The APISIX Ingress Controller implements fine-grained verification of resources declared in the CRD it manages. In cases where a non-existent service is declared, error messages are stored in the ApisixRoute event, preventing the change from taking effect. This feature helps to minimize problems stemming from misuse.
Another key advantage for customers is the rich feature set offered by APISIX. This includes support for hot updates and hot plugins, proxy request rewriting, multiple authentications, and multi-language plugin development, among numerous other capabilities.
APISIX benefits from an active community of maintainers and contributors on Slack, GitHub, and the mailing list, setting it apart from other open-source solution communities.
APISIX's performance exceeds that of Envoy by approximately 120% in pressure tests, with the difference in QPS becoming more pronounced when more cores are involved.
APISIX has enabled Horizon Robotics to streamline operations by facilitating easy uploading of oversized files.
The forward-auth plugin has improved monitoring convenience by reducing the need for a gRPC layer.
Horizon Robotics has implemented the APISIX Prometheus plugin globally and conducted debugging and optimization to increase the number of real-time concurrencies, QPS, the success rate of APISIX real-time interface, and real-time bandwidth.
Drawing from API7's use cases in the automotive industry, Lotus Cars utilizes API7 Enterprise to manage core traffic, accelerate product delivery, and optimize time to market, all while reducing manpower and saving costs.
Apache APISIX supports multiple protocols, saving great R&D costs and endowing our platform with endless vitality.
APISIX helped us greatly improve service quality under active-active architecture. Its complete monitoring feature has effectively supported troubleshooting, and updating the service list has become very simple.