You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For sites that need the full Node runtime or have some other reason to use regional Lambda rather than AWS or Cloudflare edge, it can still be beneficial to have a bit of multi-region for latency. For example, us-east, us-west, eu. There needs to be some glue between the single CloudFront distribution and the multiple copies of the server Lambda (to use a Nextjs example). Could this be Route53 or is Global Accelerator (expensive 👎 ) the only viable option? I'm not sure.
Yes @jayair, but in the context of the higher level SST components like the Nextjs server function. Not even Vercel offers this, though they just introduced a 'fallback region' for enterprise tier.
Just brainstorming here:
For sites that need the full Node runtime or have some other reason to use regional Lambda rather than AWS or Cloudflare edge, it can still be beneficial to have a bit of multi-region for latency. For example, us-east, us-west, eu. There needs to be some glue between the single CloudFront distribution and the multiple copies of the server Lambda (to use a Nextjs example). Could this be Route53 or is Global Accelerator (expensive 👎 ) the only viable option? I'm not sure.
ION-211
The text was updated successfully, but these errors were encountered: