- Ocena:
- Bądź pierwszym, który oceni tę książkę
- Stron:
- 430
- Dostępne formaty:
-
ePubMobi
Opis ebooka: Infrastructure as Code. 2nd Edition
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, practices, and patterns pioneered by DevOps teams to manage cloud-age infrastructure.
Ideal for system administrators, infrastructure engineers, software developers, team leads, and architects, this updated edition demonstrates how you can exploit cloud and automation technology to make changes easily, safely, quickly, and responsibly. You'll learn how to define everything as code and apply software design and engineering practices to build your system from small, loosely coupled pieces.
This book covers:
- Foundations: Use Infrastructure as Code to drive continuous change and raise the bar of operational quality, using tools and technologies to build cloud-based platforms
- Working with infrastructure stacks: Learn how to define, provision, test, and continuously deliver changes to infrastructure resources
- Working with servers and other platforms: Use patterns to design provisioning and configuration of servers and clusters
- Working with large systems and teams: Learn workflows, governance, and architectural patterns to create and manage infrastructure elements
Wybrane bestsellery
-
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 ks...(67.48 zł najniższa cena z 30 dni)
88.83 zł
98.70 zł(-10%) -
This book will help you learn about the practices, tools, and frameworks in the low-code/no-code platform, Microsoft Power Platform, to design and create enterprise-grade business-critical solutions at scale using the DevOps and ALM processes.
-
Unlock the power of C programming to embark on an epic journey of programming expertise with our comprehensive C programming book KEY FEATURES ? Get a solid foundation of C programming by learning the basic principles, including data types, variables, operators, and control structures. ? Hands-...(97.23 zł najniższa cena z 30 dni)
97.03 zł
109.00 zł(-11%) -
This is your guide to passing the challenging AWS Certified Developer – Associate certification exam and setting yourself up for a rewarding career. Through a sample project, it explains how to design, architect, and implement applications on AWS.
Ebooka "Infrastructure as Code. 2nd Edition" przeczytasz na:
-
czytnikach Inkbook, Kindle, Pocketbook, Onyx Boox 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 »
Audiobooka "Infrastructure as Code. 2nd Edition" posłuchasz:
-
w aplikacji Ebookpoint na Android, iOS, HarmonyOs
-
na systemach Windows, MacOS i innych
-
na dowolnych urządzeniach i aplikacjach obsługujących format MP3 (pliki spakowane w ZIP)
Masz pytania? Zajrzyj do zakładki Pomoc »
Kurs Video "Infrastructure as Code. 2nd Edition" zobaczysz:
-
w aplikacjach Ebookpoint i Videopoint na Android, iOS, HarmonyOs
-
na systemach Windows, MacOS i innych z dostępem do najnowszej wersji Twojej przeglądarki internetowej
Szczegóły ebooka
- ISBN Ebooka:
- 978-10-981-1462-6, 9781098114626
- Data wydania ebooka:
- 2020-12-08 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@ebookpoint.pl.
- Język publikacji:
- angielski
- Rozmiar pliku ePub:
- 6.8MB
- Rozmiar pliku Mobi:
- 14.2MB
Spis treści ebooka
- Preface
- Why I Wrote This Book
- Whats New and Different in This Edition
- Whats Next
- What This Book Is and Isnt
- Some History of Infrastructure as Code
- Who This Book Is For
- Principles, Practices, and Patterns
- The ShopSpinner Examples
- Conventions Used in This Book
- OReilly Online Learning
- How to Contact Us
- Acknowledgments
- I. Foundations
- 1. What Is Infrastructure as Code?
- From the Iron Age to the Cloud Age
- Infrastructure as Code
- Benefits of Infrastructure as Code
- Use Infrastructure as Code to Optimize for Change
- Objection: We dont make changes often enough to justify automating them
- Objection: We should build first and automate later
- Objection: We must choose between speed and quality
- The Four Key Metrics
- Three Core Practices for Infrastructure as Code
- Core Practice: Define Everything as Code
- Core Practice: Continuously Test and Deliver All Work in Progress
- Core Practice: Build Small, Simple Pieces That You Can Change Independently
- Conclusion
- 2. Principles of Cloud Age Infrastructure
- Principle: Assume Systems Are Unreliable
- Principle: Make Everything Reproducible
- Pitfall: Snowflake Systems
- Principle: Create Disposable Things
- Principle: Minimize Variation
- Configuration Drift
- Principle: Ensure That You Can Repeat Any Process
- Conclusion
- 3. Infrastructure Platforms
- The Parts of an Infrastructure System
- Infrastructure Platforms
- Infrastructure Resources
- Compute Resources
- Storage Resources
- Network Resources
- Conclusion
- 4. Core Practice: Define Everything as Code
- Why You Should Define Your Infrastructure as Code
- What You Can Define as Code
- Choose Tools with Externalized Configuration
- Manage Your Code in a Version Control System
- Infrastructure Coding Languages
- Infrastructure Scripting
- Declarative Infrastructure Languages
- Programmable, Imperative Infrastructure Languages
- Declarative Versus Imperative Languages for Infrastructure
- Domain-Specific Infrastructure Languages
- General-Purpose Languages Versus DSLs for Infrastructure
- Implementation Principles for Defining Infrastructure
as Code
- Separate Declarative and Imperative Code
- Treat Infrastructure Code Like Real Code
- Conclusion
- II. Working with Infrastructure Stacks
- 5. Building Infrastructure Stacks as Code
- What Is an Infrastructure Stack?
- Stack Code
- Stack Instance
- Configuring Servers in a Stack
- Low-Level Infrastructure Languages
- High-Level Infrastructure Languages
- What Is an Infrastructure Stack?
- Patterns and Antipatterns for Structuring Stacks
- Antipattern: Monolithic Stack
- Motivation
- Applicability
- Consequences
- Implementation
- Related patterns
- Antipattern: Monolithic Stack
- Pattern: Application Group Stack
- Motivation
- Applicability
- Consequences
- Implementation
- Related patterns
- Pattern: Service Stack
- Motivation
- Applicability
- Consequences
- Implementation
- Related patterns
- Pattern: Micro Stack
- Motivation
- Consequences
- Implementation
- Related Patterns
- Conclusion
- 6. Building Environments with Stacks
- What Environments Are All About
- Delivery Environments
- Multiple Production Environments
- Environments, Consistency, and Configuration
- What Environments Are All About
- Patterns for Building Environments
- Antipattern: Multiple-Environment Stack
- Motivations
- Consequences
- Related patterns
- Antipattern: Multiple-Environment Stack
- Antipattern: Copy-Paste Environments
- Motivation
- Applicability
- Consequences
- Implementation
- Related patterns
- Pattern: Reusable Stack
- Motivation
- Applicability
- Consequences
- Implementation
- Related patterns
- Building Environments with Multiple Stacks
- Conclusion
- 7. Configuring Stack Instances
- Using Stack Parameters to Create Unique Identifiers
- Example Stack Parameters
- Patterns for Configuring Stacks
- Antipattern: Manual Stack Parameters
- Motivation
- Consequences
- Implementation
- Related patterns
- Antipattern: Manual Stack Parameters
- Pattern: Stack Environment Variables
- Motivation
- Applicability
- Consequences
- Implementation
- Related patterns
- Pattern: Scripted Parameters
- Motivation
- Applicability
- Consequences
- Implementation
- Related patterns
- Pattern: Stack Configuration Files
- Motivation
- Applicability
- Consequences
- Implementation
- Related patterns
- Pattern: Wrapper Stack
- Motivation
- Consequences
- Implementation
- Related patterns
- Pattern: Pipeline Stack Parameters
- Motivation
- Applicability
- Consequences
- Implementation
- Related patterns
- Pattern: Stack Parameter Registry
- Motivation
- Applicability
- Consequences
- Implementation
- Related patterns
- Configuration Registry
- Implementing a Configuration Registry
- Infrastructure automation tool registries
- General-purpose configuration registry products
- Platform registry services
- DIY configuration registries
- Implementing a Configuration Registry
- Single or Multiple Configuration Registries
- Handling Secrets as Parameters
- Encrypting Secrets
- Secretless Authorization
- Injecting Secrets at Runtime
- Disposable Secrets
- Conclusion
- 8. Core Practice:
Continuously Test and Deliver
- Why Continuously Test Infrastructure Code?
- What Continuous Testing Means
- What Should We Test with Infrastructure?
- Why Continuously Test Infrastructure Code?
- Challenges with Testing Infrastructure Code
- Challenge: Tests for Declarative Code Often Have Low Value
- Testing variable declarative code
- Testing combinations of declarative code
- Challenge: Tests for Declarative Code Often Have Low Value
- Challenge: Testing Infrastructure Code Is Slow
- Challenge: Dependencies Complicate Testing Infrastructure
- Progressive Testing
- Test Pyramid
- Swiss Cheese Testing Model
- Infrastructure Delivery Pipelines
- Pipeline Stages
- Scope of Components Tested in a Stage
- Scope of Dependencies Used for a Stage
- Platform Elements Needed for a Stage
- Delivery Pipeline Software and Services
- Testing in Production
- What You Cant Replicate Outside Production
- Managing the Risks of Testing in Production
- Conclusion
- 9. Testing Infrastructure Stacks
- Example Infrastructure
- The Example Stack
- Pipeline for the Example Stack
- Example Infrastructure
- Offline Testing Stages for Stacks
- Syntax Checking
- Offline Static Code Analysis
- Static Code Analysis with API
- Testing with a Mock API
- Online Testing Stages for Stacks
- Preview: Seeing What Changes Will Be Made
- Verification: Making Assertions About Infrastructure Resources
- Outcomes: Proving Infrastructure Works Correctly
- Using Test Fixtures to Handle Dependencies
- Test Doubles for Upstream Dependencies
- Test Fixtures for Downstream Dependencies
- Refactor Components So They Can Be Isolated
- Life Cycle Patterns for Test Instances of Stacks
- Pattern: Persistent Test Stack
- Motivation
- Applicability
- Consequences
- Implementation
- Related patterns
- Pattern: Persistent Test Stack
- Pattern: Ephemeral Test Stack
- Motivation
- Applicability
- Consequences
- Implementation
- Related patterns
- Antipattern: Dual Persistent and Ephemeral Stack Stages
- Motivation
- Applicability
- Consequences
- Implementation
- Related patterns
- Pattern: Periodic Stack Rebuild
- Motivation
- Applicability
- Consequences
- Implementation
- Related patterns
- Pattern: Continuous Stack Reset
- Motivation
- Applicability
- Consequences
- Implementation
- Related patterns
- Test Orchestration
- Support Local Testing
- Avoid Tight Coupling with Pipeline Tools
- Test Orchestration Tools
- Conclusion
- III. Working with Servers and Other Application Runtime Platforms
- 10. Application Runtimes
- Cloud Native and Application-Driven Infrastructure
- Application Runtime Targets
- Deployable Parts of an Application
- Deployment Packages
- Deploying Applications to Servers
- Packaging Applications in Containers
- Deploying Applications to Server Clusters
- Deploying Applications to Application Clusters
- Packages for Deploying Applications to Clusters
- Deploying FaaS Serverless Applications
- Application Data
- Data Schemas and Structures
- Cloud Native Application Storage Infrastructure
- Application Connectivity
- Service Discovery
- Conclusion
- 11. Building Servers as Code
- Whats on a Server
- Where Things Come From
- Server Configuration Code
- Server Configuration Code Modules
- Designing Server Configuration Code Modules
- Versioning and Promoting Server Code
- Server Roles
- Testing Server Code
- Progressively Testing Server Code
- What to Test with Server Code
- How to Test Server Code
- Creating a New Server Instance
- Hand-Building a New Server Instance
- Using a Script to Create a Server
- Using a Stack Management Tool to Create a Server
- Configuring the Platform to Automatically Create Servers
- Using a Networked Provisioning Tool to Build a Server
- Prebuilding Servers
- Hot-Cloning a Server
- Using a Server Snapshot
- Creating a Clean Server Image
- Configuring a New Server Instance
- Frying a Server Instance
- Baking Server Images
- Combining Baking and Frying
- Applying Server Configuration When Creating a Server
- Conclusion
- 12. Managing Changes to Servers
- Change Management Patterns: When to Apply Changes
- Antipattern: Apply On Change
- Motivation
- Applicability
- Consequences
- Implementation
- Related patterns
- Antipattern: Apply On Change
- Pattern: Continuous Configuration Synchronization
- Motivation
- Applicability
- Consequences
- Implementation
- Related patterns
- Change Management Patterns: When to Apply Changes
- Pattern: Immutable Server
- Motivation
- Applicability
- Consequences
- Implementation
- Related patterns
- How to Apply Server Configuration Code
- Pattern: Push Server Configuration
- Motivation
- Applicability
- Consequences
- Implementation
- Related patterns
- Pattern: Push Server Configuration
- Pattern: Pull Server Configuration
- Motivation
- Applicability
- Implementation
- Related patterns
- Other Server Life Cycle Events
- Stopping and Restarting a Server Instance
- Replacing a Server Instance
- Recovering a Failed Server
- Conclusion
- 13. Server Images as Code
- Building a Server Image
- Why Build a Server Image?
- How to Build a Server Image
- Tools for Building Server Images
- Online Image Building Process
- Infrastructure for the builder instance
- Configuring the builder instance
- Offline Image Building Process
- Building a Server Image
- Origin Content for a Server Image
- Building from a Stock Server Image
- Building a Server Image from Scratch
- Provenance of a Server Image and its Content
- Changing a Server Image
- Reheating or Baking a Fresh Image
- Versioning a Server Image
- Updating Server Instances When an Image Changes
- Providing and Using a Server Image Across Teams
- Handling Major Changes to an Image
- Using a Pipeline to Test and Deliver a Server Image
- Build Stage for a Server Image
- Test Stage for a Server Image
- Delivery Stages for a Server Image
- Using Multiple Server Images
- Server Images for Different Infrastructure Platforms
- Server Images for Different Operating Systems
- Server Images for Different Hardware Architectures
- Server Images for Different Roles
- Layering Server Images
- Sharing Code Across Server Images
- Conclusion
- 14. Building Clusters as Code
- Application Cluster Solutions
- Cluster as a Service
- Packaged Cluster Distribution
- Application Cluster Solutions
- Stack Topologies for Application Clusters
- Monolithic Stack Using Cluster as a Service
- Monolithic Stack for a Packaged Cluster Solution
- Pipeline for a Monolithic Application Cluster Stack
- Example of Multiple Stacks for a Cluster
- Sharing Strategies for Application Clusters
- One Big Cluster for Everything
- Separate Clusters for Delivery Stages
- Clusters for Governance
- Clusters for Teams
- Service Mesh
- Infrastructure for FaaS Serverless
- Conclusion
- IV. Designing Infrastructure
- 15. Core Practice: Small, Simple Pieces
- Designing for Modularity
- Characteristics of Well-Designed Components
- Rules for Designing Components
- Avoid duplication
- Rule of composition
- Single responsibility principle
- Design components around domain concepts, not technical ones
- Law of Demeter
- No circular dependencies
- Use Testing to Drive Design Decisions
- Designing for Modularity
- Modularizing Infrastructure
- Stack Components Versus Stacks as Components
- Using a Server in a Stack
- Drawing Boundaries Between Components
- Align Boundaries with Natural Change Patterns
- Align Boundaries with Component Life Cycles
- Align Boundaries with Organizational Structures
- Create Boundaries That Support Resilience
- Create Boundaries That Support Scaling
- Align Boundaries to Security and Governance Concerns
- Conclusion
- 16. Building Stacks from Components
- Infrastructure Languages for Stack Components
- Reuse Declarative Code with Modules
- Dynamically Create Stack Elements with Libraries
- Infrastructure Languages for Stack Components
- Patterns for Stack Components
- Pattern: Facade Module
- Motivation
- Applicability
- Consequences
- Implementation
- Related patterns
- Pattern: Facade Module
- Antipattern: Obfuscation Module
- Motivation
- Applicability
- Consequences
- Implementation
- Related patterns
- Antipattern: Unshared Module
- Motivation
- Applicability
- Consequences
- Implementation
- Related patterns
- Pattern: Bundle Module
- Motivation
- Applicability
- Consequences
- Implementation
- Related patterns
- Antipattern: Spaghetti Module
- Motivation
- Consequences
- Implementation
- Related patterns
- Pattern: Infrastructure Domain Entity
- Motivation
- Applicability
- Implementation
- Related patterns
- Building an Abstraction Layer
- Conclusion
- 17. Using Stacks as Components
- Discovering Dependencies Across Stacks
- Pattern: Resource Matching
- Motivation
- Applicability
- Consequences
- Implementation
- Related patterns
- Pattern: Resource Matching
- Pattern: Stack Data Lookup
- Motivation
- Applicability
- Consequences
- Implementation
- Related patterns
- Discovering Dependencies Across Stacks
- Pattern: Integration Registry Lookup
- Motivation
- Applicability
- Consequences
- Implementation
- Related patterns
- Dependency Injection
- Issues with mixing dependency and definition code
- Decoupling dependencies from their discovery
- Conclusion
- V. Delivering Infrastructure
- 18. Organizing Infrastructure Code
- Organizing Projects and Repositories
- One Repository, or Many?
- One Repository for Everything
- One repository, multiple builds
- A Separate Repository for Each Project (Microrepo)
- Multiple Repositories with Multiple Projects
- Organizing Projects and Repositories
- Organizing Different Types of Code
- Project Support Files
- Cross-Project Tests
- Keeping integration tests within a project
- Dedicated Integration Test Projects
- Organize Code by Domain Concept
- Organizing Configuration Value Files
- Managing Infrastructure and Application Code
- Delivering Infrastructure and Applications
- Testing Applications with Infrastructure
- Testing Infrastructure Before Integrating
- Using Infrastructure Code to Deploy Applications
- Conclusion
- 19. Delivering Infrastructure Code
- Delivering Infrastructure Code
- Building an Infrastructure Project
- Packaging Infrastructure Code as an Artifact
- Using a Repository to Deliver Infrastructure Code
- Specialized artifact repository
- Tool-specific repository
- General file storage repository
- Delivering code from a source code repository
- Delivering Infrastructure Code
- Integrating Projects
- Pattern: Build-Time Project Integration
- Motivation
- Applicability
- Consequences
- Implementation
- Related patterns
- Pattern: Build-Time Project Integration
- Pattern: Delivery-Time Project Integration
- Motivation
- Applicability
- Consequences
- Implementation
- Related patterns
- Pattern: Apply-Time Project Integration
- Motivation
- Applicability
- Consequences
- Implementation
- Related patterns
- Using Scripts to Wrap Infrastructure Tools
- Assembling Configuration Values
- Simplifying Wrapper Scripts
- Conclusion
- 20. Team Workflows
- The People
- Who Writes Infrastructure Code?
- Applying Code to Infrastructure
- Applying Code from Your Local Workstation
- Applying Code from a Centralized Service
- Personal Infrastructure Instances
- Source Code Branches in Workflows
- Preventing Configuration Drift
- Minimize Automation Lag
- Avoid Ad Hoc Apply
- Apply Code Continuously
- Immutable Infrastructure
- Governance in a Pipeline-based Workflow
- Reshuffling Responsibilities
- Shift Left
- An Example Process for Infrastructure as Code with Governance
- Conclusion
- 21. Safely Changing Infrastructure
- Reduce the Scope of Change
- Small Changes
- Example of Refactoring
- Reduce the Scope of Change
- Pushing Incomplete Changes to Production
- Parallel Instances
- Backward Compatible Transformations
- Feature Toggles
- Changing Live Infrastructure
- Infrastructure Surgery
- Expand and Contract
- Zero Downtime Changes
- Blue-green changes
- Continuity
- Continuity by Preventing Errors
- Continuity by Fast Recovery
- Continuous Disaster Recovery
- Chaos Engineering
- Planning for Failure
- Data Continuity in a Changing System
- Lock
- Segregate
- Replicate
- Reload
- Mixing Data Continuity Approaches
- Conclusion
- Index
O'Reilly Media - inne książki
-
Large language models (LLMs) and generative AI are rapidly changing the healthcare industry. These technologies have the potential to revolutionize healthcare by improving the efficiency, accuracy, and personalization of care. This practical book shows healthcare leaders, researchers, data scient...(149.94 zł najniższa cena z 30 dni)
149.89 zł
199.00 zł(-25%) -
With hundreds of tools preinstalled, the Kali Linux distribution makes it easier for security professionals to get started with security testing quickly. But with more than 600 tools in its arsenal, Kali Linux can also be overwhelming. The new edition of this practical book covers updates to the ...(162.32 zł najniższa cena z 30 dni)
162.21 zł
209.00 zł(-22%) -
Learn how to implement and manage a modern customer data platform (CDP) through the Salesforce Data Cloud platform. This practical book provides a comprehensive overview that shows architects, administrators, developers, data engineers, and marketers how to ingest, store, and manage real-time cus...(185.89 zł najniższa cena z 30 dni)
185.84 zł
249.00 zł(-25%) -
Real-time applications are becoming the norm today. But building a model that works properly requires real-time data from the source, in-flight stream processing, and low latency serving of its analytics. With this practical book, data engineers, data architects, and data analysts will learn how ...(210.70 zł najniższa cena z 30 dni)
210.20 zł
279.00 zł(-25%) -
Methods of delivering software are constantly evolving in order to increase speed to market without sacrificing reliability and stability. Mastering development end to end, from version control to production, and building production-ready code is now more important than ever. Continuous deploymen...(172.22 zł najniższa cena z 30 dni)
171.72 zł
229.00 zł(-25%) -
As the transformation to hybrid multicloud accelerates, businesses require a structured approach to securing their workloads. Adopting zero trust principles demands a systematic set of practices to deliver secure solutions. Regulated businesses, in particular, demand rigor in the architectural pr...(153.98 zł najniższa cena z 30 dni)
153.48 zł
209.00 zł(-27%) -
This concise yet comprehensive guide explains how to adopt a data lakehouse architecture to implement modern data platforms. It reviews the design considerations, challenges, and best practices for implementing a lakehouse and provides key insights into the ways that using a lakehouse can impact ...(181.73 zł najniższa cena z 30 dni)
181.63 zł
249.00 zł(-27%) -
In today's fast-paced world, more and more organizations require rapid application development with reduced development costs and increased productivity. This practical guide shows application developers how to use PowerApps, Microsoft's no-code/low-code application framework that helps developer...(151.27 zł najniższa cena z 30 dni)
150.77 zł
209.00 zł(-28%) -
Welcome to the systems age, where software professionals are no longer building software&emdash;we're building systems of software. Change is continuously deployed across software ecosystems coordinated by responsive infrastructure. In this world of increasing relational complexity, we need t...(141.24 zł najniższa cena z 30 dni)
141.04 zł
209.00 zł(-33%) -
This book provides an ideal guide for Python developers who want to learn how to build applications with large language models. Authors Olivier Caelen and Marie-Alice Blete cover the main features and benefits of GPT-4 and GPT-3.5 models and explain how they work. You'll also get a step-by-step g...(143.43 zł najniższa cena z 30 dni)
143.33 zł
209.00 zł(-31%)
Dzieki opcji "Druk na żądanie" do sprzedaży wracają tytuły Grupy Helion, które cieszyły sie dużym zainteresowaniem, a których nakład został wyprzedany.
Dla naszych Czytelników wydrukowaliśmy dodatkową pulę egzemplarzy w technice druku cyfrowego.
Co powinieneś wiedzieć o usłudze "Druk na żądanie":
- usługa obejmuje tylko widoczną poniżej listę tytułów, którą na bieżąco aktualizujemy;
- cena książki może być wyższa od początkowej ceny detalicznej, co jest spowodowane kosztami druku cyfrowego (wyższymi niż koszty tradycyjnego druku offsetowego). Obowiązująca cena jest zawsze podawana na stronie WWW książki;
- zawartość książki wraz z dodatkami (płyta CD, DVD) odpowiada jej pierwotnemu wydaniu i jest w pełni komplementarna;
- usługa nie obejmuje książek w kolorze.
Masz pytanie o konkretny tytuł? Napisz do nas: sklep[at]helion.pl.
Książka, którą chcesz zamówić pochodzi z końcówki nakładu. Oznacza to, że mogą się pojawić drobne defekty (otarcia, rysy, zagięcia).
Co powinieneś wiedzieć o usłudze "Końcówka nakładu":
- usługa obejmuje tylko książki oznaczone tagiem "Końcówka nakładu";
- wady o których mowa powyżej nie podlegają reklamacji;
Masz pytanie o konkretny tytuł? Napisz do nas: sklep[at]helion.pl.
Książka drukowana
Oceny i opinie klientów: Infrastructure as Code. 2nd Edition Kief Morris (0) Weryfikacja opinii następuję na podstawie historii zamówień na koncie Użytkownika umieszczającego opinię. Użytkownik mógł otrzymać punkty za opublikowanie opinii uprawniające do uzyskania rabatu w ramach Programu Punktowego.