what about lambda architecture, small&fast + fat&batch
in the light of nosql, we know that views are batched. If the buckets are large, the views could lag behind the actual data. While this is acceptable for offline systems, is not acceptable for more reactive system. Imaging setting up an account and have to wait minutes just to login.
At civolution.com we need fat&batch views, but we also would like responsive, uptodate results on the latest data created in the database. Playing around with the stale parameter is not an option, since it falls short of expectations in one way or another (either uptodate but long latency or fast and not uptodate)
Ideally what we would like is a system composed of two components where the fast components would "fill in" the state of the last hours providing the user with fully up-to-date views combining the best of both worlds. In this way we don't have to compromise coherency and stale result with speed.
The other solution would be so move back to a responsive mysql system and leave couchbase as background fat and batch system. But it's definitely not the way I envision using couchbase on the first place.
What are your takes on this?