An interesting blog post that popped on my aggregator radar:
<http://blog.tourb.us/archives/searching-with-solr/>
"Solr Cons:
Requires java for deployment and for plugin development (although
jruby might come into play here)
Uses more memory than we’d like in our resource-constrained environments
Running a separate process adds some operational overhead"
And then this quote in the comments:
"Anybody who refuses to link up a standalone server like Solr to
their Ruby app because it is written in Java is going to have a
brutal dose of reality if they call up their database vendor to ask
what they are written in. I don’t think I’m going out on a limb to
say that none of MySQL, Postgres, Oracle, Sybase, etc. are old Ruby
projects."
<http://blog.tourb.us/archives/searching-with-solr/>
"Solr Cons:
Requires java for deployment and for plugin development (although
jruby might come into play here)
Uses more memory than we’d like in our resource-constrained environments
Running a separate process adds some operational overhead"
And then this quote in the comments:
"Anybody who refuses to link up a standalone server like Solr to
their Ruby app because it is written in Java is going to have a
brutal dose of reality if they call up their database vendor to ask
what they are written in. I don’t think I’m going out on a limb to
say that none of MySQL, Postgres, Oracle, Sybase, etc. are old Ruby
projects."