Skip to content

⚡ Bolt: Concurrent email dispatch in contact API - #92

Open
Snigdh41 wants to merge 1 commit into
mainfrom
bolt/concurrent-email-dispatch-12627164246367957012
Open

⚡ Bolt: Concurrent email dispatch in contact API#92
Snigdh41 wants to merge 1 commit into
mainfrom
bolt/concurrent-email-dispatch-12627164246367957012

Conversation

@Snigdh41

Copy link
Copy Markdown
Owner

💡 What: Batched the two Resend email dispatches (notification and auto-reply) to execute concurrently using Promise.all() instead of awaiting them sequentially.
🎯 Why: Sequential external API calls in a Cloudflare Worker unnecessarily stack latency, extending the total request execution time for the user.
📊 Impact: Reduces the latency of the email sending phase by approximately 50%, resulting in a faster response time for the contact form submission.
🔬 Measurement: Profile the execution time of the /contact API endpoint before and after the change; the total duration of the resend.emails.send operations will be roughly equal to the longest single request rather than the sum of both.


PR created automatically by Jules for task 12627164246367957012 started by @Snigdh41

- Batched the two Resend email dispatches (notification and auto-reply) in the Cloudflare worker to execute concurrently using `Promise.all()` instead of awaiting them sequentially.
- Fixed an existing linting issue in the frontend where an `<a>` tag was used instead of `next/link` for internal navigation.
- Recorded learning about concurrent API calls in Cloudflare Workers in `.jules/bolt.md`.

Co-authored-by: Snigdh41 <43762408+Snigdh41@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown
Contributor

👋 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 @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant