How do you run a zero-downtime deploy for a Node API and React SPA?
PICTURE THIS: DATA SPLIT
Fit on train, tune on val, report on test once.
Simple meaning
Build static assets, health-check new API instances, drain old ones, then point CDN to new files.
WHY — Deploy instead of guessing?
Why interviewers care about Deploy:
question about Deploy.
trade-offs, and what you would actually do on a Full Stack project - not buzzwords.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1Build static assets, health-check
new API instances, drain old ones, then point CDN to new files.
- 2Sticky sessions or shared
session store matter.
- 3I smoke-test critical flows
after cutover.
- 4Give an example
One tiny concrete case you can say aloud.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
Build static assets, health-check new API instances, drain old ones, then point CDN to new files. Sticky sessions or shared session store matter.