A modern MySQL proxy with read-write splitting, read-after-write consistency, load balancing, and OnlineDDL.
WeScale is a modern MySQL proxy that acts as a bridge between applications and MySQL databases. It provides essential features like read-write splitting, load balancing, and OnlineDDL to simplify database scaling and management. The project aims to enhance developer productivity by handling complex database operations transparently.
Application developers and DevOps engineers managing MySQL databases who need to improve performance, scalability, and availability without modifying application code.
Developers choose WeScale for its comprehensive feature set focused on developer experience, including declarative DDL and transaction chopping. Its ability to provide read-after-write consistency and seamless failover makes it a robust alternative to manual database middleware solutions.
WeScale is a Modern MySQL proxy that supports read-write-split, read-after-write-consistency, load balancing and OnlineDDL.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Enables defining desired table states with automatic incremental changes, simplifying migrations as shown in the SQL example for adding columns and indexes.
Supports OnlineDDL for schema changes and transparent failover, reducing maintenance windows and application disruption during database failures.
Provides read-after-write consistency, ensuring immediate visibility of writes in subsequent reads without requiring application code changes.
Allows custom logic integration through WebAssembly plugins, offering flexibility for query filtering and transformation based on the tutorial documentation.
Exclusively supports MySQL databases, making it unsuitable for projects using PostgreSQL, MongoDB, or other database systems.
Requires Docker or Kubernetes for setup, as shown in the getting started guide, which can be cumbersome compared to lightweight or embedded proxies.
As a newer fork of Vitess, it has a smaller community and fewer third-party integrations, which might affect tooling and support availability.
Adds an extra network layer that can introduce latency, though the performance blog notes optimizations; this is a trade-off for advanced features.