Conceptual
Browse Instruct Curate
Login

A Load Balancer Puts One Address in Front of Instances That Must Be Interchangeable

This is the first node of the curation's spine and the precondition for every statelessness node that follows: the app tier cannot be told it must be replaceable until the learner sees the mechanism that makes the next request land somewhere else. It sits on the name-resolution node (the name points at this, not at a machine) and it is what the health-check, detection-window and latency-budget nodes are all about. Nothing in the entry floor mentions horizontal scale of any kind.