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/03/01 01:44:35 UTC
[GitHub] [apisix] spacewander opened a new issue #6473: APISIX's V3 (2022) Roadmap
spacewander opened a new issue #6473:
URL: https://github.com/apache/apisix/issues/6473
### Issue description
We are going to release a new major version (V3) in 2022.
As a major version, we will remove deprecated fields, bring break
changes, and most importantly, add great features.
We are going to make APISIX easier to adopt:
1. redesign documentation
2. refactor the backend of Dashboard. Now, this backend will talk with
Admin API instead of etcd.
3. refactor the API definition in Admin API, so that it can match the
backend of Dashboard.
4. support different backend as the source of configuration instead of
etcd.
5. move some features to CP side.
6. smarter way to diagnose runtime issues. Probably a builtin plugin?
7. Connect to etcd via gRPC and reduce the number of etcd connection
8. declarative configuration like what we have done in apisix-ingress (a better implementation of standalone mode or Admin API can sync
configuration in file to etcd)
We are going to make APISIX connect to more ecosystems:
1. integrate with more Open Source projects
2. integrate with cloud vendors
3. integrate with OpenAPI spec and other API spec definitions
4. write plugin without Lua, in the traditional way (Plugin Runner) or
the modern way (Wasm)
5. native gRPC support as a client, so we can connect to further places
We are going to make APISIX proxy everything:
1. xRPC: an L4 proxy framework to provide wire-level observability of
databases & message queue & RPC.
And more L4 observability: Prometheus & logger in the L4 level.
2. support XDS so APISIX can be used as the DP of istio
--
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] moonming commented on issue #6473: APISIX's V3 (2022) Roadmap
Posted by GitBox <gi...@apache.org>.
moonming commented on issue #6473:
URL: https://github.com/apache/apisix/issues/6473#issuecomment-1055055663
> 4. support different backend，support consul，mysql？
yes
--
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] spacewander commented on issue #6473: APISIX's V3 (2022) Roadmap
Posted by GitBox <gi...@apache.org>.
spacewander commented on issue #6473:
URL: https://github.com/apache/apisix/issues/6473#issuecomment-1056849851
> apisix 2.11 是否能够无缝切换到3版本？
There will be many break changes so we can't do it.
--
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] kwanhur commented on issue #6473: APISIX's V3 (2022) Roadmap
Posted by GitBox <gi...@apache.org>.
kwanhur commented on issue #6473:
URL: https://github.com/apache/apisix/issues/6473#issuecomment-1055606966
2. backend will talk with Admin API, `apisix-adminctl` or `apisixctl` will come into the plan together?
--
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] spacewander commented on issue #6473: APISIX's V3 (2022) Roadmap
Posted by GitBox <gi...@apache.org>.
spacewander commented on issue #6473:
URL: https://github.com/apache/apisix/issues/6473#issuecomment-1058923714
Let's freeze this issue.
--
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] kwanhur commented on issue #6473: APISIX's V3 (2022) Roadmap
Posted by GitBox <gi...@apache.org>.
kwanhur commented on issue #6473:
URL: https://github.com/apache/apisix/issues/6473#issuecomment-1056317822
> > 2. backend will talk with Admin API, `apisix-adminctl` or `apisixctl` will come into the plan together?
>
> The full sentence is
>
> > 2. refactor the backend of Dashboard. Now, this backend will talk with
> > Admin API instead of etcd.
>
> `this backend` means the Dashboard's backend.
[apisix-dashboard#1884](https://github.com/apache/apisix-dashboard/issues/1884) discussion mentioned that uniformed data model for Dashboard's backend and command line's backend. So take some care of the both backends.
--
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] moonming commented on issue #6473: APISIX's V3 (2022) Roadmap
Posted by GitBox <gi...@apache.org>.
moonming commented on issue #6473:
URL: https://github.com/apache/apisix/issues/6473#issuecomment-1054961541
looking forward to service mesh of Apache APISIX
--
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] Horus-K commented on issue #6473: APISIX's V3 (2022) Roadmap
Posted by GitBox <gi...@apache.org>.
Horus-K commented on issue #6473:
URL: https://github.com/apache/apisix/issues/6473#issuecomment-1056447563
apisix 2.11 是否能够无缝切换到3版本？
--
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] lizj3624 commented on issue #6473: APISIX's V3 (2022) Roadmap
Posted by GitBox <gi...@apache.org>.
lizj3624 commented on issue #6473:
URL: https://github.com/apache/apisix/issues/6473#issuecomment-1055052155
4. support different backend，support consul，mysql？
--
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] spacewander commented on issue #6473: APISIX's V3 (2022) Roadmap
Posted by GitBox <gi...@apache.org>.
spacewander commented on issue #6473:
URL: https://github.com/apache/apisix/issues/6473#issuecomment-1056897831
> > > 2. backend will talk with Admin API, `apisix-adminctl` or `apisixctl` will come into the plan together?
> >
> >
> > The full sentence is
> > > 2. refactor the backend of Dashboard. Now, this backend will talk with
> > > Admin API instead of etcd.
> >
> >
> > `this backend` means the Dashboard's backend.
>
> [apisix-dashboard#1884](https://github.com/apache/apisix-dashboard/issues/1884) discussion mentioned that uniformed data model for Dashboard's backend and command line's backend. So take some care of the both backends.
This purpose is marked as stale.
--
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] wang-yeliang commented on issue #6473: APISIX's V3 (2022) Roadmap
Posted by GitBox <gi...@apache.org>.
wang-yeliang commented on issue #6473:
URL: https://github.com/apache/apisix/issues/6473#issuecomment-1056126859
Look forward to Service Mesh.
罗泽轩 ***@***.***> 于2022年3月1日周二 09:44写道：
> Issue description
>
> We are going to release a new major version (V3) in 2022.
> As a major version, we will remove deprecated fields, bring break
> changes, and most importantly, add great features.
>
> We are going to make APISIX easier to adopt:
>
> 1. redesign documentation
> 2. refactor the backend of Dashboard. Now, this backend will talk with
> Admin API instead of etcd.
> 3. refactor the API definition in Admin API, so that it can match the
> backend of Dashboard.
> 4. support different backend as the source of configuration instead of
> etcd.
> 5. move some features to CP side.
> 6. smarter way to diagnose runtime issues. Probably a builtin plugin?
> 7. Connect to etcd via gRPC and reduce the number of etcd connection
> 8. declarative configuration like what we have done in apisix-ingress
> (a better implementation of standalone mode or Admin API can sync
> configuration in file to etcd)
>
> We are going to make APISIX connect to more ecosystems:
>
> 1. integrate with more Open Source projects
> 2. integrate with cloud vendors
> 3. integrate with OpenAPI spec and other API spec definitions
> 4. write plugin without Lua, in the traditional way (Plugin Runner) or
> the modern way (Wasm)
> 5. native gRPC support as a client, so we can connect to further places
>
> We are going to make APISIX proxy everything:
>
> 1. xRPC: an L4 proxy framework to provide wire-level observability of
> databases & message queue & RPC.
> And more L4 observability: Prometheus & logger in the L4 level.
> 2. support XDS so APISIX can be used as the DP of istio
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/apisix/issues/6473>, or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AEXXFGMEDDSWW5R2BCI6ZUDU5VZBHANCNFSM5PSVWNMQ>
> .
> Triage notifications on the go with GitHub Mobile for iOS
> <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
> or Android
> <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
>
> You are receiving this because you are subscribed to this thread.Message
> ID: ***@***.***>
>
--
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] spacewander commented on issue #6473: APISIX's V3 (2022) Roadmap
Posted by GitBox <gi...@apache.org>.
spacewander commented on issue #6473:
URL: https://github.com/apache/apisix/issues/6473#issuecomment-1056054052
> 2. backend will talk with Admin API, `apisix-adminctl` or `apisixctl` will come into the plan together?
The full sentence is
> 2. refactor the backend of Dashboard. Now, this backend will talk with
Admin API instead of etcd.
`this backend` means the Dashboard's backend.
--
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