Hussein Nasser: Backend Engineering

What the channel actually covers

Hussein Nasser runs one of the best known backend engineering channels on YouTube. The videos go below the "boxes and arrows" level of most system design content and into how things behave on the wire and on disk:

• Networking and protocols: TCP, UDP, HTTP/1.1, HTTP/2, HTTP/3 and QUIC, TLS handshakes, WebSockets, gRPC and long polling.
• Proxies and load balancers: layer 4 versus layer 7 balancing, reverse proxies, NGINX and HAProxy behaviour.
• Databases: indexes, query plans, B-trees, isolation levels, locking, replication and sharding, mostly with PostgreSQL examples.
• Operating system behaviour that backend code depends on, such as sockets, threads and the kernel's role in I/O.
• Commentary on real incidents and engineering posts, where he reads a company write up and explains what actually happened.

Most videos are long and unscripted in feel: he thinks out loud, draws diagrams and often runs a small demo.

Is it worth your time?

Yes, if you already write backend code. The value is not in memorising facts but in being able to answer "what does this cost?" You stop saying "add a cache" and start saying what the cache costs on a write heavy path, which invalidation approach you would pick and why a connection pool size matters. That depth is exactly where design discussions and code reviews get tested.

It is less useful as a first introduction to programming or web development. The channel assumes you know what an HTTP request, a database table and a server process are.

Free videos versus the paid courses

Everything on YouTube is free. He also sells structured courses (on Udemy and through his own site) on topics such as fundamentals of backend engineering, networking, database engineering, operating systems and NGINX. The paid courses are more organised and sequenced; the free videos cover much of the same ground in a looser order. A sensible approach is to use the free channel first and only buy a course if you want one topic taught end to end. Check the course pages for current prices, since Udemy discounts change often.

There is also a podcast, The Backend Engineering Show, which is largely the audio of the YouTube videos. It works well for commutes on topics that do not need diagrams.

How to use it well

• Do not binge the channel from newest to oldest. Search it for the thing you are working on (for example "connection pooling" or "Postgres index") and watch that.
• Watch at normal speed with a terminal open. Reproduce the demo: run curl -v, open Wireshark, run EXPLAIN ANALYZE on your own table.
• After each video, write two or three sentences explaining the idea in your own words. If you cannot, rewatch the middle part.
• Pair a protocol video with the matching chapter of a book such as Designing Data-Intensive Applications for the theory behind it.

Weak spots

• Videos are long and sometimes wander. If you want a tight ten minute explanation, other channels are faster.
• Opinions are strongly stated. Treat hot takes on specific technologies as one engineer's view, not settled fact.
• Coverage is uneven: excellent on networking and PostgreSQL, thinner on cloud managed services and frontend topics.

Common questions

Is it good for system design interviews? It is good for the depth behind them. Pair it with a structured design course for the interview format itself.

Do I need a computer science degree to follow it? No, but you need to have built at least one small backend service.

Where should a beginner start? His videos on HTTP, TCP and database indexing are the most approachable entry points.

Best for: backend developers with some experience who want to understand the systems they configure every day.