Infrastructure as Code. 3rd Edition Kief Morris

(ebook) (audiobook) (audiobook)

Nowość
Promocja Przejdź

Infrastructure as Code. 3rd Edition Kief Morris - okladka książki

Infrastructure as Code. 3rd Edition Kief Morris - audiobook MP3

Infrastructure as Code. 3rd Edition Kief Morris - audiobook CD

Autor:: Kief Morris
Wydawnictwo:: O'Reilly Media (Z chęcią przeczytam książkę w języku polskim)
Ocena:: Bądź pierwszym, który oceni tę książkę
Stron:: 436
Dostępne formaty:: ePub

Mobi

Ebook (228,65 zł najniższa cena z 30 dni)

~~269,00 zł~~ (-15%)
228,65 zł

Dodaj do koszyka lub Kup na prezent Kup 1-kliknięciem

(228,65 zł najniższa cena z 30 dni)

Przenieś na półkę

Do przechowalni

The past decade has seen cloud and infrastructure as code move out of shadow IT and startups and into the mainstream. Many organizations rushed to adopt new technologies as part of their transformation into digital businesses, creating a sprawl of unmaintainable infrastructure codebases. Now, there is a need to consolidate cloud-based systems into mature foundations for sustainable growth.

With this book, Kief Morris describes patterns and practices for building and evolving infrastructure as code. The third edition provides a broader context for infrastructure, explaining how to design and implement infrastructure to better support the strategic goals and challenges of an organization, such as supporting growth while better managing costs.

This book covers:

Foundational concepts, including an exploration of declarative and procedural infrastructure languages, where infrastructure code fits into a comprehensive platform strategy and enterprise architecture, and how to test and deliver infrastructure code.
Infrastructure architecture, drawing on lessons learned from software design and engineering to build infrastructure codebases that can be evolved and scaled to enable growth and adapt to changing needs.
Patterns for building infrastructure to support platform services across the complicated, varied landscapes of real-world IT systems, from physical hardware to virtual servers to cloud-native clusters and serverless workloads.
Workflows and operating models that combine automation and cloud with forward-thinking approaches like Agile and DevOps for rigorous governance of compliance, cost, security, and operational quality.

Wybrane bestsellery

Promocja

Sześć lat temu pojęcie infrastruktury jako kodu było czymś nowym. Dzisiaj, gdy nawet banki i inne konserwatywne organizacje planują przejść na korzystanie z chmury, zespoły programistów w firmach na całym świecie próbują budować duże bazy kodu infrastruktury. W swojej praktycznej książce Kief Morris z ThoughtWorks wyjaśnia, jak efektywnie zarządzać
- PDF
Infrastruktura jako kod. Dynamiczne systemy w epoce chmury

Kief Morris

(68,43 zł najniższa cena z 30 dni)

46.39 zł ~~98.70 zł (-53%)~~

Ebooka "Infrastructure as Code. 3rd Edition" przeczytasz na:

czytnikach Inkbook, Kindle, Pocketbook, Onyx Booxs i innych
systemach Windows, MacOS i innych

systemach Windows, Android, iOS, HarmonyOS
na dowolnych urządzeniach i aplikacjach obsługujących formaty: PDF, EPub, Mobi

Masz pytania? Zajrzyj do zakładki Pomoc »

Oceny i opinie klientów: Infrastructure as Code. 3rd Edition Kief Morris

(0)

Szczegóły książki

ISBN Ebooka:: 978-10-981-5031-0, 9781098150310
Data wydania ebooka :: 2025-03-13 Data wydania ebooka często jest dniem wprowadzenia tytułu do sprzedaży i może nie być równoznaczna z datą wydania książki papierowej. Dodatkowe informacje możesz znaleźć w darmowym fragmencie. Jeśli masz wątpliwości skontaktuj się z nami sklep@helion.pl.
Język publikacji:: 1
Rozmiar pliku ePub:: 10MB
Rozmiar pliku Mobi:: 10MB

Zgłoś erratę
Kategorie:
Programowanie » Programowanie w chmurze

Spis treści książki

