APISIX's V3 (2022) Roadmap

[spacewander]

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

[moonming]

looking forward to service mesh of Apache APISIX

[lizj3624]

4. support different backend，support consul，mysql？

[moonming]

4. support different backend，support consul，mysql？

yes

[kwanhur]

2. backend will talk with Admin API, apisix-adminctl or apisixctl will come into the plan together?

[spacewander]

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.

[wang-yeliang]

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: @.***>

[kwanhur]

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 discussion mentioned that uniformed data model for Dashboard's backend and command line's backend. So take some care of the both backends.

[Horus-K]

apisix 2.11 是否能够无缝切换到3版本？

[spacewander]

apisix 2.11 是否能够无缝切换到3版本？

There will be many break changes so we can't do it.

[spacewander]

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 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.

[spacewander]

Let's freeze this issue.

[wolgod]

2.15 is the last big version of 2.x this year?

[spacewander]

2.15 will be the biggest minor version of 2.x.

[Nobilta]

if apisix v3 can support multi cluster of k8s'discovery?

[spacewander]

if apisix v3 can support multi cluster of k8s'discovery?

It's not in the roadmap.

[Nobilta]

if apisix v3 can support multi cluster of k8s'discovery?

It's not in the roadmap.

fine,when we can use apisix v3 and what's the shecdule?the connection to etcd with gRPC is necessary.

[tokers]

if apisix v3 can support multi cluster of k8s'discovery?

It's not in the roadmap.

fine,when we can use apisix v3 and what's the shecdule?the connection to etcd with gRPC is necessary.

The first rc version should be available at the end of this month.

[github-actions[bot]]

This issue has been marked as stale due to 350 days of inactivity. It will be closed in 2 weeks if no further activity occurs. If this issue is still relevant, please simply write any comment. Even if closed, you can still revive the issue at any time or discuss it on the [email protected] list. Thank you for your contributions.

[github-actions[bot]]

This issue has been closed due to lack of activity. If you think that is incorrect, or the issue requires additional review, you can revive the issue at any time.