SylviaBABY commented on code in PR #1314: URL: https://github.com/apache/apisix-website/pull/1314#discussion_r963177720
########## blog/en/blog/2021/06/28/why-we-need-Apache-APISIX.md: ########## @@ -1,109 +1,107 @@ --- -title: Why do you need Apache APISIX when you have NGINX and Kong? +title: Why would you choose Apache APISIX instead of NGINX or Kong? slug: 2021/06/28/why-we-need-apache-apisix author: Yuansheng Wang authorURL: "https://github.com/membphis"; authorImageURL: "https://avatars.githubusercontent.com/u/6814606?v=4"; keywords: - APISIX - Kong -- Nginx +- NGINX - API Gateway - Open Source - API Management -description: 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. +description: Many companies used to use NGINX or Kong as their API gateway but switched to Apache APISIX now. As an Open Source API Gateway, Apache APISIX solves a lot of pain points for businesses. tags: [Ecosystem] --- -> 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. +> 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. <!--truncate--> -In the cloud-native era, dynamic capability and observability have become the standards for measuring API gateways. Apache APISIX has been following in the footsteps of cloud-native since its inception. However, as a new-generation API gateway that was born just three years ago, why can Apache APISIX stand out from NGINX, which has been born for more than 20 years, and Kong, which has been open source for 8 years, and become the most popular and active gateway in the cloud-native era? The most important reason is that it solves the pain points of developers and enterprises in using NGINX and Kong. +API gateway is an important infrastructure component in the cloud-native era. There are two common criteria to evaluate an API gateway: how dynamic it is, and how mature its observability is. Many companies used to use NGINX or Kong as their API gateway, but then later switched to Apache APISIX. As an API gateway born for the cloud-native era, Apache APISIX indeed solves a lot of pain points for businesses in various dimensions. Now you might wonder, why? -## NGINX and Kong's Disadvantages +## NGINX and Kong's Limitations -In the era of monolithic services, NGINX can handle most scenarios, but in the cloud-native era, NGINX has two problems due to its architecture: +In the era of monolithic services, NGINX can handle most scenarios. While in the cloud-native era, NGINX has two shortcomings due to its architecture: -- First, NGINX does not support cluster management. Almost every Internet manufacturer has its own NGINX configuration management system, and there is no unified solution. -- The second is that NGINX does not support hot reloading of configurations. If a company modifies the configuration of NGINX, it can take more than half an hour to reload NGINX. And under the Kubernetes system, the upstream will change frequently. If NGINX is used, the service needs to be restarted frequently, which is unacceptable for enterprises. +- NGINX does not support cluster management. Almost every company has its own NGINX configuration management system. Although the systems are similar, there is no unified solution. +- NGINX does not support hot reloading of configurations. If the user modifies the configuration of NGINX, it will be necessary to reload NGINX. Also, in Kubernetes, the services will change frequently. So if NGINX is used to handle the traffic, you must restart the service often, which is unacceptable for enterprises. -The emergence of Kong solves the shortcomings of NGINX, but brings new problems: +Kong solves the shortcomings of NGINX but brings new limitations: -- Kong needs to rely on PostgreSQL or Cassandra database, which makes Kong's entire architecture very bloated and will bring a high availability problem to the enterprise. If the database fails, the entire API Gateway fails. -- Kong's routing uses traversal lookup. When there are more than a thousand routes in the gateway, its performance will drop dramatically. +- Kong needs to rely on a PostgreSQL or Cassandra database, which makes Kong's entire architecture very bloated and would bring a high availability limitation to the enterprise. If the database fails, the whole API Gateway fails. +- Kong's routing uses traversal search. When there are more than a thousand routes in the gateway, its performance will dramatically drop. -The emergence of APISIX solves all the above problems and becomes the most perfect API gateway in the cloud-native era. So what exactly are the advantages of Apache APISIX? Why can it become the most active API gateway in the world in just three years? +The APISIX resolves all the above limitations and becomes the best API gateway in the cloud-native era. Review Comment: ```suggestion The APISIX resolves all the above limitations and becomes the best API gateway in the cloud-native era. ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
