royguo1988

7 ms·

1. 1.▲
   by royguo1988 6y ago

   This is wired, I will call our internal Lark team to deal with it.
2. 2.▲
   by royguo1988 6y ago

   Sorry for the unclear response. 1) We use TerarkDB under a distributed SQL database and TerarkDB helps to store its pages (16KB page), its one of the most widely used SQL database inside Bytedance. 2) We use TerarkDB under a Redis compatibl
3. 3.▲
   by royguo1988 6y ago

   In bytedance, a few database services are using TerarkDB.
4. 4.▲
   by royguo1988 6y ago

   All source code is open source now. You can find them in `third-party/terark-zip`, terark-zip is a standalone repo that contains only core algorithms.
5. 5.▲
   by royguo1988 6y ago

   Thanks for your attention, glad someone here still remember our history, TerarkDB is now FULLY open source with `succinct data structures`. Here's the reasons: 1. Our `all-in-one` docs are still under writing, we will cover that part l
6. 6.▲
   by royguo1988 6y ago

   We didn't test the Java Binding for quick a long time, I am not sure if it can still compile the Java Binding well, please fill an issue on Github if you find it didn't work anymore, thanks! I remembered that we tried it on Flink
7. 7.▲
   by royguo1988 6y ago

   Thanks, tried to log-in & reset my password but didn't receive reset email.
8. 8.▲
   by royguo1988 6y ago

   We are working on our `all-in-one docs` right now, please watch our repo, thanks! I replied some of the reasons in previous comment.
9. 9.▲
   by royguo1988 6y ago

   The reasons we did a better job(from our own perspective) than RocksDB are: 1. We moved lots of code out side db_mutex (db mutex is convenient but costs too much) 2. We introduced a new KV separation implementation that we believe is better
10. 10.▲
    by royguo1988 6y ago

    We are working on our `all-in-one docs` which will explain everything. I want to address that we are not meant to "get rid of" RocksDB (which lots of KV engine claimed). What we want to do is provide another solution for storage e
11. 11.▲
    by royguo1988 6y ago

    Thanks for your suggestion, I will update the image soon
12. 12.▲
    by royguo1988 6y ago

    There are mainly three reasons here: 1. We changed the source code too much that we are not able to merge it back to RocksDB easily (This project started at 2016 as an close-source project) 2. We have different road path with RocksDB (e.g.
13. 13.▲
    TerarkDB, ByteDance's RocksDB replacement(github.com)

    168 points by royguo1988 6y ago|78 comments
14. 14.▲
    by royguo1988 6y ago

    TerarkDB was acquired by Bytedance two years ago and is now using widely in Bytedance's database services. I am one of the maintainers of this project you can ask any question here.