Add ElastiCache (Valkey) message queue template#1309
Open
vasigorc wants to merge 9 commits intovercel:mainfrom
Open
Add ElastiCache (Valkey) message queue template#1309vasigorc wants to merge 9 commits intovercel:mainfrom
vasigorc wants to merge 9 commits intovercel:mainfrom
Conversation
vasigorc
requested review from
dominiksipowicz,
goncy,
lfades,
lpalmes and
okbel
as code owners
Contributor
|
@vasigorc is attempting to deploy a commit to the Vercel Labs Team on Vercel. A member of the Team first needs to authorize it. |
acarbonetto
reviewed
Nov 27, 2025
Contributor
acarbonetto
left a comment
acarbonetto
left a comment
There was a problem hiding this comment.
Interesting idea, to you message processing instead of a basic API.
| return { | ||
| valid: true, | ||
| data: { | ||
| name: data.name.trim(), |
Author
There was a problem hiding this comment.
Here, like on two lines below, the intent is to trim trailing white spaces/tabs.
Contributor
There was a problem hiding this comment.
Right. But maybe the extra whitespace is desired.
And if not, garbage in, garbage out.
acarbonetto
reviewed
Nov 28, 2025
| // Clear form | ||
| setName('') | ||
| setEmail('') | ||
| setMessage('') |
Contributor
There was a problem hiding this comment.
nit: I'd suggest not clearing the form? But I dont have strong feelings.
acarbonetto
approved these changes
Nov 28, 2025
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
vasigorc
requested review from
a team,
chibicode,
kitfoster,
lazarv and
mknichel
as code owners
vasigorc
force-pushed
the
message-queue-elasticache-clean
branch
2 times, most recently
from
c2490d7 to
b6c014a
Compare
Demonstrates Streams with consumer groups for message queue functionality in Vercel Functions. Includes: - Contact form message producer (POST /api/messages) - Consumer group message processor with XREADGROUP and XAUTOCLAIM (GET /api/messages) - Message acknowledgement endpoint (DELETE /api/messages) - UI components for form submission and message processing - valkey-glide client integration with proper error handling
Co-authored-by: Andrew Carbonetto <andrew.carbonetto@improving.com>
`serverComponentsExternalPackages` moved out of `experimental` in Next.js 15+
getMetadata is not compatible with client components
vasigorc
force-pushed
the
message-queue-elasticache-clean
branch
from
b6c014a to
9e0410f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds a template demonstrating AWS ElastiCache integration for message queue functionality using Redis Streams.
What this template shows
Type of Change
Simple demo flow looks like this:
Screen.Recording.2025-11-25.at.4.13.35.PM.mov
New Example Checklist
npm run new-examplewas used to create the example