3

Every time a user submits a score, Socket.IO causes all the users get their leaderboard updated. This causes every single user connected through Socket.IO to read from the Dynamo DB database (every time the a user submits a score). As a result, my database gets several reads/sec.

This costs me ALOT!

How do I reduce read requests/sec to DynamoDB significantly, so I don't end up loosing a lot of money?

3
  • I might not understand the question, but why aren't you pushing the score down to clients with socket.io? Don't get clients to read the data -- tell them what the data is. Is this an approach that might work?
    – user62575
    Jul 21 '16 at 21:52
  • Also, a caching layer might help out a lot.
    – user62575
    Jul 21 '16 at 21:53
  • DAX (aws.amazon.com/dynamodb/dax) might help.
    – Foole
    Nov 3 '19 at 6:11

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.