Preface
- Why I Wrote This Book
- What This Book Is and Isnt
- Who This Book Is For
- Principles, Practices, and Patterns
- The FoodSpin Examples
- For More
- Conventions Used in This Book
- OReilly Online Learning
- How to Contact Us
- Acknowledgments
I. Foundations
1. What Is Infrastructure as Code?
- Infrastructure as Code
- From the Iron Age to the Cloud Age
  - Cloud Age Approaches to Change Management
  - The Path to the Cloud Age
- Strategic Goals and Infrastructure as Code
- System Architecture Goals and Infrastructure as Code
- Use Infrastructure as Code to Optimize for Change
  - Myth: Infrastructure Doesnt Change Very Often
  - Myth: We Can Build the Infrastructure First and Automate It Later
  - Myth: Speed and Quality Are Trade-Offs
- The Four Key Metrics
- Core Practices for Infrastructure as Code
  - Define Everything as Code
  - Continually Test and Deliver All Work in Progress
  - Build Small, Simple Pieces That Can Change Independently
- Conclusion
2. Principles of Cloud Infrastructure
- Assume Systems Are Unreliable
- Make Everything Reproducible
- Avoid Snowflake Systems
- Create Disposable Things
- Minimize Variation
- Ensure That Any Procedure Can Be Repeated
- Apply Software Design Principles to Infrastructure Code
- Conclusion
3. Infrastructure Platforms
- Infrastructure Platforms
  - Infrastructure Resources
    - Compute resources
    - Storage resources
    - Network resources
  - IaaS in the Data Center
  - Multicloud
- Engineering Platforms
  - Platform Services
  - Providing Platform Service Functionality
- Platform Delivery Services
  - Application Delivery Services
  - Infrastructure Delivery Services
  - Platform Management Services
- Conclusion
4. Infrastructure as Code Tools and Languages
- Coding Infrastructure
  - Moving Beyond Task-Based Scripting
  - Understanding What You Can Define as Code
  - Code or Configuration?
  - Defining Configuration as Code
  - Managing Your Code in a Source Code Repository
- Infrastructure Code Processing
  - Understanding When Code Executes
  - Processing and Deploying Infrastructure Code
  - Previewing Changes
  - Tracing Infrastructure Code Execution
  - Managing Infrastructure State
- Infrastructure as Code Tools
- Types of Languages for Coding Infrastructure
  - Procedural and Idempotent Code
  - Imperative and Declarative Languages and Tools
  - Domain-Specific and General-Purpose Languages
  - Low-Level and High-Level Languages
  - Infrastructure from Code
- Conclusion
II. Design
5. Design Principles for Infrastructure as Code
- Design Considerations for Infrastructure as Code
  - CUPID Properties for Design
  - Cohesion and Coupling
  - Providers, Consumers, and Interfaces
  - Management of Interfaces Between Components
  - Use of Interfaces for Composability
- Design Across Infrastructure Code Lifecycle Stages
- Design Forces
  - Design Forces for Source Code
    - Code ownership
    - Working sets
    - Delivery scope
  - Design Forces for Infrastructure Packaging and Deployment
    - Management of downtime
    - Workload alignment
    - Compliance
  - Design Forces for Runtime
    - Scaling
    - Geographical distribution
    - Resilience
    - Data regulations
    - Data partitioning
    - Component lifecycles
    - Hosting and environmental costs
    - Runtime influence on other stages
  - Design Forces Across Lifecycle Stages
    - Cognitive size
    - Change scope
    - Organizational structure
    - Cost of ownership
    - Security
- Conclusion
6. Infrastructure Components
- The Infrastructure Components
  - The Start of Infrastructure Design: Workloads
  - Infrastructure Compositions
  - Infrastructure Deployment Stacks
  - Infrastructure Code Libraries
  - Libraries as Deployable Stacks
- Sharing and Reuse of Infrastructure Code
  - Sharing Infrastructure Code Components
  - Sharing Stack Code Across Multiple Instances
  - Sharing Stack Instances Across Workloads
- Application-Driven Infrastructure Design
  - Horizontal Design
  - Vertical Design
  - Shared Infrastructure Included in Vertical Design
  - Reference Application-Driven Infrastructure Design
