Practical Guide to Continuous Delivery, A (häftad)
Fler böcker inom
Häftad (Paperback)
Antal sidor
231 x 175 x 20 mm
499 g
Antal komponenter
Practical Guide to Continuous Delivery, A (häftad)

Practical Guide to Continuous Delivery, A

Häftad Engelska, 2017-03-03
  • Skickas inom 7-10 vardagar.
  • Gratis frakt inom Sverige över 159 kr för privatpersoner.
Kan levereras innan julafton!
Using Continuous Delivery, you can bring software into production more rapidly, with greater reliability. A Practical Guide to Continuous Delivery is a 100% practical guide to building Continuous Delivery pipelines that automate rollouts, improve reproducibility, and dramatically reduce risk.


Eberhard Wolff introduces a proven Continuous Delivery technology stack, including Docker, Chef, Vagrant, Jenkins, Graphite, the ELK stack, JBehave, and Gatling. He guides you through applying these technologies throughout build, continuous integration, load testing, acceptance testing, and monitoring. Wolffs start-to-finish example projects offer the basis for your own experimentation, pilot programs, and full-fledged deployments.

A Practical Guide to Continuous Delivery is for everyone who wants to introduce Continuous Delivery, with or without DevOps. For managers, it introduces core processes, requirements, benefits, and technical consequences. Developers, administrators, and architects will gain essential skills for implementing and managing pipelines, and for integrating Continuous Delivery smoothly into software architectures and IT organizations.

  • Understand the problems that Continuous Delivery solves, and how it solves them
  • Establish an infrastructure for maximum software automation
  • Leverage virtualization and Platform as a Service (PAAS) cloud solutions
  • Implement build automation and continuous integration with Gradle, Maven, and Jenkins
  • Perform static code reviews with SonarQube and repositories to store build artifacts
  • Establish automated GUI and textual acceptance testing with behavior-driven design
  • Ensure appropriate performance via capacity testing
  • Check new features and problems with exploratory testing
  • Minimize risk throughout automated production software rollouts
  • Gather and analyze metrics and logs with Elasticsearch, Logstash, Kibana (ELK), and Graphite
  • Manage the introduction of Continuous Delivery into your enterprise
  • Architect software to facilitate Continuous Delivery of new capabilities

Visa hela texten

Passar bra ihop

  1. Practical Guide to Continuous Delivery, A
  2. +
  3. Microservices: A Practical Guide

De som köpt den här boken har ofta också köpt Microservices: A Practical Guide av Eberhard Wolff (häftad).

Köp båda 2 för 668 kr


Har du läst boken? Sätt ditt betyg »

Fler böcker av Eberhard Wolff

Övrig information

Eberhard Wolff, a Fellow at innoQ in Germany, has more than 15 years of experience as an architect and consultant working at the intersection of business and technology. He gives talks and keynote addresses at several international conferences, has served on multiple conference program committees, and has written more than 100 articles and books. His technological focus is on modern architectures-often involving cloud, continuous delivery, DevOps, microservices, and NoSQL. He is author of Microservices: Flexible Software Architecture.


Preface   xvii
Part I:  Foundations   1
Chapter 1:  Continuous Delivery: What and How?   3

1.1 Introduction: What Is Continuous Delivery?   3
1.2 Why Software Releases are So Complicated   3
1.2.1 Continuous Integration Creates Hope   4
1.2.2 Slow and Risky Processes   4
1.2.3 Its Possible to be Fast   4
1.3 Values of Continuous Delivery   4
1.3.1 Regularity   5
1.3.2 Traceability/Confirmability   6
1.3.3 Regression   6
1.4 Benefits of Continuous Delivery   6
1.4.1 Continuous Delivery for Time to Market   7
1.4.2 One Example   7
1.4.3 Implementing a Feature and Bringing It into Production   7
1.4.4 On to the Next Feature   7
1.4.5 Continuous Delivery Generates Competitive Advantages   8
1.4.6 Without Continuous Delivery   8
1.4.7 Continuous Delivery and Lean Startup   9
1.4.8 Effects on the Development Process   9
1.4.9 Continuous Delivery to Minimize Risk   10
1.4.10 Faster Feedback and Lean   13
1.5 Generations and Structure of a Continuous Delivery Pipeline   14
1.5.1 The Example   16
1.6 Conclusion   17
Endnotes   17
Chapter 2:  Providing Infrastructure   19
2.1 Introduction   19
2.1.1 Infrastructure Automation: An Example   20
2.2 Installation Scripts   21
2.2.1 Problems of Classical Installation Scripts   21
2.3 Chef   24
2.3.1 Chef versus Puppet   25
2.3.2 Other Alternatives   26
2.3.3 Technical Foundations   26
2.3.4 Chef Solo   33
2.3.5 Chef Solo: Conclusion   35
2.3.6 Knife and Chef Server   35
2.3.7 Chef Server: Conclusion   39
2.4 Vagrant   40
2.4.1 An Example with Chef and Vagrant   41
2.4.2 Vagrant: Conclusion   43
2.5 Docker   43
2.5.1 Dockers Solution   44
2.5.2 Creating Docker Containers   46
2.5.3 Running the Example Application with Docker   49
2.5.4 Docker and Vagrant   51
2.5.5 Docker Machine   53
2.5.6 Complex Configurations with Docker   55
2.5.7 Docker Compose   57
2.6 Immutable Server   60
2.6.1 Disadvantages of Idempotency   60
2.6.2 Immutable Server and Docker   61
2.7 Infrastructure as Code   61
2.7.1 Testing Infrastructure as Code   63
2.8 Platform as a Service (PaaS)   63
2.9 Handling Data and Databases   65
2.9.1 Handling Schemas   66
2.9.2 Test and Master Data   67
2.10 Conclusion   68
Endnotes   69

Part II:  The Continuous Delivery Pipeline   71
Chapter 3:  Build Automation and Continuous Integration   73

3.1 Introduction   73
3.1.1 Build Automation: An Example   74
3.2 Build Aut...