Some people simply feel more comfortable using some of these other technologies. Others may really have different access patterns, some of which ES may not handle well (this is theory - in our work with many, many companies using ES I've seen many cases of this double-storage approach, but I don't recall a concrete example of this being required because of a different access pattern ES cannot handle).
Some of the cons of having both: * keeping them in sync * duplicate data * more hardware needed * more work to maintain * more $$$ Otis -- Performance Monitoring * Log Analytics * Search Analytics Solr & Elasticsearch Support * http://sematext.com/ On Wednesday, July 16, 2014 8:05:15 AM UTC-4, HansPeterSloot wrote: > > Hi, > > While reading and watching a lot of material about elasticsearch I > frequently noticed that EE is often > combined with other NoSql products like Mongodb or Cassandra. > That suprised me. > > Can someone shed some light on the disadvantage of only using ES? > And what are the advantages of using a combination? > > Regards Hans > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/174d5d29-f7bf-4c11-977e-b32488fb409c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
