We are currently using Couchbase Community 4.0 in a small, 3 node cluster. We have not deployed dedicated Index servers; the load on the cluster is modest which doesn’t seem to justify dedicated resources.
However, I am curious to know what type of discretion should be used in the number of indexes created, other than pure hardware limitations. The reason I ask is because a couple of years ago when we first started exploring the use of Couchbase (in the pre-index, pre-N1QL days), we created a large number of Views (probably 20 design documents with approximately 5 views in each). We started running into performance problems and later found out that we were well beyond the number of Views the Couchbase would reliably handle.
To avoid putting ourselves in a situation again, I’d like to know the restraints (beyond hardware) or “best practices” in terms of the number of indexes. We’re not looking to get too crazy, but are considering creating about 30-40 different indexes.