nacos
nacos copied to clipboard
What features do you expect from Nacos 3.0?
What features do you expect from Nacos 3.0?
Read write separation? Flow control? Support DNS Server /XDS Server? Gateway integration(Tengine / Nginx)? Multi language(Rust / Dapr)? Tools(Benchmarks / CLI )? Improve consistency agreement? Rich Metrics? arm cpu? ipv6? dragonwell + jdk 11? oceanbase / PG ? Document? UT/IT?
Please update the documentation!
1、鉴权支持到Group级别的插件实现 2、分布式锁插件实现 想起来更多的再补充。。。。。。。
Read/Write Splitting
Multi language(Rust / Dapr)➕ 1⃣️
Rust 版客户端,申请参与,个人空余时间在写 Nacos2.x 的 grpc 交互客户端,期望后续基本完备后可以并入 nacos-group
支持从K8S的ConfigMap中,实时地拉取数据,并同步数据到Nacos配置中心 该Feature欢迎这里讨论:https://github.com/alibaba/nacos/issues/9134
Multi language(Rust / Dapr)➕ 1⃣️
Rust 版客户端,申请参与,个人空余时间在写 Nacos2.x 的 grpc 交互客户端,期望后续基本完备后可以并入 nacos-group
看起来不错哦
支持按组监听配置 解决的问题主要是: 客户端想监听某个一组下面的配置 比如 data_id为 nacos.common开头 group为 product开头的所有配置 当满足这个条件的配置发生了 新增 修改 删除 可以通知到客户端 (社区看看是否感兴趣 我们已经做了一套实现)
Please update the documentation!
Couldn't agree more, the NACOS documentation is poor
个人空余时间在写 Nacos2.x 的 grpc 交互客户端
大佬带带我
大佬带带我 @onewe 大佬请一起来参与玩玩,Rust 太难上手了,几个月了现在终于有点儿上道。
@CherishCai 😂, 我花了一个月时间, rust 入了个旋转门.
支持按组监听配置 解决的问题主要是: 客户端想监听某个一组下面的配置 比如 data_id为 nacos.common开头 group为 product开头的所有配置 当满足这个条件的配置发生了 新增 修改 删除 可以通知到客户端 (社区看看是否感兴趣 我们已经做了一套实现)
建议很不错,这个社区有很多朋友也有类似需求
Support DNS Server
支持按组监听配置 解决的问题主要是: 客户端想监听某个一组下面的配置 比如 data_id为 nacos.common开头 group为 product开头的所有配置 当满足这个条件的配置发生了 新增 修改 删除 可以通知到客户端 (社区看看是否感兴趣 我们已经做了一套实现)
建议很不错,这个社区有很多朋友也有类似需求,可以考虑开一个ISSUE来搞哦
https://github.com/alibaba/nacos/issues/9146 先建个issue 稍后几天 我将目前实现的思路和细节贴上来 然后讨论下适合社区发展的思路
支持按组监听配置 解决的问题主要是: 客户端想监听某个一组下面的配置 比如 data_id为 nacos.common开头 group为 product开头的所有配置 当满足这个条件的配置发生了 新增 修改 删除 可以通知到客户端 (社区看看是否感兴趣 我们已经做了一套实现)
建议很不错,这个社区有很多朋友也有类似需求,可以考虑开一个ISSUE来搞哦
#9146 先建个issue 稍后几天 我将目前实现的思路和细节贴上来 然后讨论下适合社区发展的思路
目前先进行需求收集,还没有决定是否落地实现,等到时候再提新issue提方案吧。
支持按组监听配置 解决的问题主要是: 客户端想监听某个一组下面的配置 比如 data_id为 nacos.common开头 group为 product开头的所有配置 当满足这个条件的配置发生了 新增 修改 删除 可以通知到客户端 (社区看看是否感兴趣 我们已经做了一套实现)
建议很不错,这个社区有很多朋友也有类似需求,可以考虑开一个ISSUE来搞哦
#9146 先建个issue 稍后几天 我将目前实现的思路和细节贴上来 然后讨论下适合社区发展的思路
目前先进行需求收集,还没有决定是否落地实现,等到时候再提新issue提方案吧。
ok 如果最终有这方面诉求 可以@我
Hello, I'm a user of nacos. Currently, ShardingSphere mainly uses Zookeeper and Etcd as the configuration center. ShardingSphere also expects to complete the integration of Nacos and use its configuration center to complete the subscription and publication of configured CURDs and events to complete the sharing and synchronization of status and rules in cluster mode.
But I'm currently stuck with the following features that haven't been supported yet
- Support getting configuration according to the dataId prefix range, and return dataId, group, content.
- Support publish ephemeral configuration which is deleted when the session is disconnected.
- Support range watch, the callback parameter contains the configuration that matches the dataId prefix.
- Support the listener callback parameter contains more information, such as the value before the configuration change, the value after the configuration change, and the configuration change type.
- Support deleting configurations according to the dataId prefix range.
- Support distributed locks. The data of the nacos is persistent in the database. It should be possible to implement distributed locks based on the database.
I expect nacos have these features.
Thanks.
Hello, I'm a user of nacos. Currently, ShardingSphere mainly uses Zookeeper and Etcd as the configuration center. ShardingSphere also expects to complete the integration of Nacos and use its configuration center to complete the subscription and publication of configured CURDs and events to complete the sharing and synchronization of status and rules in cluster mode.
But I'm currently stuck with the following features that haven't been supported yet
- Support getting configuration according to the dataId prefix range, and return dataId, group, content.
- Support publish ephemeral configuration which is deleted when the session is disconnected.
- Support range watch, the callback parameter contains the configuration that matches the dataId prefix.
- Support the listener callback parameter contains more information, such as the value before the configuration change, the value after the configuration change, and the configuration change type.
- Support deleting configurations according to the dataId prefix range.
- Support distributed locks. The data of the nacos is persistent in the database. It should be possible to implement distributed locks based on the database.
I expect nacos have these features.
Thanks.
#9262
很多用户升级时都会担心新版本不稳定,再加上Nacos更新迭代很快,期望提升UT/IT/ST能力
nacos客户端失败重连机制,现在nacos客户端连接失败后不会进行重试,在k8s部署时存在服务比nacos-server先启动的情况,这是肯定连接不上nacos-server,现在是连接抛出异常后就不会进行连接了,这样导致的问题很严重,觉得nacos客户端有必要加上失败重试的机制
建议紧跟spring步伐
建议紧跟spring步伐
支持+1
建议适配 SpringBoot 3.0
So do we currently have a list of things to do with nacos3.0?
Increase observability
加我一个 期望增加Arm支持!
配置抽取成配置类,like ConfigurationProperties.
In my opinion, the gateway integration is very important.
配置乱七八糟的,一会取vm配置,一会spring配置文件里的配置
Support DNS Server