| 1. Regarding performance, I recently did a simple test. CockroachDB uses a considerable number of CPU instructions compared to YugabyteDB: https://dev.to/yugabyte/comparing-sql-engines-by-cpu-instruc... Writing a database from scratch is not easy. YugabyteDB uses some PostgreSQL, Kudu, and RocksDB code that has been heavily optimized before. Those are good codebases, and only some parts need to be enhanced to make them distributed. 2. Their Go version of RocksDB, Peeble, seems less efficient. They did it for a good reason. They didn't have the C++ skills to enhance RocksDB itself. 3. The repo holds more than the database. C: is the SQL layer, based on PostgreSQL C++: the transactional distributed storage, heavily modified Kudu and RocksDB Java: some regression tests, the managed service automation, sample applications TS: the Graphical User Interface Python: some tooling to build the releases, some support tools The database itself is C and C++ |