# Cassandra + Elastic Search **URL:** \ **Category:** Elasticsearch\ **Created:** [April 2, 2012, 9:05pm UTC](https://discuss.elastic.co/t/cassandra-elastic-search/7204 "2012-04-02T21:05:33Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![benmccann](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/benmccann/32/420_2.png) [@benmccann](https://discuss.elastic.co/u/benmccann)\ **Post date:** [April 2, 2012, 9:05pm UTC](https://discuss.elastic.co/t/cassandra-elastic-search/7204/1 "2012-04-02T21:05:33Z")
Hi, I currently have numerous documents stored in Cassandra. However, they're difficult to index. Cassandra does not have native support for indexing documents (especially nested documents), so my datastore at this point is just storing these docs as blobs associated with some key. I'm thinking about adding elastic search to my setup to index these docs. Would it make more sense to have ES index my Cassandra datastore or should I ditch Cassandra entirely to have ES store my docs? Getting rid of Cassandra would mean one less service to run in my cluster, but I'm wondering if there's something I might be giving up if I do this like durability, etc.? Thanks, Ben ---
**Author:** ![ppearcy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ppearcy/32/980_2.png) [@ppearcy](https://discuss.elastic.co/u/ppearcy)\ **Post date:** [April 3, 2012, 4:13pm UTC](https://discuss.elastic.co/t/cassandra-elastic-search/7204/2 "2012-04-03T16:13:31Z")
I recommend to keep Cassandra as your primary data store, for now. ES has been much improved in terms of durability, but I believe is still not recommended as the primary data store. On Apr 2, 3:05 pm, Ben McCann [benjamin.j.mcc...@gmail.com](mailto:benjamin.j.mcc...@gmail.com) wrote: > Hi, > > I currently have numerous documents stored in Cassandra. However, they're > difficult to index. Cassandra does not have native support for indexing > documents (especially nested documents), so my datastore at this point is > just storing these docs as blobs associated with some key. I'm thinking > about adding Elasticsearch to my setup to index these docs. Would it make > more sense to have ES index my Cassandra datastore or should I ditch > Cassandra entirely to have ES store my docs? Getting rid of Cassandra > would mean one less service to run in my cluster, but I'm wondering if > there's something I might be giving up if I do this like durability, etc.? > > Thanks, > Ben ---
**Author:** ![Radu\_Gheorghe1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/radu_gheorghe1/32/2688_2.png) [@Radu\_Gheorghe1](https://discuss.elastic.co/u/Radu_Gheorghe1)\ **Post date:** [April 4, 2012, 9:26am UTC](https://discuss.elastic.co/t/cassandra-elastic-search/7204/3 "2012-04-04T09:26:26Z")
I think it depends on how "critical" your data is. But since you would use ES for searching whatever the setup, the "durability" part probably boils down to how long it takes and how complicated it is to reindex your data in case something goes wrong. Because if ES fails, you can't search properly even if you have Cassandra working well underneath. There are some threads here about how you can back up your ES indexes. And using ES alone comes with quite a lot of gains in terms of simplicity and performance. I would keep Cassandra it would be critical for me to keep the _unindexed_ data in a durable database. Otherwise, I would ditch it and try to find a way to recover in case something goes wrong. Which can happen with Cassandra as well - we just assume ES is more prone to that because it's a younger product. On Apr 3, 7:13 pm, ppearcy [ppea...@gmail.com](mailto:ppea...@gmail.com) wrote: > I recommend to keep Cassandra as your primary data store, for now. ES > has been much improved in terms of durability, but I believe is still > not recommended as the primary data store. > > On Apr 2, 3:05 pm, Ben McCann [benjamin.j.mcc...@gmail.com](mailto:benjamin.j.mcc...@gmail.com) wrote: > > > Hi, > > > I currently have numerous documents stored in Cassandra. However, they're > > difficult to index. Cassandra does not have native support for indexing > > documents (especially nested documents), so my datastore at this point is > > just storing these docs as blobs associated with some key. I'm thinking > > about adding Elasticsearch to my setup to index these docs. Would it make > > more sense to have ES index my Cassandra datastore or should I ditch > > Cassandra entirely to have ES store my docs? Getting rid of Cassandra > > would mean one less service to run in my cluster, but I'm wondering if > > there's something I might be giving up if I do this like durability, etc.? > > > Thanks, > > Ben ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 3:33am UTC](https://discuss.elastic.co/t/cassandra-elastic-search/7204/4 "2017-07-06T03:33:44Z")