Why read Infrastructure as Code?

Book cover of Infrastructure as Code: Dynamic Systems for the Cloud Age

Book description

Six years ago, Infrastructure as Code was a new concept. Today, as even banks and other conservative organizations plan moves to the cloud, development teams for companies worldwide are attempting to build large infrastructure codebases. With this practical book, Kief Morris of ThoughtWorks shows you how to effectively use principles,…

Explore

Topics

Genres

Coming soon!

When you buy books, we may earn a commission that helps keep our lights on (or join the rebellion as a member).

Why read it?

1 author picked Infrastructure as Code as one of their favorite books. Why do they recommend it?

Yevgeniy Brikman

Author

This is a book for practitioners, by a practitioner, full of practical learnings that I was able to start using in my work immediately.

I especially appreciated the parts teaching the core principles of infrastructure as code (e.g., systems are disposable, consistent, can easily be reproduced, etc.), core practices of infrastructure as code (e.g., use definition files, self-documented systems and processes, version all the things, etc.), and the idea of antifragile systems (rather than just systems that you prevent from breaking) and autonomic systems (rather than just automated systems).

From Yevgeniy's list on practical, hands-on books on DevOps and software delivery.