This is an automated email from the ASF dual-hosted git repository.
juzhiyuan pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/apisix-website.git
The following commit(s) were added to refs/heads/master by this push:
new ee991e06c33 docs: added apache-apisix-v3-preview (#1337)
ee991e06c33 is described below
commit ee991e06c3352c4ee215d01e679947d31d7e22a1
Author: 琚致远 <[email protected]>
AuthorDate: Thu Sep 22 15:55:09 2022 +0800
docs: added apache-apisix-v3-preview (#1337)
---
.../en/blog/2022/09/21/apache-apisix-v3-preview.md | 201 +++++++++++++++++++++
blog/en/config/picked-posts.json | 1 +
2 files changed, 202 insertions(+)
diff --git a/blog/en/blog/2022/09/21/apache-apisix-v3-preview.md
b/blog/en/blog/2022/09/21/apache-apisix-v3-preview.md
new file mode 100644
index 00000000000..91d3559e43b
--- /dev/null
+++ b/blog/en/blog/2022/09/21/apache-apisix-v3-preview.md
@@ -0,0 +1,201 @@
+---
+title: "Apache APISIX 3.0: 10 Highlights of Open Source API Gateway"
+authors:
+ - name: Ming Wen
+ title: Author
+ url: https://github.com/moonming
+ image_url: https://avatars.githubusercontent.com/u/26448043
+keywords:
+ - Ingress controller
+ - Open Source API Gateway
+ - API Management Platform
+ - The Best API Gateway
+ - Apache APISIX
+description: The open source API Gateway Apache APISIX beta version 3.0 is
coming! We have selected ten essential features to give a brief introduction
before the official release.
+tags: [Products]
+image: https://static-site.apiseven.com/wp-content/uploads/2022/09/APISIX.webp
+---
+
+> The open source API Gateway Apache APISIX beta version 3.0 is coming! We
have selected ten essential features to give a brief introduction before the
official release.
+
+<!--truncate-->
+
+[API Gateway](https://apisix.apache.org/docs/apisix/terminology/api-gateway/)
has acted as an essential component for a long time. It has been committed to
providing various functions such as [rate
limiting](https://apisix.apache.org/docs/apisix/plugins/limit-req/),
authentication (e.g., [Use Keycloak to secure
APIs](https://apisix.apache.org/blog/2022/07/06/use-keycloak-with-api-gateway-to-secure-apis/)),
and observability at the business level.
+
+With the iteration of server-side technologies, more and more services have
begun to migrate from bare metal to Kubernetes, and the original monolithic
architecture has gradually evolved into a microservice architecture. At the
same time, enterprises have started to migrate their on-premise data centers to
multi-cloud or hybrid clouds.
+
+With these technological advancements in the environment, the requirements for
API gateways at the business level have become increasingly complex.
+
+## API Gateway Apache APISIX
+
+[Apache APISIX](http://github.com/apache/apisix) was born to help enterprises
solve new problems in cloud-native environments and microservices. For example,
it provides autoscaling of the business traffic through the fully dynamic
feature and one-time modification to more conveniently achieve cluster
management.
+
+Therefore, in the architectural design of APISIX, the data plane and the
control plane are separated to achieve fully dynamic and cluster management,
which is mainly accomplished by etcd components.
+
+
+
+APISIX stores and manages routing-related and plugin-related configurations in
etcd. As shown in the figure above, the configurations from [Admin
API](https://apisix.apache.org/docs/apisix/admin-api/) (Control Plane) are
stored in etcd, while the data plane on the left mainly monitors the changes of
etcd. The data plane can quickly observe changes without needing to modify
configuration files.
+
+But just solving these problems is not enough. As a middleware with requests
from both
[upstream](https://apisix.apache.org/docs/apisix/terminology/upstream/) and
downstream, the API gateway plays a crucial position in the enterprise
architecture as the traffic entrance and the connection between the service
layers. API gateway's role differs from databases that only receive requests
from the user's business level.
+
+In addition to business-level requirements, API gateways also have
requirements for customization and integration. So how to make custom
development easier for developers when using APISIX is another significant pain
point that APISIX solves, lowering the threshold for developers to code.
+
+In APISIX, plugins are developed mainly through Lua, and
[LuaJIT](https://apisix.apache.org/blog/2021/08/25/why-apache-apisix-chose-nginx-and-lua/)
(a Just-In-Time Compiler for Lua) is used to ensure that the compiled code
performance is good enough. However, as a relatively minor language, the
learning cost of Lua is high for most backend engineers. To solve this problem,
APISIX provides two solutions.
+
+## Support More Programming Languages
+
+The first solution is to support more widely-used programming languages
(such as [Java](https://github.com/apache/apisix-java-plugin-runner),
[Python](https://github.com/apache/apisix-python-plugin-runner),
[Go](https://apisix.apache.org/blog/2021/08/19/go-makes-apache-apisix-better/),
etc.) through [Plugin
Runner](https://apisix.apache.org/docs/apisix/external-plugin/). You will know
at least one of these languages if you are a backend engineer. Using Plugin
Runner, backend engineers [...]
+
+The advantage of this is to reduce development costs and improve development
efficiency. The disadvantage will be performance losses. So, is there a way to
achieve the near-native performance of Lua using high-level languages that
developers are familiar with?
+
+
+
+## Support WASM
+
+The second solution is to use Wasm to develop plugins, as shown in the left
part of the above figure. Wasm (WebAssembly) was first used as a new type of
technology that runs in browsers, but now it is also gradually showing its
advantages on the server side.
+
+We embedded [Wasm](https://apisix.apache.org/docs/apisix/wasm/) into APISIX,
and users can use Wasm to compile Wasm bytecode to run in APISIX. Furthermore,
to use Wasm, we developed a Wasm plugin where users can establish near-native
APISIX plugins using high-level programming languages.
+
+As a result, users can use Lua, Go, Python, Wasm, etc., to write custom
plugins on APISIX. Furthermore, making development easy opens doors for APISIX
plugin development.
+
+Thanks to APISIX's architecture and performance upper hand, APISIX's global
user growth has far exceeded expectations in the three years since its
inception. For example, big Chinese tech companies such as
[WPS](https://apisix.apache.org/blog/2021/09/28/wps-usercase/), [Sina
Weibo](https://apisix.apache.org/blog/2021/07/06/the-road-to-customization-of-sina-weibo-api-gateway-based-on-apache-apisix/),
and [iQiyi](https://apisix.apache.org/blog/2021/09/07/iqiyi-usercase/) are
enterprise-lev [...]
+
+## 10 New Highlights of APISIX 3.0
+
+APISIX proposed a new [3.0
Roadmap](https://github.com/apache/apisix/issues/6473) in early 2022. In
version 3.0, its iterations and updates will focus on usability and the
ecosystem.
+
+
+
+APISIX plans to launch beta version 3.0 by the end of September. Here, we have
selected the following ten eye-catching features to give a brief introduction
before the official release.
+
+### Full Support of ARM64
+
+ARM64 has become a very mainstream server architecture selection for cloud
manufacturers. From [AWS
Graviton](https://apisix.apache.org/blog/2022/06/07/installation-performance-test-of-apigateway-apisix-on-aws-graviton3/),
[GCP Tau
T2A](https://apisix.apache.org/blog/2022/07/22/how-is-google-cloud-tau-t2a-performing/)
to Huawei Kunpeng and other products, we can see that various cloud
manufacturers have begun to launch servers based on the Arm architecture. The
following graph shows the [...]
+
+
+
+According to the current data, the performance of Arm-based servers is
slightly better than the performance of the x86. To conform to the
technological trend of the times, APISIX also did comprehensive CI regression
testing on ARM64 to ensure that users can still run various functions smoothly
when running APISIX in the Arm architecture.
+
+### Adding gRPC Client
+
+In version 3.0, Apache APISIX will support a new `core.grpc` module. However,
if you are familiar with NGINX and OpenResty, you should know that their
support for gRPC is pretty limited, only providing basic features like reverse
proxy or load balancing.
+
+APISIX has already implemented the transcode between gRPC and HTTP protocols
in the current 2.x version. In version 3.0, Apache APISIX will add a new gRPC
client to allow developers to directly call third-party gRPC services without
introducing additional components or requiring service providers to use
different HTTP interfaces, making the process much simpler.
+
+### Redesigning Admin API
+
+When using APISIX today, you may find that the response body of APISIX is
mixed with a lot of meaningless data, such as some etcd return values that are
passed directly to the client without any tailoring. Also, the entire response
body’s architectural design is not ideal, with many redundant fields.
+
+In APISIX 3.0 version, the response body’s structure has been improved. In
addition, the new design makes the overall request format and returns body more
RESTful, making it easier for users to use the latest version of Admin API. Of
course, this process also allows you to set which version of the Admin API to
use through parameters, freeing users from fears of upgrading to incompatible
versions.
+
+### Data Plane(DP) and Control Plane(CP) Separation
+
+APISIX has suffered several security-related vulnerabilities in the last two
years. The root cause of most vulnerabilities is that the DP and the CP are
deployed together in the default deployment mode. Therefore, once a security
vulnerability exists on the data plane, an attacker can directly invade the CP
through the DP, affecting all other DPs.
+
+Therefore, in version 3.0, the [deployment
mode](https://apisix.apache.org/docs/apisix/next/deployment-modes/)
configuration is supported, and the default deployment mode is `traditional`,
where the DP and the CP are deployed together. Of course, the new deployment
mode recommends that you set the attribute to data_plane or control_plane to
separate them.
+
+When they are separated, not only can the security risks mentioned above be
solved, but function iterations on the DP and CP are also more manageable
without affecting each other.
+
+### Improved Service Discovery Support
+
+In the current version, APISIX has supported the integration of many service
discovery components, such as Apache ZooKeeper,
[Consul](https://apisix.apache.org/blog/2022/02/25/consul-api-gateway/),
[Nacos](https://apisix.apache.org/blog/2022/02/21/nacos-api-gateway/), and so
on. But at the moment, these integrations are all done on the data plane. Once
you have a lot of nodes on the DP, it will put much pressure on the following
service discovery components. At the same time, in the actu [...]
+
+Therefore, in APISIX 3.0, we added a layer of abstraction by adding a
sub-project APISIX-SEED to achieve the service discovery support at the control
plane level and reduce the pressure on the service discovery component.
+
+
+
+### Adding xRPC Framework
+
+TCP Proxy is supported in the current version of APISIX, but there are times
when a pure TCP protocol proxy is insufficient. Users need a proxy for specific
application protocols, such as Redis Proxy, Kafka Proxy, etc., because some
functions can only be implemented after the protocol is encoded and decoded.
+
+Therefore, in version 3.0, APISIX implements a transport layer protocol
extension framework called xRPC that allows developers to customize specific
application protocols. Based on xRPC, developers can encode and decode requests
and responses through Lua codes and then realize fault injection, log
reporting, and dynamic routing based on understanding the content of the
protocol.
+
+Based on the xRPC framework, APISIX can provide proxy implementations for
several mainstream application protocols. At the same time, users can also
support their own private TCP-based application protocols based on this
framework, enabling them to have precise granularity and higher order
application layer control similar to HTTP protocol proxy. Furthermore, on top
of different protocols, some common factors can be abstracted to implement
related plugin features so that other protocols [...]
+
+### Supporting More Observability on Transport Layer Protocols
+
+APISIX has always invested heavily in observability support, supporting almost
all observability components, such as
[Zipkin](https://apisix.apache.org/blog/2022/02/28/apisix-integration-opentelemetry-plugin),
[Apache
SkyWalking](https://apisix.apache.org/blog/2021/12/07/apisix-integrate-skywalking-plugin/),
[Datadog](https://apisix.apache.org/blog/2021/11/12/apisix-datadog/), and
more. Various logging components are also supported, but most are carried out
in the application layer.
+
+Apache APISIX will add more transport layer observability support in 3.0. For
example, the support for
[Prometheus](https://apisix.apache.org/docs/apisix/plugins/prometheus/) and
various logs has been added, enabling users to observe the problems of
application layer traffic easily and enabling users to check the operation
status of transport layer traffic.
+
+### Integrating the OpenAPI Specification
+
+API is an element that involves the entire lifecycle of development, from
designing to coding, testing, and deploying. In APISIX 3.0, Apache APISIX will
support the standard OpenAPI 3.0 specification.
+
+Therefore, if you manage the APIs on API design and testing software, it is
straightforward to manage and maintain the data in APISIX by exporting and
importing it. At the same time, various APIs in APISIX can also be shipped
through the OpenAPI 3.0 specification and then imported into other systems for
use.
+
+In addition, APISIX 3.0 also supports Postman-related custom formats (Postman
Collection Format v2), enabling data transfer between the two, thus making
integration easier.
+
+### Full Support for Gateway API and Service Mesh
+
+Support for the [Gateway API](https://gateway-api.sigs.k8s.io/) has begun in
the [APISIX Ingress
Controller](https://github.com/apache/apisix-ingress-controller/issues?q=gateway+api),
and nearly all Gateway API configurations are supported in the latest 1.5
release.
+
+In this case, the APISIX Ingress can be configured using the Gateway API,
which means you can switch between different data planes. By the end of this
year, APISIX Ingress will have complete support for the Gateway API and
additional transport and application layer features.
+
+Unlike most service mesh solutions, APISIX's service mesh solution has
advantages in the data plane (due to the high performance of APISIX itself).
So, in selecting the control plane, we hope it will be compatible with some
mainstream solutions in the community. Finally, by using the xDS protocol to
integrate with Istio and writing the obtained configuration to the xDS
configuration center of APISIX, the specific routing rules are generated by
APISIX to complete the corresponding routing [...]
+
+This solution not only makes the entire service mesh lighter but also makes
custom development and migration more convenient with the high scalability of
APISIX.
+
+### Integrate with More Ecosystems
+
+In addition to the OpenAPI standard mentioned above, many ecosystem plugins
will be added in version 3.0, such as OpenFunction, ClickHouse, Elasticsearch,
SAML, CAS, etc., to integrate more support for authentication, security, and
observability.
+
+One of the exciting plugins,
[workflow](https://apisix.apache.org/docs/apisix/next/plugins/workflow/), is
used for traffic scheduling: we can do some granular processing at the traffic
control level.
+
+```shell
+curl http://127.0.0.1:9180/apisix/admin/routes/1 \
+-H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '
+{
+ "uri":"/hello/*",
+ "plugins":{
+ "workflow":{
+ "rules":[
+ {
+ "case": [
+ ["uri", "==", "/hello/rejected"]
+ ],
+ "actions": [
+ [
+ "return",
+ {"code": 403}
+ ]
+ ]
+ },
+ {
+ "case": [
+ ["uri", "==", "/hello/v2/appid"]
+ ],
+ "actions": [
+ [
+ "limit-count",
+ {
+ "count": 2,
+ "time_window": 60,
+ "rejected_code": 429
+ }
+ ]
+ ]
+ }
+ ]
+ }
+ },
+ "upstream": {
+ "type": "roundrobin",
+ "nodes": {
+ "127.0.0.1:1980": 1
+ }
+ }
+}'
+```
+
+For example, perform a specific action when condition A is true, perform
another action when condition B is true, etc. In this way, users can schedule
various business traffic more conveniently.
+
+## Summary
+
+APISIX has grown a lot from the beginning to the upcoming 3.0 version.
However, APISIX has not changed much in architecture but more in ecology,
compatibility, and product application.
+
+An open source project may not be judged solely on performance and
functionality but on the perspective of users, developers, and enterprises to
consider whether they can use the product to solve their current pain points
quickly and effectively.
+
+The highlights and new features mentioned in this article are all created
through the open source community, receiving feedback from different developers
and enterprise users, making open source products more useful and vibrant.
+
+Finally, APISIX 3.0 is expected to be released later this year, and we can
look forward to a lot of technical excitement with the new version!
diff --git a/blog/en/config/picked-posts.json b/blog/en/config/picked-posts.json
index be7777154c8..e311c693876 100644
--- a/blog/en/config/picked-posts.json
+++ b/blog/en/config/picked-posts.json
@@ -1,4 +1,5 @@
[
+ "blog/en/blog/2022/09/21/apache-apisix-v3-preview.md",
"blog/en/blog/2022/09/13/why-is-apache-apisix-the-best-api-gateway.md",
"blog/en/blog/2021/06/28/why-we-need-Apache-APISIX.md",
"blog/en/blog/2022/07/06/use-keycloak-with-api-gateway-to-secure-apis.md",
