Learning note / Reflections on my studies
Computer Networks
Networking gives me a way to reason about the journey between a client and a service. It makes an unavailable website a sequence of questions to investigate instead of a single vague problem.
Following a connection layer by layer
I start by separating the name of a service from its address, the route to that address, and the application listening at the destination. Those are related, but a failure in one does not prove a failure in the others.
That separation helps me choose a more useful next check.
Different delivery needs
TCP and UDP help me think about what an application needs from communication. Reliable delivery, ordering, overhead, and timing matter differently depending on what the application is trying to do.
The useful part is understanding the trade-off, rather than memorizing which protocol is supposedly better.
Connecting networks to application work
When I look at an API request, I can now consider more than the code at either end. Name resolution, addressing, ports, and application responses each explain a different part of the behavior. It is a useful foundation for development and technical support.
What I take forward
- Separate naming, connectivity, and application behavior.
- Choose checks that narrow the problem.
- Relate protocol choices to application needs.