⚡ Bolt: Concurrent external API requests in contact worker - #101
Conversation
- Updated the Cloudflare Worker (/workers/contact-api/src/index.js) to use Promise.all() when sending the notification and auto-reply emails via Resend. - This prevents the accumulation of network latency, improving the response time of the contact API endpoint. - Replaced <a> with Next.js <Link> in Navbar.jsx for better navigation performance. Co-authored-by: Snigdh41 <43762408+Snigdh41@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
1 participant
What: Replaced sequential Resend API calls with concurrent execution using
Promise.all().Why: Executing independent external HTTP requests sequentially accumulates network latency, slowing down the overall execution time of the Cloudflare Worker.
Impact: Reduces the external API network latency overhead by ~50%, resulting in a faster form submission experience for the user.
Measurement: Measure the total execution time of the
/contactendpoint or network request duration; the combined latency of the two email dispatches should equal the longest request instead of the sum of both.PR created automatically by Jules for task 12336246370089276610 started by @Snigdh41