- 新しい順
- 投票が多い順
- コメントが多い順
There's probably a lot more discussion to be had on this particular question - mainly because each option you choose will have an impact on the rest of your design.
If it were me, I'd go with option 2. Given that the two regions are (by the sounds of it) operating independently anyway; and you want any impact to one region not to affect the other then having separate API Gateways (and the infrastructure behind that) is a good idea. It assumes that you have a method for reliably replicating the data between the two regions but otherwise it's the way I'd go.
The particular can of worms this open is: What does the client do? If the client uses DNS and is directed to region A which is having an outage of some sort then it has to figure out there is an issue and choose to go to region B (somehow).
If you go and look at the various Netflix engineering blogs and YouTube talks that's what they do; the back end infrastructure operates independently in three regions and there is a lot of intelligence in the client to figure out which region it should talk to in order to continue serving content. In particular, look at their posts around the Simian Army (Chaos Monkey/Gorilla/Kong) to see how they test that.
For a lot of other really good content check out the Amazon Builder's Library which has lots of advice from our experience.
And finally, reach out to your local AWS Solutions Architect to continue this discussion - there are going to be more questions and (I suspect) more opinions about the right way to go.