- Design Workflow
- Conclusion
7. Designing Deployable Infrastructure Stacks
- Patterns for Sizing and Structuring Stacks
  - Full System Stack
    - Motivation
    - Applicability
    - Consequences
    - Implementation
    - Related patterns
  - Monolithic Stack
    - Motivation
    - Consequences
    - Implementation
    - Related patterns
  - Application Group Stack
    - Motivation
    - Consequences
    - Implementation
    - Related patterns
  - Single Service Stack
    - Motivation
    - Applicability
    - Consequences
    - Implementation
    - Related patterns
  - Micro Stacks
    - Motivation
    - Consequences
    - Implementation
    - Related patterns
  - Shared Stack
    - Motivation
    - Applicability
    - Consequences
    - Implementation
- Stack Patterns for Multiple Instances of Infrastructure
  - Multi-Environment Stack
    - Motivations
    - Consequences
    - Related patterns
  - Snowflakes as Code
    - Also known as
    - Motivation
    - Applicability
    - Consequences
    - Related patterns
  - Reusable Stack
    - Motivation
    - Applicability
    - Consequences
    - Implementation
    - Related patterns
- Conclusion
8. Configuring Infrastructure Stack Instances
- Key Concepts
  - Use Stack Parameters to Create Unique Identifiers
  - Keep Parameters Simple
- Example Stack
- Patterns for Configuring Stacks
  - Configuration in Code
    - Motivation
    - Consequences
    - Implementation
    - Related patterns
  - Manual Stack Parameters
    - Motivation
    - Consequences
    - Implementation
    - Related patterns
  - Stack Environment Variables
    - Motivation
    - Consequences
    - Implementation
  - Scripted Parameters
    - Motivation
    - Applicability
    - Consequences
    - Implementation
  - Stack Configuration Files
    - Motivation
    - Applicability
    - Consequences
    - Implementation
    - Related patterns
  - Deployment Wrapper Stack
    - Also known as
    - Motivation
    - Consequences
    - Implementation
    - Related patterns
  - Pipeline Stack Parameters
    - Motivation
    - Applicability
    - Consequences
    - Implementation
    - Related patterns
  - Stack Parameter Registry
    - Motivation
    - Applicability
    - Consequences
    - Implementation
    - Related patterns
- Implementing a Configuration Registry
  - Integrated Infrastructure Automation Tool Registries
  - Standalone Packaged Configuration Registries
  - IaaS Platform Registry Services
  - Your Own Configuration Registry
  - Single or Multiple Configuration Registries
- Handling Secrets
  - Generating Secrets
  - Storing Secrets in Encrypted Files
  - Using a Secrets Storage Service
  - Injecting Secrets at Runtime
- Conclusion
9. Integrating Infrastructure Stacks
- Example Infrastructure Deployment Stacks
- Resource Discovery Patterns
  - Resource Matching
    - Motivation
    - Applicability
    - Consequences
    - Implementation
    - Related patterns
  - Stack State Lookup
    - Also known as
    - Motivation
    - Applicability
    - Consequences
    - Implementation
    - Related patterns
  - Integration Registry Lookup
    - Also known as
    - Motivation
    - Applicability
    - Consequences
    - Implementation
    - Related patterns
- Implementing Resource Discovery
  - Implementing Discovery in Stack Code
  - Using Dependency Injection
  - Managing Dependencies in a Deployment Script
  - Wiring Stacks Together with a Composition
- Conclusion
10. Designing Infrastructure Code Libraries
- Facade Module
  - Also Known As
  - Motivation
  - Applicability
  - Consequences
  - Implementation
  - Related Patterns
- Obfuscation Module
  - Motivation
  - Applicability
  - Consequences
  - Implementation
  - Related Patterns
- Unshared Module
  - Motivation
  - Applicability
  - Consequences
  - Implementation
- Bundle Module
  - Motivation
  - Applicability
  - Consequences
  - Implementation
  - Related Patterns
- Spaghetti Module
  - Motivation
  - Consequences
  - Implementation
  - Related Patterns
- Infrastructure Domain Entity
  - Motivation
  - Applicability
  - Implementation
  - Related Patterns
- Stack Module
  - Also Known As
  - Motivation and Applicability
  - Implementation
- Modular Monolith
  - Motivation
  - Consequences
  - Implementation
  - Related Patterns
- Conclusion
11. Building Servers as Code
- Defining Servers
  - Whats on a Server
  - Where Things Come From
  - Server Configuration Code
  - Server Roles
