We have an application for which we are considering Couchbase. It’s somewhat different to “traditional”(!) uses of Couchbase.
We’re effectively taking a large dataset, originally in a MySQL database, filtering it heavily, and loading it in to a Couchbase instance, which we subsequently query. At the moment we’re using Couchbase as a key/value store, we’re not yet exploiting views and indexes although we plan to do so eventually.
The thing is that the loading process only happens once every few months. At all other times, the data is completely static.
Are there best practices for this sort of use-case? In a relational world I’d turn off indexing during the initial, write-heavy load phase, then turn it on when loading was complete. Is it generally recommended to do the same with Couchbase?
I’ll be interested to hear any thoughts you may have.