On 30 May 2012 03:51, rjain15 <rjai...@gmail.com> wrote: > Hi Gora, > > I am working on a Mobile App, which is updating/accessing/searching data and > I have created a simple prototype using Solr and the Update JSON / Get JSON > functions of Solr. > > I came across some discussion on MongoDB and how it natively stores JSON > data, and hence as I was looking at scalability of data storage/indexing, I > was pausing to understand if I am on the right track of just using Solr or > should I combine Solr with MongoDB as I am reading this blog post... [...]
A discussion on web architecture is off-topic for this list, and will also probably draw in people with strong opinions. Here is a brief personal opinion, but you are probably better off trying out a couple of different architectural prototypes, and/or talking to someone with experience in scalable sites. First of all, you should consider whether you really need a NoSQL store. This would depend on the scale, and requirements of your app. IMHO, RDBMSes now are proven systems with many years of learning behind them. Thus, your question should be why NoSQL, rather than the other way around. Solr for search should do fine, and you already know how to get JSON in and out of it. Incidentally, we also tested out Solr as a NoSQL store (raw data, and not JSON, though), and were quite happy with the performance. Regards, Gora
