hi, everywhere around me i hear people whisper Elastic Search, so seems a very valuable asset to consider. However when reading through http://solr-vs-elasticsearch.com/ this paragraph stroke me:
"7. Overall from working with clients as a Solr/Elasticsearch consultant, I’ve found that developer preferences tend to end up along language party lines: if you’re a Java/c# developer, you’ll be pretty happy with Solr. If you live in Javascript or Ruby, you’ll probably love Elasticsearch. If you’re on Python or PHP, you’ll probably be fine with either.”
in combination with:
“3. I find Elasticsearch’s documentation to be pretty awful. It doesn’t help that some examples in the documentation are written in YAML and others in JSON. I wrote a ES code parser once to auto-generate documentation from Elasticsearch’s source and found a number of discrepancies between code and what’s documented on the website, not to mention a number of undocumented/alternative ways to specify the same config key.”
We have grown to be more javascript oriented in recent years, with the switch to angular and swagger api. However we are also quite java/xslt oriented. For me a switch to ES would be a choice in the line of more javascript oriented and Solr keep more on the java/xslt.
my 2 cents, Paul