siddontang

TiDB provides many some ways to let the deployment easier. If you just want to have a try on the single machine, we provide docker-compose (https://github.com/pingcap/tidb-docker-compose). But if you don't like docker, the single binary may be easier.

For the business users, we support ansible and K8s deployment, both can help them run the TiDB easily and quickly in production. The deployment is not a problem so far.

IMO, for the distributed system, if you need to operate many instances (10, 100 or even more), what you pay attention to most is not whether the instance is one single binary or not, but is how to operate all these easily. At that time, there is no much difference.

Siddon Tang from TiDB here. Thanks for your interest in TiDB! TiDB uses Snapshot Isolation (https://en.wikipedia.org/wiki/Snapshot_isolation), which is similar to Repeated Read in MySQL. It doesn’t allow Read Phantom but can’t avoid Write Skew. IMO, this can work well for OLTP in most of the cases. If you really care about serializability, you can use `select for update` to promote the Read as Write explicitly like other databases do.

TiDB supports READ COMMITTED isolation which is not the same as MySQL, but it is just designed for some special cases for TiDB itself and it is not recommended for external users.

Hi @anishathalye, thanks for your https://github.com/anishathalye/porcupine. It’s a great project! Would you like to help me to check whether our model check is right or not with Porcupine? That would be highly appreciated!

Now I only see Vitess can support resharding with some restrictions, maybe I am ignorant.

I don't think handing sharding on the application level is easy, programmers may care too much about MySQL sharding and can not write sql easily, at least in my company.

I have only used Atlas (https://github.com/Qihoo360/Atlas) and cobar (https://github.com/alibaba/cobar), but they are not suitable for my company, so I want to develop a simple one using Go.

Auto resharding is very awesome but I don't have the power to do that now. Any help is very welcome.

Well, support cross sharding `join`, `subslect` and `group by` is not easy, I see Vitess does not fully support them now.

I am the only guy to develop Mixer just for fun with little time, and have to improve it step by step. Any help is welcome.

Btw, I have not used MongoDB, I will try to see it later.

Sorry, only Chinese document. The authors may only focus Chinese MySQL users.

Btw, writing english document is very hard for many Chinese programmers, the same to me:)

There is no best solution for MySQL sharding at all, so many people develop the proxy for their real scenario.

Maybe MySQL Fabric is a silver bullet, but I always think that sometimes proxy is enough.

Well, I put many limitations now only to get proxy working right first. I need to improve it step by step.

I am very glad that if anyone can help me. Many things to do but I have not enough time.

Sorry for my bad expression, Mix aims to solve some simple MySQL sharding problems. I should improve the document first, maybe:)

Mixer is more like Atlas(https://github.com/Qihoo360/Atlas) or Cobar(https://github.com/alibaba/cobar).

You can define some rules to route sql to different MySQL servers, maybe it is the main difference.

Mixer can not be used in production now, I have been improving it and try to use it in my company first.

Vitess is too huge for me, I can't fully understand it.

I don't think mixer can be the direct competitor to Vitess.I develop it just for fun and only want to solve some simple MySQL sharding problems.

Btw, Vitess is awesome and I use some codes from it.