cattle, not pets

cloudops culture

The mindset that servers should be disposable and interchangeable, not lovingly maintained individuals.

A pet server has a name, gets nursed back to health when sick, and is irreplaceable; cattle are numbered, identical, and simply replaced when one fails. The analogy captures the shift to immutable, automated infrastructure where you rebuild rather than repair.

Cattle not pets describes the shift from servers that are individually named, cared for and nursed back to health, to instances that are numbered, identical and replaced rather than repaired. The pet is a machine with a personality and a hostname someone chose; the cattle is one of forty that can be destroyed without ceremony.

The operational consequence is what matters. If a server is cattle, its configuration exists in a repository rather than in its filesystem, its state lives somewhere else, and rebuilding it is routine rather than an event. That property is what makes automated recovery, autoscaling and immutable deployment possible at all, and the cultural shift is harder than the technical one because it means giving up the diagnostic satisfaction of fixing a machine.

The honest limit is that not everything is cattle. Stateful systems, databases with real data in them, and the appliances that terminate your traffic are not disposable, and treating them as though they were produces confident destruction of things nobody can rebuild. The useful reading is not that pets are wrong, but that most machines were pets by accident rather than by decision, and being deliberate about which is which is the actual discipline.

Also known as: pets vs cattle, cattle not pets

← All glossary entries