Designing and running the server-side systems behind an app — APIs, databases, caching, and 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.
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.