On May 16, 2006, at 3:30 PM, Nick Snels wrote:
> Solr looks a promising project, only problem I have with it is that
> you
> need Tomcat and a JVM. This adds two more variables to your
> configuration you have to control. Great if you know Java, but I'm
> programming in Ruby so I don't have to program in Java or .NET, or
> whatever. So I prefer a Ruby only environment for it's simplicity.
A fair and expected critique of using Solr in a Ruby environment.
Every language enjoys a bit of lock-in and programmers obviously
would prefer to work with native API's.
It is true you need a JVM to run Solr, but it doesn't have to be
Tomcat. I use Jetty. To fire up Solr in my Rails environment only
required I customize its schema.xml and solrconfig.xml files and run
"java -jar start.jar". And voila, its up and running. So while it
does add an entirely new moving piece, I view it as something akin to
adding a database. As long as there is a good way to communicate
with it natively (a Ruby/Solr API would be well received, methinks)
then Solr isn't any more, actually less, overhead to a projects
deployment than adding a database server.
Erik
_______________________________________________
Ferret-talk mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/ferret-talk
