Book Image

Accelerate DevOps with GitHub

By : Michael Kaufmann
Book Image

Accelerate DevOps with GitHub

By: Michael Kaufmann

Overview of this book

This practical guide to DevOps uses GitHub as the DevOps platform and shows how you can leverage the power of GitHub for collaboration, lean management, and secure and fast software delivery. The chapters provide simple solutions to common problems, thereby helping teams that are already on their DevOps journey to further advance into DevOps and speed up their software delivery performance. From finding the right metrics to measure your success to learning from other teams’ success stories without merely copying what they’ve done, this book has it all in one place. As you advance, you’ll find out how you can leverage the power of GitHub to accelerate your value delivery – by making work visible with GitHub Projects, measuring the right metrics with GitHub Insights, using solid and proven engineering practices with GitHub Actions and Advanced Security, and moving to event-based and loosely coupled software architecture. By the end of this GitHub book, you'll have understood what factors influence software delivery performance and how you can measure your capabilities, thus realizing where you stand in your journey and how you can move forward.
Table of Contents (31 chapters)
1
Part 1: Lean Management and Collaboration
7
Part 2: Engineering DevOps Practices
14
Part 3: Release with Confidence
19
Part 4: Software Architecture
22
Part 5: Lean Product Management
25
Part 6: GitHub for your Enterprise

Loosely coupled systems

All developers that have worked at least once on a tightly coupled, monolithic application know the problems it induces. The communication overhead and the meetings needed to perform bigger changes. New bugs that occur after fixing a bug in another part of the application. Changes that break functionality from other developers. All these problems lead to fear of integrating and deploying and slow down developer velocity.

When designing your system and software, you should focus on the following characteristics:

  • Deployability: Can each team release their application independent of other applications or teams?
  • Testability: Can each team do most of their testing without requiring a test environment in which multiple independent solutions from other teams must be deployed together?

The team size here is a small two-pizza team (see Chapter 17, Empower Your Teams). If you design your systems for the deployability and testability of small teams...