|
|
|
|
|
|
by akrymski
1370 days ago
|
|
|
Caching at the edge could be done by an API gateway or nginx. Geo aware SQL DB sounds like a lot of added complexity. What is the latency trade off in practice? 100ms ping time is probably small compared to query execution time, especially if your backend returns everything the frontend needs in one response. I understand someone at the scale of Amazon wanting to shave ms off page loads. But most web apps? |
|
|
The last web app I worked on had a latency budget of 200ms. The one before that it was 400.
Cross pacific queries can take 200 of that off the top. Even transcontinental is close to 80. With query times you can at least work to improve them.
Now it’s not as simple as just locality but that’s a starting point.