Hey ..
I haven't used Ferret in an application yet, but I love what I see so far. The ability to have an in-process server in development, and the clean Ruby API are big wins for me. But I've heard a lot of scary things about corrupted indexes, even when using the DRb server. Is this just FUD? Are there any unresolved issues revolving around corrupted indexes? Can I afford to use Ferret in big applications for Fortune-500 clients? (I know that sounds... pompous really, but it's a genuine concern.)
We're using ferret on omdb.org for 14 month without any problems. There're a few things you might want to work around (Erik pointed some out). If you expect a huge amount of index updates, you need to think about a few infrastructural problems, because right now, AAF does not allow you to cluster indexing servers. but i know there is a solution for that :) If you just have huge amount of search queries, there is no need to worry.. i would not suggest usings AAF's ferret server for searching, though .. but it's quite easy to do the searching in each mongrel, so not concern here either. i guess we need more information about the data you want to index to give more detailed advices.
I've also read a few messages about serializing index requests/updates to Ferret through message-queues. Are there any decent guides/blog-posts on this topic?
yes, that's currently being worked on .. so there will be some guides later on :) Cheers Ben --- Benjamin Krause http://www.omdb.org/ [EMAIL PROTECTED] Rails-Schulung "Advancing with Rails" mit David A. Black 19.11.-22.11.2007, Berlin-Mitte Details u. Anmeldung: http://www.railsschulung.de
_______________________________________________ Ferret-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/ferret-talk
