Datastax have also gone far out of their way to support companies using Cassandra regardless of if it happens to be the DSE or not. We are not part of any paid agreement with the company and I had a Datastax employee sending me texts late on a weekend to help me through an issue I was having with my cluster.

Actions like this demonstrate to me a commitment by Datastax to provide support and "warm fuzzies" to the entire community. Having them around has eased many of my concerns for running Cassandra on a limited small business budget.


On Fri, May 23, 2014 at 1:42 PM, Robert Coli <rcoli@eventbrite.com> wrote:
On Fri, May 16, 2014 at 10:56 AM, Kevin Burton <burton@spinn3r.com> wrote:
Perhaps because the developers are working on DSE :-P

FWIW, and I am not necessarily known for being the biggest defender of Datastax and the relationship of their commercial interests to the architectural direction of Cassandra...

... Datastax contribute a huge amount of work back to Apache Cassandra by the simple method operating on "Cassandra issues" raised by DSE customers inside of the Apache JIRA. If they are not out there selling DSE to these (often quite large) customers, there is not necessarily a commercial driver for fixing these "Cassandra Issues."

The DSE features are mostly isolated enough from the main codebase, and from my understanding the teams are separated enough internally, that I'm pretty confident Datastax is a significant net positive for contribution to and promotion of Apache Cassandra.

=Rob



--
David Daeschler