We use both SOLR and Elasticsearch at Chegg. The search for www.chegg.com is powered by SOLR, because that's done by the search team, who are are more hard-core search nerds, like XML instead of JSON, etc. They have one master and a whole bunch of slaves, and rebuild the master continuously.
I wanted to switch to Elasticsearch for the eReader team, because we're constantly adding new eBooks to our catalog, so I needed something that clustered. We had a bunch of endless meetings discussing it. Ops wanted a zone-aware solution, which Solr Cloud, since its based on Zookeeper, couldn't do automatically. Plus realistically, only the search folks knew how to deal with Solr. I could deal with ES with just my team with partial attention. Elasticsearch could do the zone aware thing, so that's how I got Ops to sign up. Plus they were already using Logstash. But really, its because its much easier for me to administrate, and the clustering part just works on its own without needing zookeeper. Pierce -- 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/d871e8ad-8403-46cc-aa4b-942d7477604a%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
