CTRL ALTSCtrl Alt Solvereal-world developer knowledge
SearchJoin
Ctrl Alt Solve — Don't just ask what to do. Learn what developers experienced when they did it.

Developer experience network

Ctrl Alt Solve

Real-world experiences, production lessons, and structured discussions — knowledge that goes beyond tutorials.

Search

Explore by technology

Open an experience to follow topics you care about.

#postgres·10#migration·5#opentelemetry·5#api·5#architecture·5#observability·5#auth·5#devtools·5#nextjs·5#dx·5#typescript·5#slack·5#debugging·5#webhooks·5#leadership·5#ci·5

Experience feed

Unread-first ranked posts for #nextjs

DiscoverLatestFor you
AllQuestionExperienceDiscussionComparisonCase studyLearningProblem solvingRecommendationShowcaseCareer
Experience5d ago·1 entry

broke when we moved auth to the edge

We moved session checks to the edge to cut latency on every page load. It worked in staging, then failed on preview deploys when cookies crossed domains. Clock skew between edge and origin made short-lived tokens look expired. We fixed cookie domains per environment and added skew-tolerant expiry. Median auth path dropped about 120ms, with fewer cold-start surprises. Lesson: test cookies across every environment before calling a migration done.

2 views0 likes0 comments0 bookmarks
#auth#nextjs#edge
MMaya Chen
Read →
Experience5d ago·1 entry

broke when we moved auth to the edge

We moved session checks to the edge to cut latency on every page load. It worked in staging, then failed on preview deploys when cookies crossed domains. Clock skew between edge and origin made short-lived tokens look expired. We fixed cookie domains per environment and added skew-tolerant expiry. Median auth path dropped about 120ms, with fewer cold-start surprises. Lesson: test cookies across every environment before calling a migration done.

1 views0 likes0 comments0 bookmarks
#auth#nextjs#edge
MMarcus Webb
Read →
Experience14d ago·1 entry

broke when we moved auth to the edge

We moved session checks to the edge to cut latency on every page load. It worked in staging, then failed on preview deploys when cookies crossed domains. Clock skew between edge and origin made short-lived tokens look expired. We fixed cookie domains per environment and added skew-tolerant expiry. Median auth path dropped about 120ms, with fewer cold-start surprises. Lesson: test cookies across every environment before calling a migration done.

5 views0 likes0 comments0 bookmarks
#auth#nextjs#edge
PPriya Nair
Read →
Experience25d ago·1 entry

broke when we moved auth to the edge

We moved session checks to the edge to cut latency on every page load. It worked in staging, then failed on preview deploys when cookies crossed domains. Clock skew between edge and origin made short-lived tokens look expired. We fixed cookie domains per environment and added skew-tolerant expiry. Median auth path dropped about 120ms, with fewer cold-start surprises. Lesson: test cookies across every environment before calling a migration done.

6 views0 likes0 comments0 bookmarks
#auth#nextjs#edge
EEthan Brooks
Read →
ExperienceSep 29, 2026·1 entry

broke when we moved auth to the edge

We moved session checks to the edge to cut latency on every page load. It worked in staging, then failed on preview deploys when cookies crossed domains. Clock skew between edge and origin made short-lived tokens look expired. We fixed cookie domains per environment and added skew-tolerant expiry. Median auth path dropped about 120ms, with fewer cold-start surprises. Lesson: test cookies across every environment before calling a migration done.

3 views0 likes0 comments0 bookmarks
#auth#nextjs#edge
HHannah Kim
Read →

You are all caught up.