3 ms·

Why not TiDB ?

• sanxiyn 8y ago
  FYI: TiDB is relevant because it is distributed and protocol-compatible with MySQL.
  • elvinyung 8y ago
    I think at this point it's basically a non-option though. Ti is nowhere near mature enough, the ops investment cost is extremely nontrivial, and it and still has some interesting issues to work out (e.g. [1]). Furthermore, protocol-compatible doesn't directly imply API-compatible (I'm thinking of very very subtle differences between things like datatypes or isolation level behavior). I know a bit more about CockroachDB, which consciously does some things differently from Postgres. [1] https://github.com/pingcap/tidb/issues/2712 https://github.com/pingcap/tidb/issues/2712
    • sanxiyn 8y ago
      It's not a drop-in, but several very large websites migrated from MySQL to TiDB, so it definitely is an option.
      • Rafuino 8y ago
        Source? I'm guessing you're referring to Mobike and Yiguo... any others? https://www.pingcap.com/cases/ https://www.pingcap.com/cases/
        • sanxiyn 8y ago
          Those two are just case studis. There is a fuller list here: https://pingcap.com/docs/adopters/ https://pingcap.com/docs/adopters/
        • shenli3514 8y ago
          TiDB developer here. There are more than one hundred companies who use TiDB in their production environment. The number keeps growing. The link in sanxiyn's post shows part of them. I think it is safe to say that TiDB is mature enough.