A Beginner’s Journey into HTTP, Load Testing, and Observability

warningEverything in this post was built purely for curiosity, learning, and research purposes.
I’m not a networking or infrastructure expert. The environment was intentionally simple and exploratory.
AI was used as a learning and research assistant, helping to speed up understanding and experimentation.
Introduction
I’m not a networking or infrastructure expert. This experiment started from a very simple and honest question:
How does HTTP really work in practice when requests hit a server, pass through a reverse proxy, are stressed by load tests, and are explained through metrics?
This work was driven by curiosity and hands-on learning. There was no production goal, no attempt at performance optimization, and no claim of best practices. The goal was to understand behavior by building, breaking, measuring, and observing.
To answer that question, I built a small but realistic local environment using common tools. The focus was:
- Understanding HTTP request flow
- Learning how reverse proxies behave
- Generating realistic load
- Observing system behavior via metrics

