Decide the origin-transport mechanism
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- nextjs, typescript
- Domain
- backend, cloud, distributed-systems
Research direction
Compare the three proposed origin-transport options across Vercel's separate-lambda case and a single self-hosted server, starting with the current per-process in-memory table and the Next.js upstream metadata-slot constraint. Done means a decision record documenting rejected options and estimating the same-instance hit rate on serverless.
Written by the indexing model from the issue text.
Description
Example: the same app on Vercel. The fill runs in lambda 1, the hit is served by lambda 2. The shared cache has the entry, but lambda 2's memory has no record of who filled it (no link). On a single self-hosted server it works.
Solves: whether links exist on the most common deploy target. We should know this before shipping, not after.
Fix idea: compare three options. (a) A per-process in-memory table, which works today but only within one instance. (b) Trace context stored inside the cache entry, which works everywhere but needs a Next.js upstream metadata-slot ask. (c) Both, table now and entry metadata when upstream lands. Deliverable: a decision record with rejected options and an estimate of the same-instance hit rate on serverless.
- Dominant language
- TypeScript
- Stars
- 8.7k
- Forks
- 1.9k
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 543
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from getsentry/sentry-javascript
-
Browser Waiting for: Product Owner
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
getsentry/sentry-javascript#24577 · 1 comment ·
-
Task
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
getsentry/sentry-javascript#24558 · 1 comment ·
-
Task
Difficulty 1/5 Under an hour Newbie friendliness 90/100
getsentry/sentry-javascript#24557 · 1 comment ·
-
Task
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
getsentry/sentry-javascript#24556 · 1 comment ·
-
Task
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
getsentry/sentry-javascript#24555 · 1 comment ·
All issues in getsentry/sentry-javascript
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
dennys-bd/agent-hive#184 ·
-
Add: hunch Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
AbdelStark/awesome-typesafe#104 ·
-
ai-observability bug team/ai-observability
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vicharanashala/fln#563 ·