I wonder how this compares to Vitess, which youtube has been using to scale their MySql databases for years.<p>Which is also written in Go.<p>Perhaps this is a direct competitor to Vitess, but I agree the description is in dire need of some specifics.<p>Edit: adding link
<a href="https://github.com/youtube/vitess" rel="nofollow">https://github.com/youtube/vitess</a>
This sounds a lot like mysql proxy (<a href="http://dev.mysql.com/doc/refman/5.7/en/mysql-proxy.html" rel="nofollow">http://dev.mysql.com/doc/refman/5.7/en/mysql-proxy.html</a>), which afaik is not recommended for production use.<p>I would very much like to know what the differences are (apart from the choice of programming language) and how stable this is.
I think you have to improve the description: "aims to supply a simple solution for using MySQL." doesn't really make sense, because I can just use MySQL directly.<p>Is this some kind of connection pool / load balancer?
What I would really love to see in a solution like this is the ability to automatically rebalance shards (like moving data between shards when adding new instances).<p>Sharding can be achieved quite easily on the application level, or by using one of the few available proxies. On the other hand, re-balancing is not easily done yet.
There's lots of development in this space all of the sudden. From Oracle there is also MySQL Fabric.<p>Fabric also provides sharding + failover, but does so by using modified MySQL connectors rather than a proxy.