Server-side for Full Stack Developers
Server-side development is writing the code that receives requests, applies business rules and returns data. Node.js runs JavaScript outside the browser, and a framework such as Express or Fastify structures routes and middleware. APIs follow REST or GraphQL, and background jobs and webhooks handle work outside a request.
Stage: Backend and Data · Part of the Full Stack Developer roadmap · Last reviewed 19 November 2026
What to learn in Server-side
- Build REST endpoints with routing, middleware and error handling
- Design resource URLs, status codes and pagination for an API
- Compare a GraphQL schema with equivalent REST endpoints
- Queue a slow task to run in a background worker
- Verify a webhook signature and process it idempotently
Server-side interview questions
What is middleware in Express?
Middleware is a function that receives the request, response and next callback and runs between the incoming request and the final handler. It is used for logging, parsing bodies, authentication and error handling, and runs in the order registered.
Why must webhook handlers be idempotent?
Providers retry deliveries when they do not get a quick success response, so the same event can arrive more than once. Storing event IDs and skipping those already processed prevents double charges, duplicate emails or repeated records.
Where Server-side fits in the Full Stack Developer roadmap
Server-side belongs to the Backend and Data stage (beginner level), which takes about 9 hours. Services, APIs and storage.
Other units in this stage
Back to the full Full Stack Developer roadmap