- Mais recentes
- Mais votos
- Mais comentários
Based on the requirements and context you've provided, it seems you're looking for a cost-efficient, scalable server solution to handle battle simulations in your game without the need for persistent connections or real-time interactions. Here are a few options and considerations:
AWS Lambda with Container Images:
AWS Lambda now supports container images, which means you can package and deploy your Unity application as a container image. However, you'll need to consider the cold start time, especially if your container is large. You mentioned that the simulation takes around 0.2 seconds, which is well within Lambda's execution time limits.
ECS (Elastic Container Service) or EKS (Elastic Kubernetes Service) with Fargate:
If containerizing your Unity instance is feasible, ECS or EKS with Fargate allows you to run containers without having to manage servers or clusters. Like Lambda, you pay for what you use, and Fargate scales the compute capacity to match your workload.
ECS/EKS with Spot Capacity:
ECS/EKS with Spot Capacity leverages unused EC2 capacity at discounted rates. It combines the management convenience of ECS/EKS for containerized applications with the savings of Spot Instances. The service ensures automatic scaling and integration with AWS services, offering a seamless environment for deployment and management. This solution is ideal if your workload is designed to manage occasional disruptions effectively.
Batch Processing with AWS Batch:
If the matches can be processed in batches (i.e., not necessarily in real-time), AWS Batch could be a good solution. It efficiently runs hundreds to thousands of computing jobs across a range of AWS compute services, including AWS Lambda and ECS.
GameLift FleetIQ:
If you prefer GameLift for its features but find it expensive, consider GameLift FleetIQ. It's a solution for managing game servers on cheaper EC2 Spot Instances, potentially offering the best of both worlds.
Hybrid Approach:
You might also consider a hybrid approach where you use Lambda for lighter, less frequent tasks, and have an EC2 instance (or ECS/EKS with Fargate) for more demanding, continuous tasks.
If this has answered your question or was helpful, accepting the answer would be greatly appreciated. Thank you!
Conteúdo relevante
- AWS OFICIALAtualizada há 7 meses
This is great! Thank you