Building server-side systems — from basic CRUD APIs to distributed systems at scale.
Backend Engineering designs, builds, and operates the server-side systems that power applications. Beyond writing API endpoints, it encompasses database design, authentication, caching, message queues, observability, and distributed systems. From handling a single HTTP request to orchestrating services serving millions of users, it has clear growth stages distinct from general programming.
You learn how the web works at the protocol level — HTTP methods, status codes, request/response cycles. Following tutorials, you create simple endpoints that accept requests and return responses. You use API testing tools (e.g., Postman or curl) to test your endpoints and understand how clients communicate with servers. Corresponds to the Dreyfus Novice stage.
What Comes Next
If you've checked off most of this list, you're ready for the Data Builder stage, learning SQL databases, designing RESTful APIs, and implementing basic authentication to build more complete server-side applications. Bandura(1977)'s Social Learning theory suggests watching experienced developers' coding demonstrations and tutorials builds the confidence to tackle these challenges yourself.
The definitive guide to distributed systems, data modeling, replication, partitioning, and consistency — used as the primary knowledge source for defining backend competency from database fundamentals (Level 2) through distributed systems architecture (Level 6).
A global ICT/digital competency framework defining software development skills across 7 responsibility levels (Follow → Set strategy), used to design autonomy, influence, and complexity criteria for the backend engineering checklist.
Curriculum sequences across 17 knowledge areas (Software Engineering, Data Management, Networking, Security, etc.) provide the basis for learning scope and checklist items at each backend engineering level.
A paper by Amazon CTO analyzing eventual consistency models and CAP tradeoffs in distributed systems from a practitioner perspective. Provides empirical evidence for distributed system design, data consistency, and availability tradeoff checklist items at L4–L6.
