DevOps: A Manifesto

DevOps: A Manifesto

About the Book

DevOps: A Manifesto seeks to provide a continually updated perspective and text on the evolution and implementation of the new style of systems operations and software development known as DevOps. DevOps: A Manifesto is intended to be a guide for small groups of systems engineers in greenfield environments interested and engaged in continuous delivery engineering methodologies and the production of Software As A Service systems. As such the book has a special emphasis on web operations. However, many aspects of the methodologies and workflows presented within are easily applicable to line-of-business environments where quick and reliable change must meet high-availability expectations.

DevOps: A Manifesto shows you who, what, and why.

Structure in Progress

  • Introduction
  • Epoch Time
    • A brief history of systems development and operations, from the unified tentative beginning of development and operations through the siloed division-of-labour approach that characterised the punch card era.
  • Combinatorial Conceptions
    • Explores the re-emergence of the iterative development methods which were uncommon during the punchcard era. We examine the discussions and, for DevOps, framing references which birthed the early new iterative software development movement and through its maturation into mainstream engineering consciousness during the early to mid 90's.
  • The Paradigm Shifts
    • Enter DevOps - a bird's eye view.
  • A New Engineering
    • This chapter expands on the concept of aligning Development and Operations into a single entity focused on the delivery of actual value. What practices characterise the DevOps Movement. How should one organise a DevOps team? What does a productive DevOps team look like? How should it work? What should it do? How does it plan? How should it execute? How does it integrate with the rest of the organisation?
  • With Great Power
    • What can a great DevOps team accomplish?
  • Comes Great Responsibility
    • How does a DevOps team detect and deal with failure? How does a DevOps team address unmet needs? How does a team evolve and change in response to organisational pressures? How does it scale? When is DevOps the wrong way to address a problem?
  • Epilogue
  • Share this book

  • Categories

    • Software
    • Agile
    • Textbooks

About the Author

Justin 'J' Lynn
Justin 'J' Lynn

Justin Lynn, known to his friends and colleagues as 'J', is a Co-founder and the Princpal Engineer at Infrastructory with several years of professional experience and a lifetime of interest in the art of designing, building, implementing, and running large software systems. His current environment of choice is GNU/Linux, for both server and desktop use. His programming language and community of choice for the last eight years has been Ruby and its ecosystem. As for system configuration tools he prefers Opscode Chef. On any given day you can find him fixing broken electronics, doing IT work, planning for the next expansion of his client's systems, working on his or other people's various open source projects, or indulging in a good book.

The Leanpub 60 Day 100% Happiness Guarantee

Within 60 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.

Now, this is technically risky for us, since you'll have the book or course files either way. But we're so confident in our products and services, and in our authors and readers, that we're happy to offer a full money back guarantee for everything we sell.

You can only find out how good something is by trying it, and because of our 100% money back guarantee there's literally no risk to do so!

So, there's no reason not to click the Add to Cart button, is there?

See full terms...

80% Royalties. Earn $16 on a $20 book.

We pay 80% royalties. That's not a typo: you earn $16 on a $20 sale. If we sell 5000 non-refunded copies of your book or course for $20, you'll earn $80,000.

(Yes, some authors have already earned much more than that on Leanpub.)

In fact, authors have earnedover $13 millionwriting, publishing and selling on Leanpub.

Learn more about writing on Leanpub

Free Updates. DRM Free.

If you buy a Leanpub book, you get free updates for as long as the author updates the book! Many authors use Leanpub to publish their books in-progress, while they are writing them. All readers get free updates, regardless of when they bought the book or how much they paid (including free).

Most Leanpub books are available in PDF (for computers) and EPUB (for phones, tablets and Kindle). The formats that a book includes are shown at the top right corner of this page.

Finally, Leanpub books don't have any DRM copy-protection nonsense, so you can easily read them on any supported device.

Learn more about Leanpub's ebook formats and where to read them

Write and Publish on Leanpub

You can use Leanpub to easily write, publish and sell in-progress and completed ebooks and online courses!

Leanpub is a powerful platform for serious authors, combining a simple, elegant writing and publishing workflow with a store focused on selling in-progress ebooks.

Leanpub is a magical typewriter for authors: just write in plain text, and to publish your ebook, just click a button. (Or, if you are producing your ebook your own way, you can even upload your own PDF and/or EPUB files and then publish with one click!) It really is that easy.

Learn more about writing on Leanpub