youngyjd commented on issue #10472: URL: https://github.com/apache/gravitino/issues/10472#issuecomment-4087992969
@yuqi1129 I agree with the points about middleware. Let's put this effort on hold. I will first align with our internal Mysql offerings. Our setup today looks like this: 1. Old MySQL – No proxy; classic primary + replicas. This is what we use today for the entity store. The “separate read/write JDBC” approach would apply here, but we’re pausing that until we’ve decided how we want to handle read splitting long term. 2. New MySQL – We have Vitess, introduced last year to the company. There seem to be some constraints or integration details we need to understand before we can rely on it for the Gravitino entity store. We’ll revisit once we’ve clarified those options and can say whether we need app-level read/write endpoints or can rely on middleware. Thanks for the pointers to Mycat, ShardingSphere, and Vitess. -- 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]
