title: Should I treat Couchbase bucket as table, or more like a schema
body: <p>I am planing to use <strong>Couchbase</strong> as Documentation store in my web application. I am looking at <strong>Couchbase client for Java</strong>, and you need to create separate <strong>Couchbase Client</strong> for each bucket, if I treat Couchbase bucket as I would treat generic entity. This is a bit of overkill for the system (though, I can reuse executing service to minimize object creation and thread management overhead.)</p>
  
  <p>So</p>
  
  <ol>
  <li>Is there a way to reuse existing CouchbaseClient for multiple buckets (Not only adding ExecutionService)</li>
  <li>Would not it be better to use single bucket, and distinguish objects based on the keys, and rely on views selectors for querying, from performance point of view.</li>
  </ol>