I am new to this but I wanted to pitch a setup to you. I have a website being coded at the moment, in the very early stages, but is effectively a full text scrapper and search engine. We have decided on SOLR for the search system.
We basically have two sets of data: One is the content for the search engine, which is around 100K records at any one time. The entire system is built on PHP and currently put into a MSQL database. We want very quick relevant searches, this is critical. Our plan is to import our records into SOLR each night from the MYSQL database. The second set of data is other parts of the site, such as our ticket system, stats about the number of clicks etc. The performance on this is not performance critical at all. So, I have two questions: Firstly, should everything be run through the SOLR search system, including tickets and site stats? Alterntively, is it better to keep only the main full text searches on SOLR and do the ticketing etc through normal MYSQL queries? Secondly, which is probably dependant on the first question. If everything should go through SOLR, should we even use a MYSQL database at all? If not, what is the alternative? We use an XML file as a .SQL replacement for content including tickets, stats, users, passwords etc. Sorry if these questions are basic, but I’m out of my depth here (but learning!) James -- View this message in context: http://lucene.472066.n3.nabble.com/SOLR-Just-for-search-or-whole-site-DB-tp3763439p3763439.html Sent from the Solr - User mailing list archive at Nabble.com.
