I appreciate the thoughtful replies. We will have to evaluate whether
cassandra is the right datastore for us. It was chosen because our primary
requirement is to store lots of data about lots of devices at a high rate.
The search requirements are very secondary but required for the management
of t
If the goal is arbitrary queries, I'd avoid Cassandra altogether. Don't
use DSE Search or Ellesandra, they're two solutions designed to solve
problems that are Cassandra first, search second.
I'd go straight to elastic search for workloads that are primarily search
driven, like you listed above.
+1 on Datastax and could consider looking at Elassandra.
On Thu, Feb 7, 2019 at 9:14 AM Durity, Sean R
wrote:
> Kenneth is right. Trying to port/support a relational model to a CQL model
> the way you are doing it is not going to go well. You won’t be able to
> scale or get the search flexibilit
Kenneth is right. Trying to port/support a relational model to a CQL model the
way you are doing it is not going to go well. You won’t be able to scale or get
the search flexibility that you want. It will make Cassandra seem like a bad
fit. You want to play to Cassandra’s strengths – availabilit
