I see what you mean now. Thing is that we are actively moving from MySQL to Couch now and migrating tons of data at a time. So in return all the views need to catch up with all of those new documents. Erlang seems to be a promising candidate to speed up our development. That's all. I just tried it yesterday and I'm pretty happy with how much faster it is than Javascript.
On Thu, Aug 15, 2013 at 12:01 PM, Jens Alfke <[email protected]> wrote: > > On Aug 14, 2013, at 9:53 PM, Andrey Kuprianov <[email protected]> > wrote: > > > Nope, not misreading anything. And I understand they do. But the sooner > > they finish the better, wont you agree? It's mainly because of that we > dont > > do view updates during weekdays. > > OK, you must be using CouchDB for some kind of analytics, or other batch > processing, if you can get away for _days_ with stale views. Which is a > totally valid and important use of CouchDB. But it’s completely different > from using it in a live user-facing application, where changes need to be > reflected pretty near instantly. That’s why I’m disagreeing with Jason’s > unqualified statements. > > If anyone needs an example, consider a typical online shopping site. Let’s > say the page that shows the contents of your shopping cart is driven by a > view query. If a customer adds an item to their cart and then goes to view > their cart a few seconds later, the item had better show up. If it takes 30 > seconds to show up — let alone a week — that’s going to confuse and annoy > users. > > —Jens
