I’m creating a web API service that manages friends list and leadersboards.
When user requests leadersboard, server returns only user’s friends’ ranking and scores.
Now I’m figuring out right Couchbase schema structure regarding large number of users and API calls.
Meanwhile, I want to keep a cluster with as small number of nodes as possible.
On the Couchbase example leadersboard is implemented using view,
while I prefer to use append operation and manage manual index.
My questions are :
Could you give me a recommendation which one to use, view or creating manual index using append operation
regarding the performance and throughput?
To keep the manual index updated, when I finish a game and register a new score,
Couchbase have to append this score to all of my friend’s leadersboard documents.
mostly new score need be appended to less than 100 documents (=number of user’s friend).
However, there might be a extremely hard user that has more than 1000 friends.
For him, when he finish a game, application server need to call append operation to couchbase 1000 times.
I want to know if this scenario is acceptable for correctly using Couchbase.