I am at a point where I have set up a SNS topic for GameLift, and I have subscribed a SQS queue to the topic and am able to get messages via reading from the queue. However, I am now wondering, what is the difference between doing this and calling
DescribeMatchmaking to get the status of my matchmaking tickets? I have read on previous posts that it is bad to call
DescribeMatchmaking at high volumes and that it should only be used in local testing. I am wondering why that is? Does
DescribeMatchmaking put strain on the GameLift fleets/resources? And also what is the recommend approach then for notifying the client about a match/ticket’s status? Because right now, I am currently deciding between having the client call a Lambda-function-integrated-API every 10 seconds that either
- Reads from an SQS queue that is subscribed to a SNS topic that is receiving GameLift event notifications
- Reads from a database like DynamoDb that gets the SNS topic messages from a Lambda function that is subscribed to the topic.
Lastly, any examples would be very helpful. Thank you in advance.