Browse Library
Sign In Start Free Trial
Close icon Search icon
Account
Browse Library Sign In Start Free Trial

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Practical DevOps
  • Table Of Contents Toc
Practical DevOps

Practical DevOps

By : joakim verona
5 (1)
Buy this Book
close
close
Practical DevOps

Practical DevOps

5 (1)
By: joakim verona
Buy this Book

Overview of this book

DevOps is a practical field that focuses on delivering business value as efficiently as possible. DevOps encompasses all the flows from code through testing environments to production environments. It stresses the cooperation between different roles, and how they can work together more closely, as the roots of the word imply—Development and Operations. After a quick refresher to DevOps and continuous delivery, we quickly move on to looking at how DevOps affects architecture. You'll create a sample enterprise Java application that you’ll continue to work with through the remaining chapters. Following this, we explore various code storage and build server options. You will then learn how to perform code testing with a few tools and deploy your test successfully. Next, you will learn how to monitor code for any anomalies and make sure it’s running properly. Finally, you will discover how to handle logs and keep track of the issues that affect processes
Table of Contents (12 chapters)
close
close
close
Preface
Icon
Preface
Icon
Who this book is for
Icon
What this book covers
Icon
To get the most out of this book
Icon
Get in touch
Lock Free Chapter
1
Introducing DevOps and Continuous Delivery
Icon
Introducing DevOps and Continuous Delivery
Icon
Introducing DevOps
Icon
How fast is fast?
Icon
The Agile wheel of wheels
Icon
Beware the cargo cult Agile fallacy
Icon
DevOps and ITIL
Icon
Summary
2
A View from Orbit
chevron up
Icon
A View from Orbit
Icon
The DevOps process and CD – an overview
Icon
Release management
Icon
Scrum, Kanban, and the delivery pipeline
Icon
Wrapping up – a complete example
Icon
Identifying bottlenecks
Icon
Summary
3
How DevOps Affects Architecture
Icon
How DevOps Affects Architecture
Icon
Introducing software architecture
Icon
The monolithic scenario
Icon
The Twelve Factors
Icon
Architecture rules of thumb
Icon
Back to the monolithic scenario
Icon
A practical example
Icon
Handling database migrations
Icon
Manual installation
Icon
Microservices
Icon
Interlude – Conway's law
Icon
How to keep service interfaces forward compatible
Icon
Microservices and the data tier
Icon
DevOps, architecture, and resilience
Icon
Summary
4
Everything is Code
Icon
Everything is Code
Icon
The need for source code control
Icon
The history of source code management
Icon
Roles and code
Icon
Which source code management system?
Icon
A word about source code management system migrations
Icon
Shared authentication
Icon
Hosted Git servers
Icon
Large binary files
Icon
Trying out different Git server implementations
Icon
Docker intermission
Icon
Gerrit
Icon
The pull request model
Icon
GitLab
Icon
Summary
5
Building the Code
Icon
Building the Code
Icon
Why do we build code?
Icon
The many faces of build systems
Icon
The Jenkins build server
Icon
Managing build dependencies
Icon
The final artifact
Icon
Cheating with FPM
Icon
Continuous Integration
Icon
Continuous Delivery
Icon
Jenkins plugins
Icon
The host server
Icon
Build slaves
Icon
Software on the host
Icon
Triggers
Icon
Job chaining and build pipelines
Icon
A look at the Jenkins filesystem layout
Icon
Build servers and Infrastructure as Code
Icon
Build phases
Icon
Alternative build servers
Icon
Collating quality measures
Icon
About build status visualization
Icon
Taking build errors seriously
Icon
Robustness
Icon
Summary
6
Testing the Code
Icon
Testing the Code
Icon
Manual testing
Icon
Pros and cons with test automation
Icon
Unit testing
Icon
xUnit in general and JUnit in particular
Icon
Mocking
Icon
Test coverage
Icon
Automated integration testing
Icon
Performance testing
Icon
Automated acceptance testing
Icon
Automated GUI testing
Icon
Integrating Selenium tests in Jenkins
Icon
JavaScript testing
Icon
Testing backend integration points
Icon
Test-driven development
Icon
REPL-driven development
Icon
A complete test automation scenario
Icon
Summary
7
Deploying the Code
Icon
Deploying the Code
Icon
Why are there so many deployment systems?
Icon
Virtualization stacks
Icon
Executing code on the client
Icon
The Puppet master and Puppet agents
Icon
Ansible
Icon
Deploying with Chef
Icon
Deploying with SaltStack
Icon
Salt versus Ansible versus Puppet execution models
Icon
Vagrant
Icon
Deploying with Docker
Icon
Comparison tables
Icon
Cloud solutions
Icon
AWS
Icon
Azure
Icon
Summary
8
Monitoring the Code
Icon
Monitoring the Code
Icon
Nagios
Icon
Munin
Icon
Ganglia
Icon
Graphite
Icon
Log handling
Icon
Summary
9
Issue Tracking
Icon
Issue Tracking
Icon
What are issue trackers used for?
Icon
Some examples of workflows and issues
Icon
What do we need from an issue tracker?
Icon
Problems with issue tracker proliferation
Icon
All the trackers
Icon
Summary
10
The Internet of Things and DevOps
Icon
The Internet of Things and DevOps
Icon
Introducing the IoT and DevOps
Icon
The future of the IoT according to the market
Icon
Machine-to-machine communication
Icon
IoT deployment affects software architecture
Icon
IoT deployment security
Icon
Okay, but what about DevOps and the IoT again?
Icon
A hands-on lab with an IoT device for DevOps
Icon
Summary
11
Other Books You May Enjoy
Icon
Other Books You May Enjoy
Icon
Leave a review - let other readers know what you think

The DevOps process and Continuous Delivery – an overview

There is a lot of detail in the following overview image of the Continuous Delivery pipeline, and you most likely won't be able to read all the text. Don't worry about this just now; we are going to delve deeper into the details as we go along.

For the time being, it is enough to understand that when we work with DevOps, we work with large and complex processes in a large and complex context.

An example of a Continuous Delivery pipeline in a large organization is introduced in the following image:

The DevOps process and Continuous Delivery – an overview

While the basic outline of this image holds true surprisingly often, regardless of the organization. There are, of course, differences, depending on the size of the organization and the complexity of the products that are being developed.

The early parts of the chain, that is, the developer environments and the Continuous Integration environment, are normally very similar.

The number and types of testing environments vary greatly...

CONTINUE READING
83
Tech Concepts
36
Programming languages
73
Tech Tools
Icon Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.
Icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Icon 50+ new titles added per month and exclusive early access to books as they are being written.
Practical DevOps
End of Section 2
Next Section
notes
bookmark Notes and Bookmarks search Search in title playlist Add to playlist font-size Font size

Change the font size

margin-width Margin width

Change margin width

day-mode Day/Sepia/Night Modes

Change background colour

Close icon Search
Country selected
Close icon Your notes and bookmarks

Confirmation

Modal Close icon
claim successful
Order Page Read Now

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY

Submit Your Feedback

Modal Close icon
Modal Close icon
Modal Close icon