The TRUTH About JavaScript At the Edge with Databases

The Edge DOESN'T FIX EVERYTHING. Deploying to the edge can only bring performance benefits when used in the right way with the right tools. This is especially true when taking into account your database. To get the most benefit, your database has to be built to support the edge!

**DISCORD**

**STAY IN TOUCH 👋**

**QUESTIONS ABOUT MY SETUP**

**TIMESTAMPS**
00:00 - Intro
00:30 - Existing Deployment Architecture
01:30 - Edge Deployment Architecture
03:00 - The Problem With Deploying to the Edge
04:50 - Introduction to Turso (Sponsor)
05:30 - Creating and Testing a Database with Turso
09:05 - Creating and Testing a Database Replica
11:00 - Logical Database URLs and Its Benefits
12:00 - Writing to Databases at the Edge
14:30 - Wrap Up

[christopheanfry]

Didn’t use the edge yet but it’s true, no need to deploy on the edge of the database is only in one location. Amazing Turso to give the opportunity to have instances of the database all around the world. My question is what will happen if there are many many read request while one user is writing? Could it affect the data sent back after multiple requests in different locations ?