Implementing Continuous Delivery
This course provides you with an understanding of the concepts and principles surrounding Continuous Integration/Continous Delivery (CI/CD) to help you prepare for the AWS Certified Developer - Associate exam.
- How to set up your development environment
- How version control works
- How to begin implementing testing in your environment
- The why and how of database schema migrations
- What Jenkins is and why you should care
- Define continuous delivery and continuous deployment
- Describe some of the code level changes that will help support continuously delivery
- Describe the pros and cons for monoliths and microservices
- Explain blue / green & canary deployments
- Explain the pros and cons of mutable and immutable servers
- Identify some of the tools that are used for continuous delivery
Welcome back to Introduction to Continuous Delivery. I'm Ben Lambert, and I'll be your instructor for this lecture. In this summary, we'll review what we've covered so far.
Now we've covered a lot of information in this course, so I wanted to do a quick recap to make sure that some of what I consider to be the high level important points aren't lost. Alright, let's run through them quickly.
First, if you're going to deliver code regularly throughout the day, it needs to be able to run, even if some features aren't complete.
Next, modular coding practices will make for code that's easier to test and maintain.
Number three, security needs to be considered throughout the entire software life cycle.
Four, start most all new development as a monolith.
Number five, gradually refactor monoliths that are too large into microservices.
Number six, immutable servers are great, however mutable servers can also work as long as you're careful to ensure that they're not snowflake servers.
Number seven, there are a lot of options for no or low downtime deployments, such as blue, green, and canary.
Number eight, the list of tools that exists in DevOps and the Continuous Delivery space is longer than the Great Wall of China. Well, not really, but it's pretty long.
Number nine, your CD process should make your releases so boring that you may not even know that new changes went live.
And number 10, finally, all companies that are considered unicorns are using continuous delivery practices, and it's not a secret why.
So, this has been Introduction to Continuous Delivery. Thanks for taking the time to watch, I hope this has been useful to you and that you've gotten something out of this.
If there are aspects of Continuous Delivery that you'd like to know more about, please let us know at email@example.com.
I hope to hear from you!
I'm Ben Lambert, thanks for watching!
Ben Lambert is a software engineer and was previously the lead author for DevOps and Microsoft Azure training content at Cloud Academy. His courses and learning paths covered Cloud Ecosystem technologies such as DC/OS, configuration management tools, and containers. As a software engineer, Ben’s experience includes building highly available web and mobile apps. When he’s not building software, he’s hiking, camping, or creating video games.