Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Continuous Delivery with Docker and Jenkins

You're reading from   Continuous Delivery with Docker and Jenkins Delivering software at scale

Arrow left icon
Product type Paperback
Published in Aug 2017
Publisher Packt
ISBN-13 9781787125230
Length 332 pages
Edition 1st Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
 Leszko Leszko
Author Profile Icon Leszko
Leszko
Arrow right icon
View More author details
Toc

Table of Contents (17) Chapters Close

Title Page
Credits
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Dedication
Preface
1. Introducing Continuous Delivery 2. Introducing Docker FREE CHAPTER 3. Configuring Jenkins 4. Continuous Integration Pipeline 5. Automated Acceptance Testing 6. Configuration Management with Ansible 7. Continuous Delivery Pipeline 8. Clustering with Docker Swarm 9. Advanced Continuous Delivery

Advanced Docker Swarm


Docker Swarm offers a lot of interesting features that are useful in the Continuous Delivery process. In this section, we will walk through the most important ones.

Rolling updates

Imagine you deploy a new version of your application. You need to update all replicas in the cluster. One option would be to stop the whole Docker Swarm service and to run a new one from the updated Docker image. Such approach, however, causes downtime between the moment when the service is stopped and the moment when the new one is started. In the Continuous Delivery process, downtime is not acceptable, since the deployment can take place after every source code change, which is simply often. Then, how can we provide zero-downtime deployment in a cluster? This is the role of rolling updates.

A rolling update is an automatic method for replacing a service, replica by a replica, in a way that some of the replicas are working all the time. Docker Swarm uses rolling updates by default, and they...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime
Visually different images