Infrastructure as code dynamic systems for the cloud age
Gespeichert in:
| 1. Verfasser: | |
|---|---|
| Format: | Elektronisch E-Book |
| Sprache: | English |
| Veröffentlicht: |
Beijing
O'Reilly
[2021]
|
| Ausgabe: | Second edition |
| Schlagworte: | |
| Online-Zugang: | DE-1050 |
| Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
MARC
| LEADER | 00000nam a2200000 c 4500 | ||
|---|---|---|---|
| 001 | BV047630545 | ||
| 003 | DE-604 | ||
| 005 | 00000000000000.0 | ||
| 007 | cr|uuu---uuuuu | ||
| 008 | 211208s2021 xx o|||| 00||| eng d | ||
| 020 | |a 9781098114626 |9 978-1-098-11462-6 | ||
| 035 | |a (OCoLC)1289774822 | ||
| 035 | |a (DE-599)BVBBV047630545 | ||
| 040 | |a DE-604 |b ger |e rda | ||
| 041 | 0 | |a eng | |
| 049 | |a DE-1050 | ||
| 084 | |a ST 200 |0 (DE-625)143611: |2 rvk | ||
| 100 | 1 | |a Morris, Kief |e Verfasser |0 (DE-588)1108594522 |4 aut | |
| 245 | 1 | 0 | |a Infrastructure as code |b dynamic systems for the cloud age |c Kief Morris |
| 250 | |a Second edition | ||
| 264 | 1 | |a Beijing |b O'Reilly |c [2021] | |
| 300 | |a 1 Online-Ressource | ||
| 336 | |b txt |2 rdacontent | ||
| 337 | |b c |2 rdamedia | ||
| 338 | |b cr |2 rdacarrier | ||
| 505 | 8 | |a Intro -- Preface -- Why I Wrote This Book -- What's New and Different in This Edition -- What's Next -- What This Book Is and Isn't -- Some History of Infrastructure as Code -- Who This Book Is For -- Principles, Practices, and Patterns -- The ShopSpinner Examples -- Conventions Used in This Book -- O'Reilly 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 | |
| 505 | 8 | |a Objection: "We don't 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 | |
| 505 | 8 | |a 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 | |
| 505 | 8 | |a 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 | |
| 505 | 8 | |a 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 -- Patterns and Antipatterns for Structuring Stacks -- Antipattern: Monolithic Stack -- Motivation -- Applicability -- Consequences -- Implementation -- Related patterns -- Pattern: Application Group Stack -- Motivation -- Applicability -- Consequences -- Implementation -- Related patterns -- Pattern: Service Stack -- Motivation -- Applicability -- Consequences -- Implementation | |
| 650 | 4 | |a Coding theory | |
| 650 | 7 | |a Coding theory |2 fast | |
| 650 | 0 | 7 | |a Cloud Computing |0 (DE-588)7623494-0 |2 gnd |9 rswk-swf |
| 689 | 0 | 0 | |a Cloud Computing |0 (DE-588)7623494-0 |D s |
| 689 | 0 | |5 DE-604 | |
| 776 | 0 | 8 | |i Erscheint auch als |n Druck-Ausgabe |z 978-1-098-11467-1 |
| 912 | |a ZDB-30-PQE | ||
| 943 | 1 | |a oai:aleph.bib-bvb.de:BVB01-033014966 | |
| 966 | e | |u https://ebookcentral.proquest.com/lib/th-deggendorf/detail.action?docID=6422000 |l DE-1050 |p ZDB-30-PQE |q FHD01_PQE_Kauf |x Aggregator |3 Volltext | |
Datensatz im Suchindex
| _version_ | 1819311778062925824 |
|---|---|
| any_adam_object | |
| author | Morris, Kief |
| author_GND | (DE-588)1108594522 |
| author_facet | Morris, Kief |
| author_role | aut |
| author_sort | Morris, Kief |
| author_variant | k m km |
| building | Verbundindex |
| bvnumber | BV047630545 |
| classification_rvk | ST 200 |
| collection | ZDB-30-PQE |
| contents | Intro -- Preface -- Why I Wrote This Book -- What's New and Different in This Edition -- What's Next -- What This Book Is and Isn't -- Some History of Infrastructure as Code -- Who This Book Is For -- Principles, Practices, and Patterns -- The ShopSpinner Examples -- Conventions Used in This Book -- O'Reilly 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 don't 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 -- Patterns and Antipatterns for Structuring Stacks -- Antipattern: Monolithic Stack -- Motivation -- Applicability -- Consequences -- Implementation -- Related patterns -- Pattern: Application Group Stack -- Motivation -- Applicability -- Consequences -- Implementation -- Related patterns -- Pattern: Service Stack -- Motivation -- Applicability -- Consequences -- Implementation |
| ctrlnum | (OCoLC)1289774822 (DE-599)BVBBV047630545 |
| discipline | Informatik |
| edition | Second edition |
| format | Electronic eBook |
| fullrecord | <?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>04297nam a2200433 c 4500</leader><controlfield tag="001">BV047630545</controlfield><controlfield tag="003">DE-604</controlfield><controlfield tag="005">00000000000000.0</controlfield><controlfield tag="007">cr|uuu---uuuuu</controlfield><controlfield tag="008">211208s2021 xx o|||| 00||| eng d</controlfield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">9781098114626</subfield><subfield code="9">978-1-098-11462-6</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(OCoLC)1289774822</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-599)BVBBV047630545</subfield></datafield><datafield tag="040" ind1=" " ind2=" "><subfield code="a">DE-604</subfield><subfield code="b">ger</subfield><subfield code="e">rda</subfield></datafield><datafield tag="041" ind1="0" ind2=" "><subfield code="a">eng</subfield></datafield><datafield tag="049" ind1=" " ind2=" "><subfield code="a">DE-1050</subfield></datafield><datafield tag="084" ind1=" " ind2=" "><subfield code="a">ST 200</subfield><subfield code="0">(DE-625)143611:</subfield><subfield code="2">rvk</subfield></datafield><datafield tag="100" ind1="1" ind2=" "><subfield code="a">Morris, Kief</subfield><subfield code="e">Verfasser</subfield><subfield code="0">(DE-588)1108594522</subfield><subfield code="4">aut</subfield></datafield><datafield tag="245" ind1="1" ind2="0"><subfield code="a">Infrastructure as code</subfield><subfield code="b">dynamic systems for the cloud age</subfield><subfield code="c">Kief Morris</subfield></datafield><datafield tag="250" ind1=" " ind2=" "><subfield code="a">Second edition</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="a">Beijing</subfield><subfield code="b">O'Reilly</subfield><subfield code="c">[2021]</subfield></datafield><datafield tag="300" ind1=" " ind2=" "><subfield code="a">1 Online-Ressource</subfield></datafield><datafield tag="336" ind1=" " ind2=" "><subfield code="b">txt</subfield><subfield code="2">rdacontent</subfield></datafield><datafield tag="337" ind1=" " ind2=" "><subfield code="b">c</subfield><subfield code="2">rdamedia</subfield></datafield><datafield tag="338" ind1=" " ind2=" "><subfield code="b">cr</subfield><subfield code="2">rdacarrier</subfield></datafield><datafield tag="505" ind1="8" ind2=" "><subfield code="a">Intro -- Preface -- Why I Wrote This Book -- What's New and Different in This Edition -- What's Next -- What This Book Is and Isn't -- Some History of Infrastructure as Code -- Who This Book Is For -- Principles, Practices, and Patterns -- The ShopSpinner Examples -- Conventions Used in This Book -- O'Reilly 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</subfield></datafield><datafield tag="505" ind1="8" ind2=" "><subfield code="a">Objection: "We don't 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</subfield></datafield><datafield tag="505" ind1="8" ind2=" "><subfield code="a">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</subfield></datafield><datafield tag="505" ind1="8" ind2=" "><subfield code="a">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</subfield></datafield><datafield tag="505" ind1="8" ind2=" "><subfield code="a">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 -- Patterns and Antipatterns for Structuring Stacks -- Antipattern: Monolithic Stack -- Motivation -- Applicability -- Consequences -- Implementation -- Related patterns -- Pattern: Application Group Stack -- Motivation -- Applicability -- Consequences -- Implementation -- Related patterns -- Pattern: Service Stack -- Motivation -- Applicability -- Consequences -- Implementation</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Coding theory</subfield></datafield><datafield tag="650" ind1=" " ind2="7"><subfield code="a">Coding theory</subfield><subfield code="2">fast</subfield></datafield><datafield tag="650" ind1="0" ind2="7"><subfield code="a">Cloud Computing</subfield><subfield code="0">(DE-588)7623494-0</subfield><subfield code="2">gnd</subfield><subfield code="9">rswk-swf</subfield></datafield><datafield tag="689" ind1="0" ind2="0"><subfield code="a">Cloud Computing</subfield><subfield code="0">(DE-588)7623494-0</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="0" ind2=" "><subfield code="5">DE-604</subfield></datafield><datafield tag="776" ind1="0" ind2="8"><subfield code="i">Erscheint auch als</subfield><subfield code="n">Druck-Ausgabe</subfield><subfield code="z">978-1-098-11467-1</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">ZDB-30-PQE</subfield></datafield><datafield tag="943" ind1="1" ind2=" "><subfield code="a">oai:aleph.bib-bvb.de:BVB01-033014966</subfield></datafield><datafield tag="966" ind1="e" ind2=" "><subfield code="u">https://ebookcentral.proquest.com/lib/th-deggendorf/detail.action?docID=6422000</subfield><subfield code="l">DE-1050</subfield><subfield code="p">ZDB-30-PQE</subfield><subfield code="q">FHD01_PQE_Kauf</subfield><subfield code="x">Aggregator</subfield><subfield code="3">Volltext</subfield></datafield></record></collection> |
| id | DE-604.BV047630545 |
| illustrated | Not Illustrated |
| indexdate | 2024-12-24T09:01:56Z |
| institution | BVB |
| isbn | 9781098114626 |
| language | English |
| oai_aleph_id | oai:aleph.bib-bvb.de:BVB01-033014966 |
| oclc_num | 1289774822 |
| open_access_boolean | |
| owner | DE-1050 |
| owner_facet | DE-1050 |
| physical | 1 Online-Ressource |
| psigel | ZDB-30-PQE ZDB-30-PQE FHD01_PQE_Kauf |
| publishDate | 2021 |
| publishDateSearch | 2021 |
| publishDateSort | 2021 |
| publisher | O'Reilly |
| record_format | marc |
| spelling | Morris, Kief Verfasser (DE-588)1108594522 aut Infrastructure as code dynamic systems for the cloud age Kief Morris Second edition Beijing O'Reilly [2021] 1 Online-Ressource txt rdacontent c rdamedia cr rdacarrier Intro -- Preface -- Why I Wrote This Book -- What's New and Different in This Edition -- What's Next -- What This Book Is and Isn't -- Some History of Infrastructure as Code -- Who This Book Is For -- Principles, Practices, and Patterns -- The ShopSpinner Examples -- Conventions Used in This Book -- O'Reilly 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 don't 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 -- Patterns and Antipatterns for Structuring Stacks -- Antipattern: Monolithic Stack -- Motivation -- Applicability -- Consequences -- Implementation -- Related patterns -- Pattern: Application Group Stack -- Motivation -- Applicability -- Consequences -- Implementation -- Related patterns -- Pattern: Service Stack -- Motivation -- Applicability -- Consequences -- Implementation Coding theory Coding theory fast Cloud Computing (DE-588)7623494-0 gnd rswk-swf Cloud Computing (DE-588)7623494-0 s DE-604 Erscheint auch als Druck-Ausgabe 978-1-098-11467-1 |
| spellingShingle | Morris, Kief Infrastructure as code dynamic systems for the cloud age Intro -- Preface -- Why I Wrote This Book -- What's New and Different in This Edition -- What's Next -- What This Book Is and Isn't -- Some History of Infrastructure as Code -- Who This Book Is For -- Principles, Practices, and Patterns -- The ShopSpinner Examples -- Conventions Used in This Book -- O'Reilly 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 don't 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 -- Patterns and Antipatterns for Structuring Stacks -- Antipattern: Monolithic Stack -- Motivation -- Applicability -- Consequences -- Implementation -- Related patterns -- Pattern: Application Group Stack -- Motivation -- Applicability -- Consequences -- Implementation -- Related patterns -- Pattern: Service Stack -- Motivation -- Applicability -- Consequences -- Implementation Coding theory Coding theory fast Cloud Computing (DE-588)7623494-0 gnd |
| subject_GND | (DE-588)7623494-0 |
| title | Infrastructure as code dynamic systems for the cloud age |
| title_auth | Infrastructure as code dynamic systems for the cloud age |
| title_exact_search | Infrastructure as code dynamic systems for the cloud age |
| title_full | Infrastructure as code dynamic systems for the cloud age Kief Morris |
| title_fullStr | Infrastructure as code dynamic systems for the cloud age Kief Morris |
| title_full_unstemmed | Infrastructure as code dynamic systems for the cloud age Kief Morris |
| title_short | Infrastructure as code |
| title_sort | infrastructure as code dynamic systems for the cloud age |
| title_sub | dynamic systems for the cloud age |
| topic | Coding theory Coding theory fast Cloud Computing (DE-588)7623494-0 gnd |
| topic_facet | Coding theory Cloud Computing |
| work_keys_str_mv | AT morriskief infrastructureascodedynamicsystemsforthecloudage |