ProductsApache APISIX 3.0: 11 Highlights of Open Source API GatewayThe open source API Gateway Apache APISIX version 3.0 is coming! We have selected 11 essential features to give a brief overview.
TechnologyProductsWhy Is Apache APISIX the Best API Gateway?Why is Apache APISIX the best API Gateway? We will compare multiple API gateways (Kong, Tyk, Gloo) in terms of the popularity among developers, their open source licenses, their performances, and the ecosystem as a whole.
EcosystemWhy would you choose Apache APISIX instead of NGINX or Kong?This article describes the history of the open source API Gateway Apache APISIX architecture's evolution and compares the advantages of the two frameworks, Apache APISIX and NGINX.
EcosystemGCP, AWS, Azure, and OCI ARM-Based Server Performance ComparisonThis article uses Apache APISIX to compare the performance of AWS, Google, Azure, and Oracle ARM-based servers in network IO-intensive scenarios.
AuthenticationPluginsUse Keycloak with API Gateway to secure APIsThis article describes how Apache APISIX integrates with Keycloak (OpenID Connect Provider) to secure your APIs.
EcosystemHow to Integrate API Gateway and Consul?Apache APISIX supports the Consul KV-based service discovery registry. This article will walk you through the process of implementing service discovery and service registry in Apache APISIX.
EcosystemPluginsIntegrating Splunk HTTP Event Collector with API GatewayThis article explains how to configure and use the Splunk HEC service in Apache APISIX.
EcosystemHow to Integrate API Gateway and Consul? Not Consul K/VApache APISIX supports the Consul service discovery registry. This article will walk you through the process of implementing service discovery and service registry in Apache APISIX.
EcosystemAccessing APISIX-Dashboard from Everywhere with Keycloak AuthenticationThis article describes how to setup an external access to apisix-dashboard protecting the URL with authentication managed by a keycloak server.
CommunityRelease Apache APISIX 3.1.0Apache APISIX 3.1.0 is officially released! This version brings a lot of functional support on the security level and adds a built-in debugging plugin, to optimize the experience of using APISIX.
EcosystemWeb resource caching: Server-SideThe subject of Web resource caching is as old as the World Wide Web itself. However, I'd like to offer an as-exhaustive-as-possible catalog of how one can improve performance by caching. Web resource caching can happen in two different places: client-side - on the browser and server side. In the previous post, I explained the former; this post focuses on the latter.
EcosystemWeb resource caching: Client-SideThe subject of Web resource caching is as old as the World Wide Web itself. However, I'd like to offer an as-exhaustive-as-possible catalog of how one can improve performance by caching. Web resource ...
EcosystemHow to choose the right API Style and TechnologyIn this post, we’ll go through the 5 most popular API styles and look at very common questions like “How to decide on the right API style and which technology to choose for a style” and provide practical scenarios where an API Gateway can supplement their weaknesses.
EcosystemA poor man's APICreating a full-fledged API requires resources, both time and money. You need to think about the model, the design, the REST principles, etc., without writing a single line of code. Most of the time, ...
EcosystemGeo-routing with Apache APISIXApache APISIX, the Apache-led API Gateway, comes out of the box with many plugins to implement your use case. Sometimes, however, the plugin you're looking for is not available. While creating your ow...
EcosystemEvent-Driven APIs with Webhook and API GatewayThere are many ways and technology options to consider when implementing an event-driven API. For example, we explored how to build event-driven APIs using these 3 well-known patterns: CQRS, API Gateway and Serverless on the previous blog post. This post elaborates on building event-driven APIs by making use of Webhook and API Gateway, we understand the role of each in this solution. Firstly, let’s turn our attention to the initial problem statement without the webhook in place.
