terrymanu opened a new issue #12273: URL: https://github.com/apache/shardingsphere/issues/12273
The current events publish and subscribe process is too complicated, the chains are too deep. There are:  The disadvantages are: 1. Only cluster mode can support primary data source change. 2. Call chains are too deep, and there are lots of async subscribe, hard to understander. It is better to redesign like this way.  The benefits are: 1. Support primary data source change for every modes. 2. Redesign call chains, no lots of async subscribe. The disadvantages are adding more complex of event publish logic: 1. Need to check same governance instance before persist to registry repository. 2. Need to check different governance instances before event post. The tasks for complete the design are: - [ ] Design event source tracing for post; - [ ] Split ContextManagerBuilder for build one time only and put renew into coordinator; - [ ] Add ContextManagerHook via SPI; - [ ] Add governance instance judge for persist registry repository; - [ ] Update ContextManager for all modes. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
