Database Hosting: How Latency Is Handeled?

I read some things about hosted (aka cloud) databases. For example, Cloudant offers a hosted CouchDB database or Cassandra.io offers a Cassandra hosted. I understand why these services solve some problems.

My question is: Why do these services work? I believe that I host my own application on my own servers (or somewhere on the cloud-hosting-platform) and use one of these services to store my data. For each database request (both for reading and writing) I need to pay a full circuit over the Internet (if my application is not located in the same place as my database cloud provider). Why don't these killings kill me? . When we think about SQL, each query will cost another x * 10 ms for the network only, without wasting time.

How is this problem resolved? Or are these services not suitable for applications that need quick answers and can only be used for data processing, where latency is not a problem?

+5
source share
1 answer

typically, the physical hosts of hosted databases are typically located in major data centers (such as AWS). To reduce network latency, customers can choose whether to host their application on servers located in the physical data center where the hosted databases are located.

Most high-performance applications and / or websites that do not use hosted database services typically support their application servers and their database servers on different hosts for performance reasons. So, in short, switching to a hosted database service does not necessarily increase network latency.

+1
source

All Articles