For full disclosure, I've been in the Apache Cassandra community since 2010 and
at DataStax since 2012.
So DataStax moved on to focus on things for their customers, effectively
putting most development effort into DataStax Enterprise. However, there have
been a lot of fixes and improvements
It will (did) slow, but it didn’t (won’t) stop. There’s some really interesting
work in the queue, like
https://issues.apache.org/jira/plugins/servlet/mobile#issue/CASSANDRA-14404 ,
that should make a lot of users very happy.
--
Jeff Jirsa
> On Jul 19, 2018, at 6:59 AM, Vitaliy Semochkin
Jeff and Rahul thank you very much for clarification.
My main concern was the fact that since DataStax left Cassandra
project it is unclear if the development speed will significantly slow
down,
even now it seems documentation site seems abandoned. Though players
like Netflix, Apple and Microsoft
YgaByte!!! <— another Cassandra “compliant" DB - not sure if they forked C*
or wrote Cassandra in go. ;)
https://github.com/YugaByte/yugabyte-db
Datastax is Cassandra compliant — and can use the same sstables at least until
6.0 (which uses a patched version of “4.0” which is 2-5x faster) —
There are 4+ implementations of CQL in addition to Apache Cassandra - the
ones I can think of off the top of my head include DSE, Yugabyte, CosmosDB,
and Scylla.
You'll want to define "popular". If by popular you mean "which
implementation of CQL has the most installed servers", nobody knows for
Hello,
It's a complex topic that has already been extensively discussed (at least
for the part about Datastax). I am sharing my personal understanding, from
what I read in the mailing list mostly:
Recently Cassandra eco system became very fragmented
>
I would not put Scylladb in the same 'eco
