apisix-go-plugin-runner VS apisix-ingress-controller

In addition to developing plugins and other features using LuaJIT, Apache APISIX also supports the development of plugins using various languages such as Java, Go, Lua, Python, and Wasm. This broad language support allows developers to leverage their existing skills and choose the most suitable language for their specific plugin requirements. It not only reduces development costs but also improves development efficiency, fostering collaboration and innovation within the APISIX community.

Apache APISIX Apache APISIX is an open source, dynamic, real-time, high-performance cloud native API gateway. APISIX provides rich traffic management features such as load balancing, dynamic upstream, canary release, circuit breaking, authentication, observability, and more. Official website https://apisix.apache.org/ GitHub projects APISIX (the core): https://github.com/apache/apisix GitHub - apache/apisix: The Cloud-Native API Gateway GitHub - apache/apisix-dashboard: Dashboard for Apache APISIX GitHub - apache/apisix-website: Apache APISIX Website GitHub - apache/apisix-docker: the docker for Apache APISIX GitHub - apache/apisix-go-plugin-runner: Go Plugin Runner for APISIX GitHub - apache/apisix-java-plugin-runner: APISIX Plugin Runner in Java GitHub - apache/apisix-python-plugin-runner: Apache APISIX Python plugin runner GitHub - apache/apisix-helm-chart: Apache APISIX Helm Chart GitHub - apache/apisix-ingress-controller: ingress controller for K8s

This post shows how to implement it with Apache APISIX.

APISIX Ingress Controller is a tool focused on API management, offering high performance and flexible configuration options. If you require more complex routing rules, rate limiting, circuit breaking, and other advanced features, APISIX Ingress Controller may be a better choice. It provides a rich plugin system, allowing integration of plugins through APISIX Ingress CRD using declarative configuration to handle authentication, authorization, monitoring, logging, and other functionalities. This enriches the capabilities of APISIX Ingress Controller and simplifies configuration.

In this post, I'd like to describe how to fix some of them via the Apache APISIX API Gateway.

In the era of digitization, the availability and stability of services are crucial for the success of enterprises. As a key component of microservices architecture, the API gateway plays a significant role. APISIX, an open-source API gateway platform, ensures the continuity and stability of services through its health check mechanism.

Next February will mark the two-year milestone that I'm working for: API7.ai on Apache APISIX. I'm still very pleased about both. It allows me to do things I like a lot, such as writing posts and giving talks.

In early 2021, I started to work on the Apache APISIX project. I have to admit that I had never heard about it before. In this post, I'd like to introduce some Apache projects that are less well-known than HTTPD or Kafka.

Apache APISIX is an API Gateway, which builds upon the OpenResty reverse-proxy to offer a plugin-based architecture. The main benefit of such an architecture is that it brings structure to the configuration of routes. It's a help at scale, when managing hundreds or thousands of routes.

API resilience is about building robust APIs that can withstand a variety of challenges, ensuring that they continue to function effectively. API Gateways play a key role in this, acting as the entry point for external requests and managing the communication between different services by taking into account common API resilience patterns. One of the popular open-source API Gateways, Apache APISIX, provides a variety of features to enhance the resilience and robustness of APIs. In this article, we will explore 10 common API resilience design patterns and how they can be implemented using APISIX.