3 ms·
You are assuming that the database is being directly accessed from the end user. If the database is being accessed from within an application running in a data
by btilly 10y ago
You are assuming that the database is being directly accessed from the end user. If the database is being accessed from within an application running in a datacenter, then you only need a database in that datacenter.
2.8 ms to access data within a datacenter is both good and believable. And if I'm building an application, it is a latency figure that matters to me a lot.
- shshhdhs 10y agoYes, OP is assuming that. The popular use-case for a "global DB" is end-users. And the popular definition of geographic network latency is a function of distance & the speed of light, not the speed of which an app talks to the DB.
- jazoom 10y agoIf it's "global" then whichever service provider I choose should see the same latency. If my datacentre is in Brisbane and their closest is Sydney the latency I see will be about 40ms. I wasn't even thinking of the end user.