Pets vs Cattle

Pets : Unique한 시스템, 한대 한대 각 특성에 맞게 관리 필요

Servers or server pairs that are treated as indispensable or unique systems that can never be down. Typically they are manually built, managed, and “hand fed”. Examples include mainframes, solitary servers, HA loadbalancers/firewalls (active/active or active/passive), database systems designed as master/slave (active/passive), and so on.

Cattle : 언제나 대체가능한 시스템, 필요한 만큼 도입하고 필요없으면 처분 가능

Arrays of more than two servers, that are built using automated tools, and are designed for failure, where no one, two, or even three servers are irreplaceable. Typically, during failure events no human intervention is required as the array exhibits attributes of “routing around failures” by restarting failed servers or replicating data through strategies like triple replication or erasure coding. Examples include web server arrays, multi-master datastores such as Cassandra clusters, multiple racks of gear put together in clusters, and just about anything that is load-balanced and multi-master.

http://cloudscaling.com/blog/cloud-computing/the-history-of-pets-vs-cattle/

The History of Pets vs Cattle and How to Use the Analogy Properly