Perhaps his most striking contribution is the demystification of storage engines. Nasser argues that you cannot effectively scale a backend if you don't know how your database writes to disk.
The material is structured around several critical domains that bridge the gap between high-level application code and low-level system behavior. How to Become a Good Backend Engineer (Fundamentals)
He is famous for his "backend trade-off" scenarios. He rarely gives a "correct" answer. Instead, he presents a scenario— a chat application with spotty internet connection —and asks the student to choose. REST? Maybe too chatty. gRPC? Great for binary data, but how’s the browser support? WebSockets? Good, but how do you handle reconnection logic? fundamentals of backend engineering hussein nasser
Backend engineering is avoiding O(n) memory scaling.
Synchronous vs. Asynchronous. REST vs. gRPC vs. GraphQL. WebSockets. Nasser treats these not as buzzwords to be listed on a resume, but as tools in a toolbox with specific trade-offs. How to Become a Good Backend Engineer (Fundamentals)
Security is a top priority in backend engineering. Hussein Nasser highlights the importance of:
Hussein Nasser’s work is a pushback against this commoditization. He argues that when the abstraction leaks—as it always does—only the engineer who understands the fundamentals can fix it. When the database locks up, or when the API latency spikes at the 99th percentile, no amount of cloud configuration menus will save you. You need to understand the bits, the bytes, the protocols, and the disk seeks. You need to understand the bits
The "Fundamentals of Backend Engineering" is not a quick fix. It is a heavy lift. It requires sitting through diagrams of TCP handshakes and understanding how an operating system handles a file descriptor.