3 ms·

> Why would you care about the redundancy on staging / dev? If you deploy to multiple regions then it wouldn't make no sense at all to have a single preprod st

> Why would you care about the redundancy on staging / dev? If you deploy to multiple regions then it wouldn't make no sense at all to have a single preprod stage, specially to run integration tests. Also, keep in mind that professional apps support localization, and localization has a significant afinity with regional deployments. I mean, if you support japanese and have a prod stage on Japan, would you think it was a good idea to run localization tests in a us deployment?

philliphaydon 4y ago
Currently have a deployment in Oregon and cloudfront servicing most of the world. With localisation. No need to deploy in Japan to support Japan. The only tricky one is China because of the firewall. Tho that hasn’t been an issue for the last few years as they haven’t been blocking cloudfront completely. (This has been running for 10 years in AWS without issue)
- arinlen 4y ago
  > Currently have a deployment in Oregon and cloudfront servicing most of the world. With localisation. So you're serving static assets through CloudFront with a single backing service. Congrats, you managed to have a service that doesn't offer regional services. Also, you definitely don't support clients in China, or enjoy shooting yourself in the foot. Most professional applications with a global deployment and paying customers don't have the benefit of uploading HTML and calling it done.
  - philliphaydon 4y ago
    So 10+ years of supporting broadcasters and creative agencies around the world from 1 region is not supporting those countries. Got it. I mean there’s services in those regions for the tasks performed but even then it doesn’t require the level of testing you’re assuming it does.
    - sieabahlpark 4y ago
dageshi 4y ago
If you're deploying to multiple regions in aws then you'd presumably have to roll out the infrastructure for 3 regions yourself if you weren't? In which case I gotta assume using aws is probably a lot more straightforward straight off the bat than rolling your own solution in three different data centers?

philliphaydon 4y ago

Currently have a deployment in Oregon and cloudfront servicing most of the world. With localisation. No need to deploy in Japan to support Japan. The only tricky one is China because of the firewall. Tho that hasn’t been an issue for the last few years as they haven’t been blocking cloudfront completely. (This has been running for 10 years in AWS without issue)

arinlen 4y ago
> Currently have a deployment in Oregon and cloudfront servicing most of the world. With localisation. So you're serving static assets through CloudFront with a single backing service. Congrats, you managed to have a service that doesn't offer regional services. Also, you definitely don't support clients in China, or enjoy shooting yourself in the foot. Most professional applications with a global deployment and paying customers don't have the benefit of uploading HTML and calling it done.
- philliphaydon 4y ago
  So 10+ years of supporting broadcasters and creative agencies around the world from 1 region is not supporting those countries. Got it. I mean there’s services in those regions for the tasks performed but even then it doesn’t require the level of testing you’re assuming it does.
  - sieabahlpark 4y ago

dageshi 4y ago

If you're deploying to multiple regions in aws then you'd presumably have to roll out the infrastructure for 3 regions yourself if you weren't? In which case I gotta assume using aws is probably a lot more straightforward straight off the bat than rolling your own solution in three different data centers?