ngaut

72 ms·

1. 781.▲
   by ngaut 9y ago

   Almost there.
2. 782.▲
   How-to: Sanitize your Rust code(github.com)

   4 points by ngaut 10y ago|0 comments
3. 783.▲
   by ngaut 10y ago

   If the clock offset is too high (more than 250ms), we should use another transaction model, Google Percolator is a good fit before the unforeseeable improvement in the hardware. Based on the monitoring of clock offset on cloud, TiDB chose t
4. 784.▲
   A Lightweight, Elasticsearch-Compatible Search Server. Built on RocksDB and Rust(github.com)

   4 points by ngaut 10y ago|0 comments
5. 785.▲
   Boson:A C++14 framework for asynchronous I/O, and green threads scheduling(github.com)

   1 points by ngaut 10y ago|0 comments
6. 786.▲
   by ngaut 10y ago

   RocksDB is widely used in many of projects for years, i think it's quite mature. Not just TiDB and CockroachDB, MyRocks and MongoRocks are using RocksDB as storage engine too. Also there are plenty of other projects are using RocksDB.
7. 787.▲
   by ngaut 10y ago

   Thank you,We are still working on the next RC release.
8. 788.▲
   by ngaut 10y ago

   Yes, it does. Thanks to MVCC, TiDB supports the repeatable read isolation level which guarantees that any data read cannot change, if the transaction reads the same data again, it will find the previously read data in place, unchanged, and
9. 789.▲
   by ngaut 10y ago

   Hi, TiDB maps SQL table to K/V table and store the SQL table to K/V store(TiDB store these K/V to TiKV), Please see https://pingcap.github.io/blog/2016/10/17/how-we-build-tidb/
10. 790.▲
    by ngaut 10y ago

    (TiDB developer here) Actually we are using RPC to call Rust from go, and it has nothing to do with Go or Rust, because either way we have to do RPC call(by encoding and decoding data), currently we depend on protocol buffer and customized
11. 791.▲
    by ngaut 10y ago

    There are lots of other differences. The default distributed storage engine of TiDB is TiKV, and TiKV is written is Rust. The transaction mode is different, and so on. The are something similar are they are both NewSQL, both use Raft to rep
12. 792.▲
    by ngaut 11y ago

    Thanks. swingbach.
13. 793.▲
    by ngaut 11y ago

    The goal of TiDB is to create fault-tolerant distributed RDBMS. Especially for distributed transaction support. Let developers get benefits without changing any of their existing code.
14. 794.▲
    by ngaut 11y ago

    Yes, currently TiDB works well with HBase. Coming soon. There are alse some distribute transaction layer on HBase.Ex: https://github.com/XiaoMi/themis
15. 795.▲
    by ngaut 11y ago

    PostgreSQL support is on our roadmap. https://github.com/pingcap/tidb/blob/master/ROADMAP.md
16. 796.▲
    by ngaut 12y ago

    cool