GitHub user CAICAIIs created a discussion: [DISCUSS] [GSoC 2026] Proposal on Seata-Go multi-registry support and seata-ctl diagnostics
Dear Seata community, My name is Xuwei Yang (GitHub: CAICAIIs). I have submitted a GSoC 2026 proposal for Apache Seata on improving Seata-Go multi-registry support and enhancing seata-ctl diagnostic capability, and I would like to briefly introduce the idea here. >From my recent reading of the Seata-Go, Seata Java, and seata-ctl codebases, >my understanding is that Seata-Go still has a clear gap with the Java side in >registry support, while the current diagnostic tooling on the Go side is also >still limited. In practice, this makes it harder to use Seata-Go in >environments that already depend on registries such as Nacos or ZooKeeper, and >it also increases the cost of troubleshooting distributed transaction issues. My proposal is to approach this work incrementally. On the Seata-Go side, I plan to first improve the shared registry foundation, then prioritize Nacos and ZooKeeper support, followed by Consul and Redis. On the seata-ctl side, I plan to focus on a practical diagnostic baseline first, including environment checks, transaction inspection, and lock inspection, and then continue with further improvements if time allows. I have recently been contributing in Seata-Go and related Go middleware projects, and I also did some local prototype and code reading work while preparing this proposal. Please find the attached proposal PDF for more details. I would greatly appreciate any feedback from the community on the scope and priorities of this topic. [CAICAIIsSeataGoMultiRegistryAndSeataCtl.pdf](https://github.com/user-attachments/files/26774467/CAICAIIsSeataGoMultiRegistryAndSeataCtl.pdf) Best regards, Xuwei Yang GitHub: CAICAIIs Time zone: Asia/Shanghai (UTC+8) GitHub link: https://github.com/apache/incubator-seata-go/discussions/1108 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
