Timeline for Trade offs of putting an international master database in us-west-2
Current License: CC BY-SA 4.0
18 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 26, 2019 at 1:58 | comment | added | Michael - sqlbot | @030 sorry I haven't gotten back with an answer, yet. I'm trying to make it relevant to the general audience and explain how I modeled this. | |
| Dec 25, 2019 at 9:15 | comment | added | 030 | @Chris Ok. Thanks for posting an answer. | |
| Dec 25, 2019 at 9:08 | comment | added | Chris | Sure @030 I've done this now. I won't mark as the correct answer though as I think some kind of metric based answer would be ideal. | |
| Dec 25, 2019 at 9:07 | answer | added | Chris | timeline score: 1 | |
| Dec 24, 2019 at 14:09 | history | edited | 030 |
edited tags
|
|
| Dec 24, 2019 at 12:52 | comment | added | 030 | @Chris Could you post this comment as an answer? | |
| Dec 23, 2019 at 15:05 | comment | added | Chris | @030 I can offer my experiences since asking the question, albeit it's a subjective view as I have no quantitative data. I can offer that a year and a half later, I haven't regretted my decision putting the master into us-west-2. Our users in any region don't seem to be impacted by having the master in us-west-2, at least from a UX perspective. I suppose at some point it could be worth measuring write times -- but to date I haven't had to. There's no business impact from any latencies due to the location of the master, that we can detect at least, so we're happy here. | |
| Dec 23, 2019 at 10:29 | comment | added | 030 | @Michael-sqlbot Could you post an answer? | |
| Jun 29, 2018 at 9:57 | comment | added | Michael - sqlbot | Thanks... I'm trying to think of a way to transform it into an answer that would be useful to others. I'll see what I can come up with. | |
| Jun 29, 2018 at 2:02 | comment | added | Chris | @Michael-sqlbot I can't thank you enough for looking at this for me. Sounds like you've really put thought into your model, and I'll accept this information as enough rationale to start off with those regions. If you wanted to put your comment there into an answer, I'll accept it and perhaps it will help the next person in a similar situation. Thanks very much! | |
| Jun 29, 2018 at 0:06 | comment | added | Michael - sqlbot | Nice... My model agrees that us-west-2 is the best choice, followed by us-west-1, us-east-2, then eu-central-1. The logic I used is slightly tricky to explain, but it is based on which region would be the closest, then the next closest, then the next closest, from each of your three... us-west-2 is its own 0th preference, of course; eu-central-1 has 6 regions closer than us-west-2, and ap-southeast-2 has 8 regions closer than us-west-2, but (0 + 6 + 8) / 3 is still a smaller (better) possible result of any other combo, even if we allow for the db itself to be in a region other than these 3. | |
| Jun 28, 2018 at 1:33 | comment | added | Michael - sqlbot | Something else to consider is that depending on the nature of the writes to the db, it can also make sense to shift some of the latency burden away from the app... e.g. app in ap-southeast-2 hands off the write to SNS in the same region, which asynchronously invokes Lambda cross-region, which does the DB update. The propagation time is higher, but the app doesn't have to wait for the write to complete. Obviously this is only suitable for non-critical writes, but it's a thought. | |
| Jun 28, 2018 at 1:26 | comment | added | Michael - sqlbot | I've collected a matrix of cross-region latency data for a project I've been working on... I'll plan to look at that model tomorrow and see what it thinks about the selection of us-west-2 for this scenario, or whether it recommends something different. | |
| Jun 28, 2018 at 1:15 | comment | added | Chris |
Thanks @Michael-sqlbot, I am planning to deploy the master RDS into us-west-2, with read replicas and web server instances running in ap-southeast-2 and eu-central-1. I understand the open ended-ness of this, but having not created this specific setup before, I figure any information I can gather the better. The design will allow me to change the RDS region for the master if required.
|
|
| Jun 27, 2018 at 12:19 | comment | added | Michael - sqlbot | Remember also that RDS will only manage 5 replicas of a Postgres instance. Unlike with MySQL and MariaDB, RDS apparently won't let you work around this using cascaded/subtended replicas. | |
| Jun 27, 2018 at 12:18 | comment | added | Michael - sqlbot | You should, of course, design the application so that you can easily change this if the theoretical calculations don't align with reality... but this does seem like a question with an objective solution. Can you list the specific regions where you're planning to deploy? | |
| Jun 27, 2018 at 1:52 | review | First posts | |||
| Jun 27, 2018 at 3:55 | |||||
| Jun 27, 2018 at 1:47 | history | asked | Chris | CC BY-SA 4.0 |