> Nomad is similar to Kubernetes, AWS ECS, AWS EKS, Azure AKS, etc, but a bit simpler to work with in a day-to-day. This will greatly simplify your configuration. You will not need to do any additional configuration on Amazon Linux 2 or the distribution of Ubuntu those instances deploy with using the Launch Wizard - both from the point of view of the Linux firewall and from the point of view of security group configuration. It sounds like your current instances were deployed to a private subnet. They will correctly reach WAN addresses via their public interface and you will not need a NAT gateway. You can assign public IP addresses to your t4g instances by using a public subnet in the VPC they are deployed to. If the OpenTTD folks are reading this: this is not true. So instead, we run as much as we can IPv6-only. Sadly, those are (relatively speaking) rather expensive.
On AWS you do this by installing NAT gateways. > To keep the AWS infrastructure as cheap as possible, we wanted to avoid needing a NAT gateway: if you use IPv4, you need something that allows you to talk with the outside world. Hmm, the web services interact with OpenTTD the game/application, across a few versions, so it's understandable to me that their infrastructure is complex. Start scaling only when the load from this setup overwhelms you (and I can guarantee it won't for 99.9% of cases, including the one in this post). Data stored in mysql or postgres with some regular backup. A single web service to handle all business logic, hosted on two rented VPS instances which split traffic.
#AWS MINECRAFT SERVER HOSTING PRO#
> In total, we store over 150GiB of data, transfer over 6TiB of data monthly, have more than 10M requests a month, and serve thousands of unique visitors every week.īasically my MacBook Pro from 2019 could host all their infra and data and serve the entire load (~3 RPS) with room to spare for my day-to-day work.įor anyone else who is reading the post looking to get inspired – ignore everything they did and start small. Was waiting for them to get to the "why is it so complex" part, but after all the details of Cloudflare Pages, Cloudflare R2, Cloudflare Workers, Cloudflare Access, EC2 instances, multiple CDNs, hosted Redis, Nomad, Pulumi, web of proxies and APIs and front doors, a dozen microservices and an IaaS repo to make sense of all of this, it came down to: The question: how does OpenTTD’s infrastructure look, or even: why is it so complex, is a rather complicated question to answer in a few words.
0 kommentar(er)
