“To fix the problem of inconvenient service management and costly R&D investment, we introduced APISIX as our API gateway. APISIX's dynamic performance with etcd aligns most with Beeto's product requirements.”
Director of R&D at Beeto
in migrating from monolith to microservices
APISIX has been implemented as the primary API gateway in the architecture deployment, responsible for handling all traffic. The gateway routes and forwards north-south traffic while also managing east-west traffic for services on the intranet.
The APISIX gateway cluster offers a range of extension tools, including a registry center, service control, service monitoring, protocol forwarding, and plugins for all services.
Apache APISIX can handle various policies at the gateway level, including authentication, service forwarding, and health checks.
Apache APISIX significantly aids Beeto in terms of dynamic service forwarding.
By unifying north-south and east-west traffic, APISIX has helped Beeto save on resources and workforce costs, while enabling dynamic and unified management.
The deployment architecture has been simplified, lowering interaction between the gateway and users.
APISIX's multiple extension plugins have facilitated efficient management of permission verification, route distribution, and health checks for services.
APISIX's ability to dynamically launch and migrate services has been developer-friendly.
“API7 solution performs surprisingly well in its practice in production scenarios. We love its high availability, high performance, and rich functionality, allowing us to build and grow our business in a cloud-native way.”
“After adopting APISIX Ingress Controller, it is easier for developers to add configurations on the gateway than to write codes.”
“After comparing some mainstream gateway products, we find that the response latency of Apache APISIX is more than 50% lower than other gateways, and Apache APISIX can still run stably when the CPU reaches more than 70%.”