3 ms·

"That’s why there is no Red Hat of Lucene or Solr, despite their enormous popularity in search" You forgot ElasticSearch, which is not a Red Hat but seems to b

by cfontes 12y ago

"That’s why there is no Red Hat of Lucene or Solr, despite their enormous popularity in search" You forgot ElasticSearch, which is not a Red Hat but seems to be doing fine and working on getting there. They have some interesting takes on open source, they give the dough for free but the frosting like security and managing interface are charged/subscription, I think it can work. Also their software is built on top of SOLR/LUCENE but with lot more enterprize keywords thrown at it (Distributed,Clustering....) So makes it easier to sell for the

arafalov 12y ago
Well, it's not that simple. Elasticsearch seems to have shifted their positioning from pure Search Engine to the log analytics with strong emphasis on the ELK stack. They had early advantage over Solr by addressing the Innovator's dilemma and tackling things Solr did not touch (better clustering, JSON interface, smaller initial downloads, dynamic configuration, etc). But the actual commercial entity on top of Solr (LucidWorks) has finally noticed that and has put some resources in closing the gap and maybe even getting ahead of Elasticsearch. And, of course, their own commercial product (Fusion) has all those enterprize keywords covered as well. Also, LucidWorks is not the only commercial company putting money into Solr. Cloudera (yes, the one with 1.2 billion $ of investment) is fully committed to Solr and is contributing to it as well. I'd say LucidWorks wants to the be The Red Hat of Solr, while Elasticsearch is trying to take over Splunk in that very specific (and, as Splunk proved, fairly lucrative) part of the log collection/analysis business.
- AznHisoka 12y ago
  log collection? eww.. that's so boring. For a company that's trying to focus on log analysis, they sure have a much better search engine than SOLR (see percolation, sharding, distribution capabilities, REST interface)
  - arafalov 12y ago
    I did look for a while. Even got to present on it: http://www.slideshare.net/arafalov/solr-vs-elasticsearch-case-by-case http://www.slideshare.net/arafalov/solr-vs-elasticsearch-cas... (video out soon) # The percolation apparently does not scale: (as compared to https://github.com/flaxsearch/luwak https://github.com/flaxsearch/luwak - Not in Solr yet, granted ), # The sharding and distribution has (in ES 1.3) serious issues due to the in-house implementation (http://aphyr.com/posts/317-call-me-maybe-elasticsearch http://aphyr.com/posts/317-call-me-maybe-elasticsearch) # The REST interface is nice but is also coming to Solr really fast # The rivers are deprecated. The scripting (enabled by default originally) had to be reworked due to Amazon shutting down every EC2 Elasticsearch instance they detected. # Some other features have been deprecated and now are basically the same as Solr (e.g. copy_to vs. copyField). The production recommendations from Elasticsearch specialists are to disable dynamic schema, _source, and _all fields. Not that Elasticsearch is bad. I just feel it is not fair to compare a commercial solution (that does not even give you admin console for free) to a fully open-source solution (that does). If you are planning to pay money for commercial solution, then compare it with another commercial solution (e.g. LucidWorks Fusion). Or at least compare latest Elasticsearch (1.4) to the latest Solr (4.10.2 currently).

by cfontes 12y ago

arafalov 12y ago

Well, it's not that simple. Elasticsearch seems to have shifted their positioning from pure Search Engine to the log analytics with strong emphasis on the ELK stack. They had early advantage over Solr by addressing the Innovator's dilemma and tackling things Solr did not touch (better clustering, JSON interface, smaller initial downloads, dynamic configuration, etc). But the actual commercial entity on top of Solr (LucidWorks) has finally noticed that and has put some resources in closing the gap and maybe even getting ahead of Elasticsearch. And, of course, their own commercial product (Fusion) has all those enterprize keywords covered as well. Also, LucidWorks is not the only commercial company putting money into Solr. Cloudera (yes, the one with 1.2 billion $ of investment) is fully committed to Solr and is contributing to it as well. I'd say LucidWorks wants to the be The Red Hat of Solr, while Elasticsearch is trying to take over Splunk in that very specific (and, as Splunk proved, fairly lucrative) part of the log collection/analysis business.

AznHisoka 12y ago
log collection? eww.. that's so boring. For a company that's trying to focus on log analysis, they sure have a much better search engine than SOLR (see percolation, sharding, distribution capabilities, REST interface)
- arafalov 12y ago
  I did look for a while. Even got to present on it: http://www.slideshare.net/arafalov/solr-vs-elasticsearch-case-by-case http://www.slideshare.net/arafalov/solr-vs-elasticsearch-cas... (video out soon) # The percolation apparently does not scale: (as compared to https://github.com/flaxsearch/luwak https://github.com/flaxsearch/luwak - Not in Solr yet, granted ), # The sharding and distribution has (in ES 1.3) serious issues due to the in-house implementation (http://aphyr.com/posts/317-call-me-maybe-elasticsearch http://aphyr.com/posts/317-call-me-maybe-elasticsearch) # The REST interface is nice but is also coming to Solr really fast # The rivers are deprecated. The scripting (enabled by default originally) had to be reworked due to Amazon shutting down every EC2 Elasticsearch instance they detected. # Some other features have been deprecated and now are basically the same as Solr (e.g. copy_to vs. copyField). The production recommendations from Elasticsearch specialists are to disable dynamic schema, _source, and _all fields. Not that Elasticsearch is bad. I just feel it is not fair to compare a commercial solution (that does not even give you admin console for free) to a fully open-source solution (that does). If you are planning to pay money for commercial solution, then compare it with another commercial solution (e.g. LucidWorks Fusion). Or at least compare latest Elasticsearch (1.4) to the latest Solr (4.10.2 currently).