You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by GitBox <gi...@apache.org> on 2022/10/28 08:21:49 UTC
[GitHub] [apisix-website] EmilyKeer opened a new pull request, #1382: Update Apache APISIX 3.0 blog
EmilyKeer opened a new pull request, #1382:
URL: https://github.com/apache/apisix-website/pull/1382
Update the Apache APISIX 3.0 blog after syncing with R&D; this updated article is meant to be published on 10.31
--
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
[GitHub] [apisix-website] guoqqqi commented on pull request #1382: Update Apache APISIX 3.0 blog
Posted by GitBox <gi...@apache.org>.
guoqqqi commented on PR #1382:
URL: https://github.com/apache/apisix-website/pull/1382#issuecomment-1299577239
> > Need to add a redirect link?
>
> @guoqqqi Can you help me to do that?
OK, already updated
--
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
[GitHub] [apisix-website] netlify[bot] commented on pull request #1382: Update Apache APISIX 3.0 blog
Posted by GitBox <gi...@apache.org>.
netlify[bot] commented on PR #1382:
URL: https://github.com/apache/apisix-website/pull/1382#issuecomment-1294678048
### <span aria-hidden="true">👷</span> Deploy Preview for *apache-apisix* processing.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | d57c5224c264ae04332270851bc37f5e99accb0e |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/sites/apache-apisix/deploys/635b911d36b02d000969363a |
--
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
[GitHub] [apisix-website] EmilyKeer commented on pull request #1382: Update Apache APISIX 3.0 blog
Posted by GitBox <gi...@apache.org>.
EmilyKeer commented on PR #1382:
URL: https://github.com/apache/apisix-website/pull/1382#issuecomment-1299551759
> Need to add a redirect link?
@guoqqqi Can you help me to do that?
--
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
[GitHub] [apisix-website] hf400159 commented on pull request #1382: Update Apache APISIX 3.0 blog
Posted by GitBox <gi...@apache.org>.
hf400159 commented on PR #1382:
URL: https://github.com/apache/apisix-website/pull/1382#issuecomment-1296252037
Need to add a redirect link?
--
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
[GitHub] [apisix-website] juzhiyuan commented on pull request #1382: Update Apache APISIX 3.0 blog
Posted by GitBox <gi...@apache.org>.
juzhiyuan commented on PR #1382:
URL: https://github.com/apache/apisix-website/pull/1382#issuecomment-1296254770
Wait for 3.0 release.
--
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
[GitHub] [apisix-website] EmilyKeer commented on a diff in pull request #1382: Update Apache APISIX 3.0 blog
Posted by GitBox <gi...@apache.org>.
EmilyKeer commented on code in PR #1382:
URL: https://github.com/apache/apisix-website/pull/1382#discussion_r1007791954
##########
blog/en/blog/2022/10/31/apache-apisix-v3-preview.md:
##########
@@ -40,93 +36,88 @@ But just solving these problems is not enough. As a middleware with requests fro
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 can communicate through local RPC to develop APISIX plugins using the programming languages they are familiar with.
-
-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
+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.
Review Comment:
Update: removed in-depth details so that the audience can quickly jump to the core part of the article
--
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
[GitHub] [apisix-website] juzhiyuan merged pull request #1382: Update Apache APISIX 3.0 blog
Posted by GitBox <gi...@apache.org>.
juzhiyuan merged PR #1382:
URL: https://github.com/apache/apisix-website/pull/1382
--
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