Starting from version 4.0, DataStax Enterprise (DSE) Search got more robust and scalable distributed queries, thanks to a custom implementation built on top of Netty.
We are improving our early adopter program (EAP) by offering a better way to give us feedback, share the experience and making access to resources (downloads, docs) easier. We are going to use phpbb3, an open source forum management package, to facilitate that.
For the third and final part of this series, we will shift gears and instead of talking about offense-driven best practices, we will cover defense-driven best practices around disaster prevention and monitoring.
I’m pleased to announce the DataStax Sandbox, which is a virtual machine (VM) image that contains a Linux-based bundle of DataStax software – DataStax Enterprise (DSE), OpsCenter, DevCenter, and a number of easy to use utilities – that’s designed to make it simple for you to get up to speed quickly with DataStax software.
This is the second in a series of posts about making good choices for hosting Cassandra on the Amazon Web Services (AWS) environment.
Introduction: Back in DSE 3.2 we quietly introduced support for CQL3 and DataStax Enterprise Search, but did little to showcase the new way of using CQL3 sets, lists, maps, and compound primary keys with Solr.
This is the first in a series of posts about making good choices for hosting Cassandra on the Amazon Web Services (AWS) environment.