Backend
BAK-end
The server-side part of an application that handles data, logic, and infrastructure.
The backend is everything that runs on the server: the API endpoints, the business logic, the database queries, the authentication, the background jobs, and the infrastructure. Users never see the backend directly, but every interaction they have depends on it.
The backend is where data lives and business rules are enforced. When a user submits a payment, the frontend sends a request to the backend. The backend validates the payment, charges the card, updates the database, sends a receipt email, and returns a success response. All of that happens invisibly.
Backend engineering is about reliability, correctness, and performance at scale. A frontend bug shows the wrong color. A backend bug charges the wrong amount, loses data, or exposes sensitive information. The stakes are different.
Examples
A backend handles a surge in traffic.
A product launch drives 10x normal API traffic. The backend auto-scales from 5 instances to 50. The load balancer distributes requests evenly. Response times increase from 50ms to 120ms but remain acceptable. No requests are dropped.
A backend bug causes data inconsistency.
A race condition in the order processing backend allows two concurrent requests to deduct inventory for the same item. One customer's order ships successfully. The other gets a backorder notification after payment was already charged. The fix adds a database lock to prevent concurrent deductions.
A backend migration changes databases.
The team migrates from PostgreSQL to a combination of PostgreSQL (for relational data) and Redis (for session storage and caching). The backend code changes, but the API contract stays the same. Frontend developers notice nothing except faster response times.
In practice
Read more on the blog
Frequently asked questions
What languages are used for backend development?
Python, JavaScript/TypeScript (Node.js), Go, Java, Ruby, and Rust are the most common. The choice depends on the team's expertise, performance requirements, and ecosystem needs. Go and Rust are popular for high-performance services. Python and Node.js are popular for rapid development.
What is a backend-for-frontend (BFF)?
A BFF is a backend service specifically designed for a particular frontend. Instead of a generic API serving web, mobile, and partner clients, each client gets its own backend that returns exactly the data it needs in the format it needs. This simplifies the frontend at the cost of more backend services.
Related terms
The part of an application that users see and interact with directly.
Application programming interface: a defined way for software programs to communicate with each other.
A structured system for storing, organizing, and retrieving data.
On-demand computing infrastructure (servers, storage, networking) provided by a third party.
A cloud model where the provider manages all infrastructure and you only pay for actual execution time.
Want the complete playbook?
Picks and Shovels is the definitive guide to developer marketing. Amazon #1 bestseller with practical strategies from 30 years of marketing to developers.