ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
When designing a Netlify site that must handle sudden spikes in request volume, engineers need to pick between deploying the logic as an Edge Function or as a traditional Serverless Function. The decision hinges on how each platform’s concurrency limits affect latency when traffic exceeds the allowed simultaneous invocations. Edge Functions are limited to 10
Goal Determine the exact precedence order Netlify Dev uses when resolving environment variables for both Netlify Functions (Node.js) and Edge Functions (Deno) during local development, so that integration tests can reliably mirror production behavior without deploying. Constraints and uncertainty Netlify Dev sources variables from a local .env file, the link
A JAMstack configuration is being designed where a static site generator pre-renders pages at build time and the site relies on serverless functions for request-time data. The integration boundary is between the SSG build process and the serverless function runtime. Local builds commonly use .env.local for configuration, while production hosts require enviro
netlify
jamstack