3 ms·
Question from a newbie to cloud stuff: what is the performance like for a database server that's separated from your host like that? In terms of latency alone
by jfengel 6y ago
Question from a newbie to cloud stuff: what is the performance like for a database server that's separated from your host like that?
In terms of latency alone it sounds like it risks adding tens or even hundreds of milliseconds to even a fairly trivial request: out of my datacenter, across the wire, into theirs, grab the data, and then reverse the path. And perhaps a charge for data going out each way.
Am I wrong about that? Am I overestimating the travel time, or perhaps they end up being located in the same datacenter so it's all high speed?
- benbjohnson 6y agoIt's typical to see at least millisecond latency for a database server that's located in the same data center (e.g. hosting your own Postgres) and tens or hundreds of milliseconds for cloud database services that run outside your data center. The OP's approach of SQLite & Litestream removes that latency entirely since the database is colocated with the application. Litestream will stream backups to an external service (e.g. S3) and that can have tens or hundreds of milliseconds of latency but that won't affect the application's performance since it is asynchronous replication.
- jfengel 6y agoAh, I had misread how that worked. That makes a ton of sense. Thank you.
- webmobdev 6y agowhat is the performance like for a database server that's separated from your host like that? It's not separated. As this diagram shows - https://mtlynch.io/litestream/diagram.jpg https://mtlynch.io/litestream/diagram.jpg - the SQLite database is on the same server as the web application. Additionally, OP's setup seems to use Litestream to backup the SQLite database to some cloud storage.