- Creating and Provisioning a New Server Instance
  - Creating a Server by Using Network Provisioning
  - Creating an IaaS Server by Hand
  - Creating a Server as Part of a Stack
  - Creating a Server from an Event
- Configuring a New Server Instance
  - Baking Images and Frying Instances
  - Pull Configuration with Initialization Scripts
  - Push Configuration with External Commands
- Updating and Changing Servers
  - Push on Change
  - Continuous Configuration Synchronization
  - Changing Servers by Replacement
  - Immutable Server
- Building Server Images
  - Hot-Cloning an Existing Server
  - Booting an OS Installer
  - Modifying a Stock Image
  - Orchestrating Image Building
- Conclusion
12. Designing Environments
- Multi-Environment Architectures
- Multiple Delivery Environments
- Environments Split for Alignment
  - Aligning Environments to System Architecture
  - Aligning Environments to Organizational Structure
  - Aligning Environments to Governance Concerns
- Multiple Environment Replicas
  - Designing Environments for Operability Scenarios
  - Distributing Environments Geographically
  - Replicating Environments for User Bases
- Environment Implementation Layers
  - Using Design Forces to Choose the Environment Implementation Layer
  - Testing and Delivering Changes to Environment Infrastructure
- IaaS Resource Groups and Environments
- Environments with Multiple Stacks
- Conclusion
13. Providing Application Runtime Infrastructure
- Application-Driven Infrastructure Design
- Application Runtime Platforms
  - Servers as Code
  - Server Clusters as Code
  - Application Clusters as Code
    - Cluster as a service (IaaS provisioned)
    - Packaged cluster distribution
  - Serverless Application Infrastructure
    - Serverless and infrastructure
    - Serverless platforms
- Cluster Topologies
  - Multiple Environments in One Cluster
  - One Cluster per Environment
  - Multiple Clusters per Environment
  - Cross-Environment Clusters
- Conclusion
III. Delivery
14. Core Infrastructure Delivery Workflows
- Continuous Delivery Principles for Infrastructure as Code
  - Automate the Full Process
  - Make Changes Using Only the Automated Process
  - Ensure That Environments Are Consistent
  - Deliver Changes Comprehensively
  - Keep Delivery Cycles Short
  - Keep All Code Production-Ready
  - Ensure That Code and Deployed Resources Are Consistent
  - Minimize Disruption When Deploying Changes
- Core Infrastructure Delivery Workflow
  - Development Stage
  - Build Stage
  - Test Stages
  - Release Stage
  - Run Stage
  - Workflow Cycles
- Workflows and Team Topologies for Delivering Software and Infrastructure
  - Infrastructure Instance Management Teams
  - Full Stack Infrastructure Team
  - Infrastructure Enablement Team
- Measuring Infrastructure Delivery Effectiveness
- Conclusion
15. Building and Distributing Infrastructure as Code
- Build Stage: Preparing for Distribution
  - Code Processing Steps for Building and Deploying
  - Build on Deploy Workflow
  - Build Once, Deploy Many Workflow
  - Bundling or Locking Dependencies
  - Pull Requests and Trunk-Based Development
- Distribution of Infrastructure Code
  - Distributing Code Branches as Artifacts
  - Distributing Stack Packages as Artifacts
  - Distributing Libraries as Artifacts
- Integration Workflows
  - Fan-in: Integrating Components During Delivery
  - Federation: Integrating Components at Runtime
  - Monorepo: Integrating Components in the Build
  - Pretesting Infrastructure
- Infrastructure Service Teams
  - Shared Infrastructure as a Service
  - Provisioning an Infrastructure Instance on Demand
  - Providing Deployable Infrastructure as a Component
  - Multiple Infrastructure Platform Teams
- Conclusion
16. Implementing Infrastructure Delivery with Pipelines
- Organizing Projects in a Codebase
  - Organizing Build Projects and Repositories
    - Full codebase in one repository
    - A separate repository for each build project
    - Multiple repositories with multiple projects
  - Organizing Types of Code
    - Organize code by domain concept
    - Project support files
    - Cross-project tests
    - Dedicated integration test projects
- Working on Code Locally
  - Local IaaS Emulators
  - Personal IaaS Environments
  - Just Enough Environment
