1 views collected around this technical thread.
This article presents the motivation, architecture, component selection, user authentication flow, micro‑service integration, and technical details—including custom Lua plugins and NGINX phases—of an automated operations platform built on the cloud‑native API gateway Apache APISIX.
The article explains the specific stability, regulatory, and precision requirements of financial software, examines Java's role in the sector, describes the shortcomings of Spring Cloud Gateway, and details how Apache APISIX was adopted, deployed, customized, and evaluated to improve performance, cost, and operational efficiency in a cloud‑native environment.
The Apache APISIX community announced the 2.13.0 LTS release, enhancing stability, adding observability plugins, a new OpenTelemetry tracing plugin, multi‑language (Wasm, Python, Go) support, and a comprehensive list of bug fixes and improvements.
This article details the evaluation, migration, and practical implementation of replacing Ingress‑Nginx with Apache APISIX Ingress at YouPai Cloud, covering architectural changes, performance trade‑offs, configuration methods, health‑check strategies, and future expectations for a unified cloud‑native gateway.
Apache APISIX 2.9 introduces the authz‑casbin authorization plugin, dynamic per‑route real‑ip configuration, and significant enhancements to external plugin mechanisms, including unique keys for Plugin Runner and reverse information retrieval, alongside richer features for existing plugins such as request‑id and error‑log‑logger.
This article introduces Apache APISIX, examines the challenges of using it as a data‑plane in a service‑mesh architecture, presents the apisix‑mesh‑agent as an intermediary solution, and outlines the advantages, design, and future roadmap of a APISIX‑based cloud‑native service mesh.
This article explains how etcd 3.x switched its external API to gRPC, the challenges of using its gRPC‑gateway for HTTP requests in Apache APISIX, the default message size limit causing sync failures, and the certificate configuration pitfalls that were fixed through a PR merged in v3.5.0.
This article details the 360 team’s decision to adopt Apache APISIX for their gateway layer, describes the production architecture, containerized deployment steps, plugin development workflow, and operational metrics, providing a practical guide for building and managing a high‑performance API gateway.