[GitHub] [apisix] spacewander commented on a change in pull request #6695: docs: update FAQ docs

[GitBox <gi...@apache.org>]

spacewander commented on a change in pull request #6695:
URL: https://github.com/apache/apisix/pull/6695#discussion_r833836188



##########
File path: docs/en/latest/FAQ.md
##########
@@ -469,40 +468,47 @@ HTTP/1.1 200 OK
 ......
 ```
 
-The route was created successfully. It means that the modification of `X-API-KEY` takes effect.
+**Note**: By using the default token, you could be exposed to security risks. It is recommended to update it when deploying to a production environment.

Review comment:
       ```suggestion
   **Note**: By using the default token, you could be exposed to security risks. It is required to update it when deploying to a production environment.
   ```
   would that be better?

##########
File path: docs/en/latest/FAQ.md
##########
@@ -21,74 +21,80 @@ title: FAQ
 #
 -->
 
-## Why a new API gateway?
+## Why do I need a new API gateway?
 
-There are new requirements for API gateways in the field of microservices: higher flexibility, higher performance requirements, and cloud native.
+As organizations move towards cloud native microservices, there is a need for an API gateway that is performant, flexible, secure and scalable.
 
-## What are the differences between Apache APISIX and other API gateways?
+APISIX outperforms other API gateways in these metrics while delivering functions like dynamic routing, a plugin mechanism, a low code dashboard and more.
 
-Apache APISIX is based on etcd to save and synchronize configuration, not relational databases such as Postgres or MySQL.
+## How does Apache APISIX differ from other API gateways?
 
-This not only eliminates polling, makes the code more concise, but also makes configuration synchronization more real-time. At the same time, there will be no single point in the system, which is more usable.
+Apache APISIX differs in the following ways:
 
-In addition, Apache APISIX has dynamic routing and hot loading of plug-ins, which is especially suitable for API management under micro-service system.
+- It uses etcd to save and synchronize configurations rather than relational databases like PostgreSQL or MySQL. This eliminates the need for polling, synchronizes the configuration in real-time, makes the code concise and avoids a single point of failure.
+- Supports dynamic routing.

Review comment:
       Almost every gateway supports dynamic routing...




-- 
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: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org