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 now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Continuous Delivery with Docker and Jenkins

You're reading from   Continuous Delivery with Docker and Jenkins Create secure applications by building complete CI/CD pipelines

Arrow left icon
Product type Paperback
Published in May 2019
Publisher Packt
ISBN-13 9781838552183
Length 350 pages
Edition 2nd Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
Rafał Leszko Rafał Leszko
Author Profile Icon Rafał Leszko
Rafał Leszko
Arrow right icon
View More author details
Toc

Table of Contents (16) Chapters Close

Preface 1. Section 1: Setting Up the Environment FREE CHAPTER
2. Introducing Continuous Delivery 3. Introducing Docker 4. Configuring Jenkins 5. Section 2: Architecting and Testing an Application
6. Continuous Integration Pipeline 7. Automated Acceptance Testing 8. Clustering with Kubernetes 9. Section 3: Deploying an Application
10. Configuration Management with Ansible 11. Continuous Delivery Pipeline 12. Advanced Continuous Delivery 13. Best practices 14. Assessment 15. Other Books You May Enjoy

Summary

This chapter was a mixture of various Continuous Delivery aspects that were not covered before. The key takeaways from the chapter are as follows:

  • Databases are an essential part of most applications, and should therefore be included in the Continuous Delivery process.
  • Database schema changes are stored in the version control system and managed by database migration tools.
  • There are two types of database schema changes: backwards-compatible and backwards-incompatible. While the first type is simple, the second requires a bit of overhead (split to multiple migrations spread over time).
  • A database should not be the central point of the whole system. The preferred solution is to provide each service with its own database.
  • The delivery process should always be prepared for a rollback scenario.
  • Three release patterns should always be considered: rolling updates, blue-green...
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 $19.99/month. Cancel anytime