Software Engineering Roadmap

Learn how to build, test, deploy, and maintain robust software systems.

Overall Progress0%

Backend Fundamentals

Explanation

The backend is the part of an application that runs on a server. When the frontend needs data or needs to perform an action, it sends a request over HTTP to the backend, which processes it, talks to a database or external service, and sends a response back. This lesson introduces the core ideas of backend development: what a server is, how HTTP requests and responses work, how routes map URLs to handlers, how middleware sits in the middle of every request, and how configuration and secrets should be managed safely. The examples use FastAPI (Python) and Express (Node.js) as representatives, but the concepts — routing, middleware, environment variables, error handling, and logging — are the same in every backend framework.

What Is Backend Development?

Frontend (client)

↓

HTTP request

↓

Backend (server)

↓

Database / external services

↓

HTTP response

The client sends a request; the server processes it, may read or write data, and returns a response.

What Is a Server?

A server is a program that listens on a port for incoming requests.
It accepts a request, processes it, and returns a response.
Many frameworks let you define handlers for specific routes.

HTTP Request and Response

Part	Meaning
Method	What action to perform (GET, POST, ...)
URL / path	Which resource or route
Headers	Metadata (content type, auth, ...)
Body	The data being sent
Status code	The result (200 OK, 404, ...)
Response body	The returned data

Server Routing

A route maps an HTTP method and a path to a handler function. Different paths and methods run different handlers.

text

1GET  /users      → list users2POST /users      → create a user3GET  /users/123  → fetch one user

Middleware

Middleware is code that runs before the route handler, for every request (or a group of them). It sits in the middle of the request pipeline.

Request

↓

Middleware 1

↓

Middleware 2

↓

Route handler

↓

Response

Logging requests
Authentication and authorization
Validation
CORS handling
Error handling
Transforming the request or response

The Request Lifecycle

Incoming request

↓

Middleware

↓

Routing

↓

Validation

↓

Business logic

↓

Database / service

↓

Response

↓

Error handling if needed

Business Logic and Layers

A route handler should stay thin. Real logic belongs in a service layer, and data access belongs in its own layer. This separation keeps code testable and maintainable.

Controller / route (HTTP concerns)

Service (business logic)

Data access (database)

Environment Variables and Secrets

Configuration such as database URLs and API keys must not live in source code. They belong in environment variables (commonly loaded from a .env file) so they can differ between environments and stay out of version control.

Configuration by Environment

Environment	Purpose
Development	Local, with debug tooling
Staging	Mirrors production for testing
Production	Live, real users

Error Handling and Logging

Handle errors centrally so failures return consistent responses. Log useful context (request, timestamp) but never secrets or sensitive user data.

Security Basics

Validate all input.
Distinguish authentication from authorization.
Keep secrets out of source control.
Rate-limit expensive or public endpoints.

Syntax

A small FastAPI server with middlewarepython

1import os2from fastapi import FastAPI, Request3 4app = FastAPI()5 6@app.middleware("http")7async def log_requests(request: Request, call_next):8    print(f"{request.method} {request.url.path}")9    return await call_next(request)10 11@app.get("/health")12def health():13    return {"status": "ok", "env": os.getenv("APP_ENV", "development")}

The middleware runs before the route handler. Secrets and configuration come from environment variables, not the code.

Examples

Reading configuration safely

Read a value from the environment with a fallback default.

python

1import os2DB_URL = os.getenv("DATABASE_URL")3if not DB_URL:4    raise RuntimeError("DATABASE_URL is required")

Output

(raises if DATABASE_URL is not set)

A middleware pipeline

Each request passes through middleware before reaching the handler.

text

1request → auth middleware → logging middleware → route → response

Output

(the handler only runs after middleware passes)

Key Takeaways

The backend runs on a server and answers client requests over HTTP.
Routes map an HTTP method and path to a handler.
Middleware runs before handlers for logging, auth, and validation.
Business logic belongs in a service layer, not the route handler.
Secrets and configuration live in environment variables, never in code.

← PreviousFrontend Frameworks Next →RESTful APIs