Web architecture is the organization of a web application into building blocks (interface, server, database, external services) and the way those blocks communicate. It is decided early, because it shapes performance, security, hosting costs and how easily the product can evolve.
The basic pattern stays the same: a front end in the browser or on mobile, calling a back end through APIs, which reads from and writes to one or more databases. Around it come a cache, a message queue, a CDN, authentication or payment services.
The structural choices concern how the system is split (monolith or microservices), where rendering happens (server side or client side), hosting (servers, containers, serverless) and how load growth is handled. There is no good architecture in absolute terms: a startup looking for its market does not have the same needs as a platform with millions of users.
Why it matters when hiring
Architecture choices weigh for years, which is why the first tech hires (CTO, founding engineer, tech lead) matter so much. In an interview, ask the candidate to draw the architecture of a product they built and justify each choice. The strong signal: they talk about constraints and trade-offs. The trap: someone who immediately proposes an architecture built for a scale you do not have.
