fargate-game-servers VS aws-lambda-dotnet

AWS - GameTech

Visit https://aws.amazon.com/gametech/ to get started today!

Even if BSG came out tomorrow and publicly released their entire server topology/infrastructure, then said "here's what's consistently failing under too much load; somebody with expertise please help us fix it", there'd still be 10+ people all making blanket suggestions like "jUsT pUT iT In ThE ClOuD!!! It's this easy!", without a single iota of a nuance or a detailed solution offered. As if it's just a matter of calling fucking CDW or something and having their "experts" migrate your product into your elastic computing partner of choice over a weekend, JFC.

Also curious, maybe it was mentioned by Scott in an interview. Amazon Game Tech has many hosting solutions not just EKS.

Amazon Web Services (AWS - Game Technologies group)| Various roles | Seattle (though currently WFH) | Full-time, Onsite | https://aws.amazon.com/gametech/

I am the senior manager (skip-level manager) for these roles so feel free to email me with questions (contact info in my profile). We have multiple mid-level (experience expected) software development engineering roles open. We work on cutting edge tech that helps games and simulations run on AWS and scale in ways they couldn't alone. I am looking for people with distributed service development (we do most of this in Java), and game engine/game dev experience (preferred Unreal). We're building an all new AWS service, solving hard technical problems, and we get to have games as a customer, which is pretty awesome to me.

Links: (service focused SDE role) https://www.amazon.jobs/en/jobs/1365397/software-development..., (game engine role) https://www.amazon.jobs/en/jobs/1365399/software-development...

Game Server Hosting on AWS Fargate This repository contains an example solution on how to scale a fleet of game servers on AWS Fargate on Elastic Container Service and route players to game sessions using a Serverless backend. Game Server data is stored in ElastiCache Redis. All resources are deployed with Infrastructure as Code using CloudFormation, Serverless Application Model, Docker and bash/powershell scripts. By leveraging AWS Fargate for your game servers you don't need to manage the underlying virtual machines.

I saw this issue: https://github.com/aws/aws-lambda-dotnet/issues/245

Creating Lambda Project using Amazon.Lambda.Templates. I use Amazon.Lambda.Annotations because it will be similar to my previous console program, and we can use dependency injection.

Hopefully, this post will have intrigued you enough to check out the new framework, and try converting some of your existing functions into what I think is a much more readable and easier to comprehend format. Also, the development team is always interested in feedback, which you can supply in the issues folder of their repo. You can also find the design document for the annotations in this issue.

I don't think it's exactly what you're looking for, but you could try out the LambdaTestTool https://github.com/aws/aws-lambda-dotnet/tree/master/Tools/LambdaTestTool

According to this GitHub issue we need to add and configure an additional package when running a custom runtime on ARM:

I'm assuming API's are REST APIs. Those sound like excellent use cases for running as Lambda functions. If the API's are an ASP .NET Core Web API project it is possible to deploy that to Lambda using the Amazon.Lambda.AspNetCoreServer, https://github.com/aws/aws-lambda-dotnet/tree/master/Libraries/src/Amazon.Lambda.AspNetCoreServer, NuGet package. That can be a quick way to get something working and then later choose to rearchitect to a smaller more micro services architecture if necessary.

AWS provides a NuGet package (see Amazon.Lambda.AspNetCoreServer) that makes it easy to do this. It works pretty well, but instead of one copy of the API serving many clients you have many copies of the API each serving one client at a time. There are also limitations in areas like file upload and download (which vary depending upon whether this is being used with API Gateway or an Application Load Balancer).