Traffic 101: Packets Mostly Flow

Cool article! A little feedback for the authors, if they read this: PoPs is used in the first non-intro paragraph and thereafter, but not defined until nearly the end. A reader _could_ find the definition by clicking the link from the first mention, but (IME) it is preferable to provide the expansion in-line (as you did with, say, AZ) at first usage so users do not have to "click out"

EDIT: and, for any potential smart-arse who points out that I did not expand "IME" - TBH, that rule does not hold value (IMO) for abbreviations that are widely-known, e.g. "AWS", etc.

the SHED_LOAD thing offered by ns1 looks cool. anyone have experience with it? https://help.ns1.com/hc/en-us/articles/360020683413-Configur.... seems like something juicy missing from route53. ns1 even has an integration with cloudwatch (not to say cloudwatch is great) as a source for the load stats.

it seems obvious at the level of like an individual load balancer to consider the load of the nodes backing an upstream when it decides which one to send reqs to. i didn't think of lifting that to the record that points to the load balancers.

i'm trying to think how you'd do it with route53. maybe with health checks that take load into account? i don't think you'd get the low and high watermarks like in ns1s thing. maybe a weighted record with something wired up to to tweak weights based on load? sounds just annoying enough to get right and working safely that if route53 implemented it well, people would pay for it...