I dunno how else to put it. Having EVERYTHING on AWS is a national security threat. This isn't good, and someone who can do something about it needs to.
Having _everything_ on a single AZ of AWS is, indeed, a problem. Having everything well-architected on AWS is...well, it's a problem for reasons of monopoly and cost, but it's not a problem for availability.
AWS us-east-2 outage
251–254 of 254 posts
Certain "global" AWS services depend on a specific region (us-east-1 if I recall right) so if that goes down you could be in trouble.
Re: AWS us-east-2 outage
#252Earlier quoted context omitted.
multi az brings multi complexity in terms of data duplication, consistency, if your app wasnt designed to handle those kind of scenarios and experience high users loads then you are in for a lot of problems. designing for those scenarios increase complexity; cost; architecture style and most of the time it will bring you in microservices territory where most of the companies lack experience and just are following bes…
RDS just has a button for multi-AZ primaries. No complexity or microservices.
ok lets say you have a master in one AZ and it dies. what happens?