Comparison questionHard~10 min

Interview question

How do you choose between the Node.js and Edge runtimes in Next.js?

Chooses runtime from dependency, data locality, feature, latency, and deployment constraints instead of fashion.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

Node.js is the default runtime and supports the full Node API and the broadest package compatibility. The Edge runtime exposes a smaller web-standard API surface and some Node-dependent packages will not work; it also does not support ISR. I choose Edge only when its placement and constraints provide a measured benefit for lightweight request work, not as a default performance label.

Full answer below

Practice focus

Node and Edge runtimes, API compatibility, ISR, streaming, packages, data locality, and deployment evidence.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Overview
A theoretically close runtime is not faster when its dependencies, database, or required APIs live elsewhere.
Node.js is the default runtime and supports the full Node API and the broadest package compatibility. The Edge runtime exposes a smaller web-standard API surface and some Node-dependent packages will not work; it also does not support ISR. I choose Edge only when its placement and constraints provide a measured benefit for lightweight request work, not as a default performance label.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
The decision includes database location, connection strategy, authentication library, native dependencies, response streaming, cold starts, and the hosting adapter's actual runtime support. Moving code to an edge location while every request crosses back to a regional database can increase latency. I keep heavy SDKs and Node-only modules out of edge bundles and test the production artifact, because development polyfills can hide incompatibility. Proxy has its own supported runtime choices and should remain lightweight whichever runtime is selected.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
I benchmark end-to-end latency at representative geographies and include dependency calls, not just handler execution. Operational differences matter too: logs, tracing, resource limits, cache consistency, and incident debugging must work on the chosen platform. A route can stay on Node while static assets and a CDN serve globally, which often captures most of the benefit without runtime fragmentation. I document why each exception uses Edge and add a compatibility test so a package upgrade cannot silently introduce unsupported APIs.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Assuming Edge is always faster because it is geographically distributed.
Importing Node-only or native packages into an edge route.
Ignoring the location of the authoritative database.

Red flagsCandidateRed flagsSignals that an interviewer may treat as risky.Open details

Details

Runtime choice is based on a benchmark without dependencies.
Production fails on an API that development appeared to polyfill.
The team cannot trace or debug the edge execution path.

Follow-up prompts

Quick interviewer prompts inside this drill.

Follow-up questionsCandidateFollow-up questionsLikely next questions after the main answer.Open details

Details

Treat these as the next interviewer turn. Answer one out loud, then save the gap in your practice notes.

Does Edge support ISR?
How does data locality affect the choice?
Can a mostly Node application still be globally fast?

Continue practice

Move to the linked follow-up, next path step, prerequisite, or deeper variant.

1 linked

Next interviewer turn

Continue the conversation with a linked follow-up drill.

Async route APIsAdds runtime constraints to request-bound route code.

Practice route

Read core answer Review checklist Follow-up prompts Track progress

Finished this drill?

Practice freely. Sign in only when you want to save completion, confidence, notes, or bookmarks.

New to Aporeon? Create account

Drill details

Human editorial direction

Aporeon is shaped by Aleksandar Tomovski, a software developer with experience on both sides of technical interviews. Content is reviewed for accuracy, natural spoken delivery, useful depth, and honest trade-offs.

About the creator Editorial standards

Was this drill useful?

Help improve the interview library.

Found this answer useful?

Say thanks with a standalone, one-time $5 contribution. No account required.

No subscription or perks.Choose another amount

Opening drill

Comparison questionHard~10 min

Interview question

How do you choose between the Node.js and Edge runtimes in Next.js?

Chooses runtime from dependency, data locality, feature, latency, and deployment constraints instead of fashion.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

Full answer below

Practice focus

Node and Edge runtimes, API compatibility, ISR, streaming, packages, data locality, and deployment evidence.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Overview
A theoretically close runtime is not faster when its dependencies, database, or required APIs live elsewhere.
Node.js is the default runtime and supports the full Node API and the broadest package compatibility. The Edge runtime exposes a smaller web-standard API surface and some Node-dependent packages will not work; it also does not support ISR. I choose Edge only when its placement and constraints provide a measured benefit for lightweight request work, not as a default performance label.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
The decision includes database location, connection strategy, authentication library, native dependencies, response streaming, cold starts, and the hosting adapter's actual runtime support. Moving code to an edge location while every request crosses back to a regional database can increase latency. I keep heavy SDKs and Node-only modules out of edge bundles and test the production artifact, because development polyfills can hide incompatibility. Proxy has its own supported runtime choices and should remain lightweight whichever runtime is selected.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
I benchmark end-to-end latency at representative geographies and include dependency calls, not just handler execution. Operational differences matter too: logs, tracing, resource limits, cache consistency, and incident debugging must work on the chosen platform. A route can stay on Node while static assets and a CDN serve globally, which often captures most of the benefit without runtime fragmentation. I document why each exception uses Edge and add a compatibility test so a package upgrade cannot silently introduce unsupported APIs.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Assuming Edge is always faster because it is geographically distributed.
Importing Node-only or native packages into an edge route.
Ignoring the location of the authoritative database.

Red flagsCandidateRed flagsSignals that an interviewer may treat as risky.Open details

Details

Runtime choice is based on a benchmark without dependencies.
Production fails on an API that development appeared to polyfill.
The team cannot trace or debug the edge execution path.

Follow-up prompts

Quick interviewer prompts inside this drill.

Follow-up questionsCandidateFollow-up questionsLikely next questions after the main answer.Open details

Details

Treat these as the next interviewer turn. Answer one out loud, then save the gap in your practice notes.

Does Edge support ISR?
How does data locality affect the choice?
Can a mostly Node application still be globally fast?

Continue practice

Move to the linked follow-up, next path step, prerequisite, or deeper variant.

1 linked

Next interviewer turn

Continue the conversation with a linked follow-up drill.

Async route APIsAdds runtime constraints to request-bound route code.

How do you choose between the Node.js and Edge runtimes in Next.js?

Practice focus

Answer path

Overview

Review signals

Follow-up prompts

Continue practice

Next interviewer turn

How do you choose between the Node.js and Edge runtimes in Next.js?

Practice focus

Answer path

Overview

Review signals

Follow-up prompts

Continue practice

Next interviewer turn