11–20 of 30 posts
How does YugaByte compare to CockroachDB?
There's a feature matrix here [1] comparing YugaByte to CRDB, TiDB, Aurora, CosmosDB, Spanner, MongoDB, FoundationDB, Cassandra and Dynamo. No idea about performance characteristics though. [1] https://docs.yugabyte.com/latest/comparisons/ edit: there is a relatively recent blogpost comparing the two here: https://blog.yugabyte.com/yugabyte-db-vs-cockroachdb-perform... Key summary from the post: In a nutshell, YugaBy…
How does YugaByte compare to CockroachDB?
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/
Earlier quoted context omitted.
One way for YB to fight off the competition from AWS would be to include a clause that any forks of the DB should always be in sync with the upstream(master developed by YB), so hypothetically speaking this would mean companies that are using the AWS YB could always have the freedom to switch to using the OSS YB and only risk loosing the features that AWS has contributed to its fork and might actually force the OSS t…
(founder/cto of YugaByte) This is a very insightful suggestion, thanks for raising that! We had considered many of these variants until finally, we concluded that fully open is the best way. PostgreSQL (which is the database on fire right now) got to this spot by being fully open and permissive - and embracing all forms of competition. In fact, PostgreSQL got rewritten from Lisp to C (which begs an interesting questi…
Good intentions here, wish you guys the very best.
I think you mean it "raises the question". See: https://en.wikipedia.org/wiki/Begging_the_question Edit: To whomever downvoted this: care to justify your action?
I think you mean it "raises the question". See: https://en.wikipedia.org/wiki/Begging_the_question Edit: To whomever downvoted this: care to justify your action?
Earlier quoted context omitted.
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/
That comparison misses some things like "AS OF SYSTEM TIME" queries, changefeeds, and other CRDB-specific pieces.
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)
Earlier quoted context omitted.
One way for YB to fight off the competition from AWS would be to include a clause that any forks of the DB should always be in sync with the upstream(master developed by YB), so hypothetically speaking this would mean companies that are using the AWS YB could always have the freedom to switch to using the OSS YB and only risk loosing the features that AWS has contributed to its fork and might actually force the OSS t…
(founder/cto of YugaByte) This is a very insightful suggestion, thanks for raising that! We had considered many of these variants until finally, we concluded that fully open is the best way. PostgreSQL (which is the database on fire right now) got to this spot by being fully open and permissive - and embracing all forms of competition. In fact, PostgreSQL got rewritten from Lisp to C (which begs an interesting questi…
How does YugaByte compare to CockroachDB?
There's a feature matrix here [1] comparing YugaByte to CRDB, TiDB, Aurora, CosmosDB, Spanner, MongoDB, FoundationDB, Cassandra and Dynamo. No idea about performance characteristics though. [1] https://docs.yugabyte.com/latest/comparisons/ edit: there is a relatively recent blogpost comparing the two here: https://blog.yugabyte.com/yugabyte-db-vs-cockroachdb-perform... Key summary from the post: In a nutshell, YugaBy…
Best of luck with new licensing.
Earlier quoted context omitted.
There's a feature matrix here [1] comparing YugaByte to CRDB, TiDB, Aurora, CosmosDB, Spanner, MongoDB, FoundationDB, Cassandra and Dynamo. No idea about performance characteristics though. [1] https://docs.yugabyte.com/latest/comparisons/ edit: there is a relatively recent blogpost comparing the two here: https://blog.yugabyte.com/yugabyte-db-vs-cockroachdb-perform... Key summary from the post: In a nutshell, YugaBy…
Going to vendor's website always have comparisons that claims, it can do everything that the competitor's can not. What I'd also like to know is limitations. Where it's not a good idea to use a product? This would help me make informed decision and build relationship with vendor based on trust. Best of luck with new licensing.
This might help answer some of your questions: https://docs.yugabyte.com/latest/introduction/#what-are-the-...
Please look at the trade-offs in the above section (vs SQL, vs transactional NoSQL, vs eventually consistent NoSQL).
(founder/cto at YugaByte)
Earlier quoted context omitted.
One way for YB to fight off the competition from AWS would be to include a clause that any forks of the DB should always be in sync with the upstream(master developed by YB), so hypothetically speaking this would mean companies that are using the AWS YB could always have the freedom to switch to using the OSS YB and only risk loosing the features that AWS has contributed to its fork and might actually force the OSS t…
(founder/cto of YugaByte) This is a very insightful suggestion, thanks for raising that! We had considered many of these variants until finally, we concluded that fully open is the best way. PostgreSQL (which is the database on fire right now) got to this spot by being fully open and permissive - and embracing all forms of competition. In fact, PostgreSQL got rewritten from Lisp to C (which begs an interesting questi…
A) I can conveniently install it and work with it via apt, yum, dnf, etc. for free at home.
B) I trust that the product will remain alive as long as its interest and users are, not when funding runs out.
Who wants to put time into vaporware? I don't want to pay for it until I know it's good and that it'll be around. I don't think being hostile to AWS takeover with change adoption.