Part 5
Performance Engineering
Load testing with k6, JMeter, and Gatling, reading the results correctly, finding the real bottleneck with USE/RED and profilers, and planning capacity with Little's Law.
Everything in this course has limits: connections, IOPS, partitions, heap, a single Redis thread. Performance engineering is how you find those limits BEFORE customers do: generate realistic load, measure the right numbers, find which resource saturates first, fix it, and repeat. It closes the course because it uses everything before it.
- 5.1
Load Testing Fundamentals with k6
BeginnerThe types of performance test, the numbers that matter (throughput, percentiles, errors), open vs closed workload models, coordinated omission, and a k6 test with thresholds that gates CI.
50 min · 5 lab steps · 2 drills
- 5.2
JMeter and Gatling (and When to Use Which Tool)
IntermediateJMeter's thread groups, samplers, and non-GUI runs; Gatling's code-first simulations and injection profiles; distributed load; and choosing between k6, JMeter, Gatling, and Locust.
45 min · 3 lab steps · 1 drills
- 5.3
Finding Bottlenecks and Planning Capacity
AdvancedA repeatable bottleneck workflow, USE and RED methods, Little's Law and the utilisation knee, profilers and flame graphs, the usual suspects in each tier, and capacity planning with headroom.
60 min · 4 lab steps · 2 drills