ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Memory constraint context Vercel Edge Functions enforce a fixed 128 MB memory ceiling per invocation with no configuration option to increase it, unlike Serverless Functions which scale to 3008 MB on Pro plans. The limit is intentional for low-latency V8 isolate workloads, but it creates uncertainty when functions approach the boundary under real traffic pat
We are evaluating whether to move API routes from Vercel Serverless Functions running Node.js 18 or 20 to Edge Functions running on V8 isolates. The goal is to reduce cold-start latency while keeping existing npm packages functional. Edge Functions do not provide Node.js built-ins such as fs, path, crypto, process, or Buffer, and packages with native addons
Goal: Ensure that a write operation retried by the Supabase client does not result in duplicate rows in the underlying PostgreSQL table. The Supabase JavaScript SDK automatically retries failed network requests with exponential back‑off, but it does not deduplicate the corresponding INSERT or UPDATE statements. Developers must therefore rely on database‑leve
Preventing Duplicate Writes During Execution Retries Vercel Serverless Functions may execute multiple times for a single request due to platform-level retries or cold start timeouts. Because the runtime does not natively manage idempotency, write operations to external databases risk duplication if a function is retried after a partial success. There is a de
The goal is to let Vercel Edge Functions automatically convert UTC timestamps to a visitor’s local time zone using information present in the HTTP request, so developers do not need to write custom Intl conversion logic. Constraints include the stateless nature of Edge Functions, which execute in a global CDN and default to UTC for Date.now(), the lack of a
Netlify Edge Functions utilize a Deno-based runtime to execute logic at the network edge, providing native support for TypeScript and JavaScript. This architecture allows for request interception and modification via middleware before a request reaches the origin. Because the runtime is based on Deno rather than Node.js, there is a known discrepancy regardin
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 To display event dates in the user’s local time on a Jamstack site while keeping the build process simple and ensuring SEO friendliness. Constraints & Uncertainty Jamstack sites are pre‑rendered; static pages may hard‑code dates, causing stale or incorrect times when users visit from different time zones. Client‑side conversion via Intl.DateTimeForm
vercel
supabase
netlify
javascript
jamstack