Backend vs Infrastructure: Where Code Ends and the Systems It Runs On Begin

The article explains the distinction between a backend and infrastructure, framing the backend as the code that runs an app's logic on a server. It describes the backend's responsibilities as handling data, managing identity and authentication, enforcing business rules, and exposing APIs for the frontend. Infrastructure is defined as the servers, databases, storage, and networks that the backend code runs on, which operate independently of what the application does. The author notes that the two layers fail differently, with backend bugs producing wrong behaviour on healthy machines and infrastructure failures occurring when machines are missing, full, or unreachable. A restaurant analogy illustrates the split, comparing the backend to a recipe book and infrastructure to the kitchen.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in