You're still restricted by physics with edge computing. If you need to make a call back into us-east-1 to get data out of a data store, it doesn't matter that there's an edge CDN and API layer.
Outside of that, there's compliance reasons too. Partitioning your data by region because storing customer information in say the EU is different than the US. More likely CN is much different than the rest of the world if you do business there.
Comments
Depends on your architecture.
You're still restricted by physics with edge computing. If you need to make a call back into us-east-1 to get data out of a data store, it doesn't matter that there's an edge CDN and API layer.
Outside of that, there's compliance reasons too. Partitioning your data by region because storing customer information in say the EU is different than the US. More likely CN is much different than the rest of the world if you do business there.
It does in fact matter that your tcp packets are roundtripping over lower rtt connection even if you do have to fetch from the origin