1

we're facing a common use-case which seems "impossible" to solve with CouchBase server.... Basically in our web app we need to implement grids showing FRESH data (with all newest/updated documents present!)

EX: User creates a new "order" in a dedicated edit page, then goes to "all orders" page with the grid and expects to see the just-created record.

How can we achieve this?

  • since the grids is bound to a VIEW its index could be out-dated.
  • also using "stale=false" the new index could NOT contain the last data, since it could be still in the "disk-writes" queue
  • we can't afford to use "PersistTo.XXX" to force disk write upon Store because of performance issues (the architecture is multi-tenant and we must handle hundreds of write operations / min. Actually our couchbase cluster performs ~2500 MemCached ops/sec BUT ~3 Disk-writes ops/sec !!! )

Any soulution? For this kind of needs is a NoSql DB a good way out? (We'd like to avoid mixed-solution RDBMS+NoSql... Maybe a compromise on grids freshness or a complicated "home-made dirty-documents-list" mechanism?)

Thankyou in advance....

Community
  • 1
  • 1
user2470997
  • 11
  • 1
  • You have something seriously wrong if you are only getting 3 disk writes a second. What are the machine specs that you are using? How much data do you have stored and how much is held in ram? – scalabilitysolved Apr 08 '14 at 15:16

1 Answers1

1

Firstly it'd be good if you could give more information so we could look at why your disk writes are so low. Secondly have you decided to use Couchbase because you want to or because it fits your data and access patterns? Wouldn't a RDBMS solution be better for you?

Regarding your explanation of a user creating a new order, personally I wouldn't use a view to capture this data, on the user document I would have two attributes, processed orders and pending orders. As a user adds something to their basket you could add the id of the product to the pending orders array, as the transaction is completed this could then be moved to processed orders.

This structure means that when you want to display all orders for a user you can just do a simple multi get on all the ids held on the document, be aware that you'd then have to sort them at the application layer by whichever attribute you wanted but that'd be trivial!

Good luck!

scalabilitysolved
  • 2,473
  • 1
  • 26
  • 31