News for hackers. Stuff that matters.

A comment on We Changed YugaByte DB Licensing to Apache 2.0. Parent comment

Re:We Changed YugaByte DB Licensing to Apache 2.0 by sidch on Tuesday July 16, 2019 @05:42PM (#20454161)
YugaByte product manager here -- have documented the answer to your question [1] As you can see, there are many similarities but there are also a few important differences such as depth of PostgreSQL compatibility (YB reuses PostgreSQL query layer while CRDB is a re-implementation) and latency/throughput observed for modern OLTP workloads.

[1] https://docs.yugabyte.com/latest/comparisons/cockroachdb/

[ Parent | on HN ]
Re:We Changed YugaByte DB Licensing to Apache 2.0 by kodablah on Tuesday July 16, 2019 @06:28PM (#20454459)
That comparison misses some things like "AS OF SYSTEM TIME" queries, changefeeds, and other CRDB-specific pieces.
[ Parent | on HN ]
Re:We Changed YugaByte DB Licensing to Apache 2.0 by rkarthik007 on Tuesday July 16, 2019 @06:43PM (#20454579)
Hi @kodeblah,

True, but note that the comparison only focuses on SQL (as it related to PostgreSQL) features and not any DB-specific features.

The YugaByte DB specific pieces are not included as well - for example, support for YCQL (Cassandra-compatible) and YEDIS (Redis-compatible) APIs to the DB.

(disclosure: founder/cto at yugabyte)

[ Parent | on HN ]