wescale
wescale copied to clipboard
wesql
WeScale is a Modern MySQL proxy that supports read-write-split, read-after-write-consistency, load balancing and OnlineDDL.
## Related Issue(s) & Descriptions ## Checklist - [x] Tests were added or are not required - [x] Documentation was added or is not required
## Related Issue(s) & Descriptions ## Checklist - [x] Tests were added or are not required - [x] Documentation was added or is not required
# Background Currently, the go module name for the project is not aligned with the GitHub repository URL. This mismatch can cause confusion and make it harder for users to...
# Background The current implementation of the read_after_write consistency feature in the system relies on waiting for the execution of the last global transaction identifier (GTID), indiscriminately applying this method...
# Background Vertical Split is a valuable functionality for database management. It involves splitting a database into multiple components for improved scalability and performance. A typical Vertical Split process involves...
# Background In the current branch feature, users can choose whether to continuously synchronize data from source database for all tables during the preparation phase. However, this approach is not...
# Background The current 'Branch Prepare' command copies unnecessary data when creating a database branch. # Proposal Add a new 'Branch Create' command that creates a branch without copying data.
# Background Currently, the `schemadiff` feature of the branch can compare whether the `source_branch` and `target_branch` in a certain workflow are the same. If they are different, it will print...
# Background WeScale's non-transactional Data Manipulation Language (DML) functionality is a powerful feature that allows users to perform data modifications outside of transactional boundaries. However, there is currently a lack...
# Background WeScale currently stores its system tables, which are used to record metadata such as the schema_migrations table required by OnlineDDL, in the 'mysql' database. The question is whether...