Alien App Server Region Selection (AWS)

Deploying and Designing a Server on AWS

It's finally time to deploy the server.

"It feels like the launch is getting closer..."

Alien is a global dating app. As such, it needs to target a global audience, which necessitates multi-region support.

The requirements are:

1. Multi-region support is needed. Servers need to be located in various countries and locations.

2. Too many configurations should be avoided. (Since a small team will operate it, they might not be able to manage all the controls).

3. Autoscaling needs to be implemented. (While not immediately necessary, it's convenient to have it pre-configured).

It's likely to be designed something like this.

Which services should we use?

However, multi-region support is not automated, so we need to configure it manually. This isn't a major problem as we can automate the upload process using GitHub Actions.

Which regions should we use?

Ideally, we would use four regions, but that's for when we have more money and users. For now, we're limiting it to two.

* Future planned regions

3. sa-east-1 - São Paulo, or us-west-2 - Oregon: The South American market is large, but purchasing power is considered lower. However, we believe that purchases from other countries might flow into the South American market, so it's a positive outlook.

The US market is large, but we believe that there's less interest in international dating compared to other countries. We'll conduct further market research to make a decision.

So, the conclusion is that South Americans might be more valuable. Let's just keep this in mind for now.

I think this should be sufficient.

We can configure routing using Amazon Route 53... and use S3 + CDN (CloudFront) to ensure that images, videos, and other content are delivered with minimal latency.

This should be enough to get it running.