flypiggyyoyoyo commented on PR #838: URL: https://github.com/apache/incubator-seata-go/pull/838#issuecomment-2962702573
> Is the content of the core package less after decomposition? Is it necessary to eliminate the core package and decompose it again? Yes, the vast majority of the logic in the previous core package has been extracted. In fact, the logic corresponding to the Go version's current core package is implemented in different packages under the engine package in the Java version - the Java version does not have a core package. My original design intention was to minimize modifications to the original architecture while ensuring the store layer is separated and all circular dependencies are resolved - hence I did not remove the core package. My thinking is that if we aim to minimize modifications to the original architecture, we should not remove it; if we need to align with the Java version's design as much as possible, it needs to be split. I am uncertain whether to decompose the core package. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
