search

aws-samples / amazon-gamelift-ultrafrogroyale-large-match-sample

A small sample game that demonstrates how to use GameLift FlexMatch new large match features.
Apache License 2.0
22 stars 12 forks source link

Is this best practice? #9

Open chanson7 opened 2 years ago

chanson7 commented 2 years ago

https://github.com/aws-samples/amazon-gamelift-ultrafrogroyale-large-match-sample/blob/43dac185b6f6b4d4f76d771e55f7313719d5c5e8/AWS/ConnectUltraFrogRoyaleClient_Lambda.js#L64

According to AWS documentation, describeMatchmaking() is not meant to be continuously polled: https://docs.aws.amazon.com/gamelift/latest/apireference/API_DescribeMatchmaking.html

"This operation is not designed to be continually called to track matchmaking ticket status. This practice can cause you to exceed your API limit, which results in errors. Instead, as a best practice, set up an Amazon Simple Notification Service to receive notifications, and provide the topic ARN in the matchmaking configuration. Continuously poling ticket status with DescribeMatchmaking should only be used for games in development with low matchmaking usage."

squidbot commented 2 years ago

Clearly not :) I wrote this sample when large match was still in development and as a developer sample to introduce the concept. You should definitely follow the advice in the API documentation for a game at scale.