Have you looked into using pull queues combined with sharded counters?
If you lease 1,000 tasks at a time you can probably condense writes
considerably. There are several different sharding strategies you
could take, even just one master set of shards each of which covers
all items. 100 shards
We are developing an application, where users can vote for many
objects.
(for example, voting the best music video of the week)
- This means, we have millions of possible objects to vote for, and
millions of users
To our best knowledge, after taking in consideration different
options, the best
