Skip to main content

Performance for Full Stack Developers

Full stack performance is making both the page and the API fast. On the frontend that means smaller bundles, optimised images and good Core Web Vitals. On the backend it means efficient queries, indexes, caching, pagination and avoiding the N+1 query problem, with measurements guiding each change.

Stage: Quality and Security · Part of the Full Stack Developer roadmap · Last reviewed 19 November 2026

What to learn in Performance

Performance interview questions

What is the N+1 query problem?

It occurs when code fetches a list with one query, then runs an extra query for each item to load related data, giving N+1 round trips. Fix it with a join, eager loading, or batching so related rows come in one or two queries.

Why use cursor pagination instead of offset pagination?

Offset pagination makes the database skip rows, which gets slower on deep pages and can show duplicates when data changes. A cursor uses the last seen key, so queries stay fast with an index and results remain stable.

Where Performance fits in the Full Stack Developer roadmap

Performance belongs to the Quality and Security stage (beginner level), which takes about 5 hours. Test it and protect it.

Back to the full Full Stack Developer roadmap