- Designing Infrastructure Delivery Pipelines
  - Pipeline Stage Content
  - Pipeline Stage Actions
  - Pipeline Stage Context
  - Delivery Pipeline Software and Services
- Using Delivery Orchestration Scripts
- Conclusion
17. Infrastructure Code Testing Strategy
- Why Continually Test Infrastructure Code?
  - What Continual Testing Means
  - Immediate Testing and Eventual Testing
- What Should We Test with Infrastructure?
- Challenges with Testing Infrastructure Code
  - Tests for Declarative Code Often Have Low Value
    - Testing declarative code that varies outcomes
    - Testing combinations of declarative code
  - Unit Testing Code Generation
  - Testing Infrastructure Code Is Slow
  - Dependencies Complicate Testing Infrastructure
- Progressive Testing
  - Test Pyramid
  - Swiss Cheese Testing Model
- Testing in Production
  - What You Cant Replicate Outside Production
  - Managing the Risks of Testing in Production
- Conclusion
18. Infrastructure Code Testing Implementation
- Offline Testing Stages for Stacks
  - Syntax Checking
  - Offline Static Code Analysis
  - Connected Static Code Analysis
  - Supply-Chain Checks
  - Local Infrastructure Emulators
- Use Test Fixtures to Handle Dependencies
  - Use Test Fixtures to Replace Providers
  - Use Test Fixtures to Replace Consumers
  - Refactor Components So They Can Be Isolated
- Online Testing Stages for Stacks
  - Preview: Seeing What Changes Will Be Made
  - Verification: Making Assertions About Infrastructure Resources
  - Outcomes: Proving Infrastructure Works Correctly
- Test Instance Lifecycles
  - Persistent Test Stack
    - Motivation
    - Applicability
    - Consequences
    - Implementation
    - Related patterns
  - Ephemeral Test Stack
    - Motivation
    - Applicability
    - Consequences
    - Implementation
    - Related patterns
  - Dual Persistent and Ephemeral Stack Stages
    - Motivation
    - Applicability
    - Consequences
    - Implementation
    - Related patterns
  - Periodic Stack Rebuild
    - Motivation
    - Applicability
    - Consequences
    - Implementation
    - Related patterns
  - Continuous Stack Reset
    - Motivation
    - Applicability
    - Consequences
    - Implementation
    - Related patterns
- Test Orchestration
  - Consider Test Orchestration Tools
  - Support Local Testing
  - Avoid Tight Coupling with Pipeline Tools
- Conclusion
19. Deploying Infrastructure
- Understanding Software Deployment Strategies
  - Push Deployment for Software
  - Pull Deployment for Software
  - GitOps Deployment for Software
- Using Infrastructure Deployment Strategies
  - Siloed Infrastructure Deployment
  - Application Infrastructure Descriptor
  - Infrastructure from Code
- Running Infrastructure Deployments
  - Deploying Infrastructure Code from Your Computer
  - Deploying from a Central Service
  - Deploying from a Delivery Pipeline
  - Using an Infrastructure Code Deployment Service
  - Infrastructure as Data
  - Infrastructure Deployment Scripts
- Triggering Infrastructure Deployments
  - Using Input Materials for Deployment
  - Manually Triggering Deployment
  - Automatically Triggering Deployment
  - Implementing Triggers
- Conclusion
20. Changing Existing Infrastructure
- Changing a System Incrementally
  - Break a Change into Increments
  - Handle Incomplete Changes
- Safely Changing Live Infrastructure
  - Manually Remap Live Infrastructure
  - Remap Live Infrastructure in Pipelines
  - Define Changes to Live Infrastructure in Code
  - Script Live Infrastructure Changes
  - Use Expand and Contract to Incrementally Change Live Infrastructure
- Minimizing Disruption When Deploying Changes
  - Blue-Green Deployments
  - Rolling Upgrades and Canary Releases
- Managing Data When Changing Live Infrastructure
  - Store and Load
  - Use Continuous Data Transfer
  - Segregate Data Infrastructure
  - Separate Software and Data Changes
  - Use Continuous Disaster Recovery
- Conclusion
21. Governance
- Shift Left
  - Workflow for Shifting Left
  - Team Topologies for Shifting Left
- Compliance as Code
  - Controls by Component Design Layer
  - Controls by Workflow
- Conclusion
Index