From f0d3013ca6ef105efc6f7da5aa539dc044dc3c4a Mon Sep 17 00:00:00 2001 From: LarytheLord Date: Wed, 25 Feb 2026 21:21:22 +0530 Subject: [PATCH] docs: use neutral terminology for pets vs cattle section --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 852c693e..5f9bcc14 100644 --- a/README.md +++ b/README.md @@ -580,7 +580,7 @@ This guide is about AWS, not DevOps or server configuration management in genera ### Philosophy - Heroku’s [**Twelve-Factor App**](http://12factor.net/) principles list some established general best practices for deploying applications. -- **Pets vs cattle:** Treat servers [like cattle, not pets](https://www.engineyard.com/blog/pets-vs-cattle). That is, design systems so infrastructure is disposable. It should be minimally worrisome if a server is unexpectedly destroyed. +- **Disposable vs unique infrastructure ("pets vs cattle")**: Treat servers as disposable infrastructure, not unique snowflakes. Design systems so infrastructure is replaceable and resilient. It should be minimally worrisome if a server is unexpectedly destroyed. - The concept of [**immutable infrastructure**](http://radar.oreilly.com/2015/06/an-introduction-to-immutable-infrastructure.html) is an extension of this idea. - Minimize application state on EC2 instances. In general, instances should be able to be killed or die unexpectedly with minimal impact. State that is in your application should quickly move to RDS, S3, DynamoDB, EFS, or other data stores not on that instance. EBS is also an option, though it generally should not be the bootable volume, and EBS will require manual or automated re-mounting.