nach oben

2012 | Buch

DevOps for Developers

verfasst von: Michael Hüttermann

Verlag: Apress

Enthalten in: Springer Professional "Wirtschaft+Technik" , Springer Professional "Technik" , Springer Professional "Wirtschaft"

Einloggen, um Zugang zu erhalten

Über dieses Buch

DevOps for Developers delivers a practical, thorough introduction to approaches, processes and tools to foster collaboration between software development and operations. Efforts of Agile software development often end at the transition phase from development to operations. This book covers the delivery of software, this means “the last mile”, with lean practices for shipping the software to production and making it available to the end users, together with the integration of operations with earlier project phases (elaboration, construction, transition).

DevOps for Developers describes how to streamline the software delivery process and improve the cycle time (that is the time from inception to delivery). It will enable you to deliver software faster, in better quality and more aligned with individual requirements and basic conditions. And above all, work that is aligned with the “DevOps” approach makes even more fun!

Provides patterns and toolchains to integrate software development and operations Delivers an one-stop shop for kick-starting with DevOps Provides guidance how to streamline the software delivery process

Inhaltsverzeichnis

Frontmatter

Fundamentals

Frontmatter

Chapter 1. Beginning DevOps for Developers

Abstract

Welcome to DevOps for Developers. This book discusses approaches, processes, and tools for optimizing collaboration between software development and operations and bringing Agile approaches to all parts of the streamlined software delivery process.

Michael Hüttermann

Chapter 2. Introducing DevOps

Abstract

In this chapter, I’ll introduce the concept of DevOps. I’ll also summarize in which areas traditional projects suffer, what Agile has done in the past several years to improve this situation, and what is nevertheless still missing in many projects to day. With Agile, testers and programmers became developers, and with DevOps, developers and operations become DevOps. I will show that natural con fl icts between developers and operations often lead to the “blame game,” which can be resolved through use of the DevOps approach. DevOps leads to a “one team” approach where programmers, testers, and system administrators are involved in the development of the solution.

Michael Hüttermann

Chapter 3. Building Blocks of DevOps

Abstract

In this chapter, we’ll examine the building blocks of DevOps. We’ll talk about the metrics, and you’ll learn that the cycle time is the most important metric for both development and operations. We’ll also discuss how to improve and accelerate software delivery. Let’s start with measurement and metrics.

Michael Hüttermann

Metrics and Measurement View

Frontmatter

Chapter 4. Quality and Testing

Abstract

Everyone discusses quality and wants to improve it. However, not defining quality has the wonderful effect of allowing quality to be everything, including perks such as full pots of coffee on each table. Many projects have experienced excellent results by using tests as a vehicle for measuring quality. This chapter will discuss quality and tests and show their essential relevance for DevOps.

Michael Hüttermann

Chapter 5. Introduce Shared Incentives

Abstract

This chapter will discuss shared incentives. You’ll learn how to evolve a team from a working group and you’ll discover that goals, working agreements, and motivation are essential for creating shared incentives. I’ll introduce patterns to become a team. Finally, we go through two real-world success stories, which illustrate how to bring all of these different aspects together. But let’s start with the war story of the magic kingdoms.

Michael Hüttermann

Process View

Frontmatter

Chapter 6. Gain Fast Feedback

Abstract

In this chapter, I’ll introduce the DevOps area matrix, comprising four different areas, to introduce and catalog DevOps: to extend development to operations, to extend operations to development, to embed development into operations, and to embed operations into development. To each area, I’ll provide further details and examples. You’ll also learn that Kanban, a method for incrementally changing an underlying process, can be useful in applying DevOps. Finally, I’ll provide a concrete use case to bring all four areas of the DevOps matrix together and combine them with Kanban. Now let’s start discussing the DevOps area matrix.

Michael Hüttermann

Chapter 7. Unified and Holistic Approach

Abstract

This chapter will discuss a unified and holistic approach to software engineering. We’ll start with a discussion of concepts, particularly nonfunctional requirements. Then we’ll discuss one of the main dangers for collaboration between development and operations in more detail. Called a conceptual deficit, this can cause a discrepancy between business needs, project results, and expectations of operations.

Michael Hüttermann

Technical View

Frontmatter

Chapter 8. Automatic Releasing

Abstract

In earlier chapters, you learned about the importance of automation as a vehicle for reducing cycle time and for fostering collaboration between development and operations. In Chapter 3 you learned that automatic releasing is a building block of DevOps and that it can be a powerful strategy to decouple deployment and release.

Michael Hüttermann

Chapter 9. Infrastructure as Code

Abstract

Recent years have seen the rise of disciplines like continuous integration, test driven development, build/deployment automation, and more. All of these had a purpose to automate as many parts as possible of the lifecycle of a software product. However, the main focus often is the software itself, and the infrastructure on which the software runs is still quite often a “work of art.”

Michael Hüttermann

Chapter 10. Specification by Example

Abstract

One of the fundamental principles of DevOps is that any build that successfully passes the gauntlet of automated checks can potentially be delivered into production. Checks can specifically verify whether any new or updated code broke any existing feature. In other words, they guard against regression failures. It is for this reason that automated testing plays such a vital role in the DevOps process.

Michael Hüttermann

Backmatter

Titel: DevOps for Developers
verfasst von: Michael Hüttermann
Verlag: Apress
Electronic ISBN: 978-1-4302-4570-4
Print ISBN: 978-1-4302-4569-8
DOI: https://doi.org/10.1007/978-1-4302-4570-4