Continuous Integration and Delivery (CI/CD) | Microservices 101
Continuous Integration (CI) is the process of automatically building and testing your code on every source control commit. Continuous Delivery (CD) takes this further and automatically deploys the code to production on every commit. Used together these techniques allow code to be built, tested, and deployed automatically through a robust CI/CD pipeline.
Check out Confluent Developer to find more information and courses on how to build event driven microservices: https://cnfl.io/48FnKRB
ADDITIONAL RESOURCES
► 4 Must-Have Tests for Your Apache Kafka CI/CD with GitHub Actions: https://cnfl.io/3GnlvFP
► Use GitOps as an efficient CI/CD pipeline for Data Streaming: https://www.youtube.com/watch
► Migrate from Monoliths to Event-Driven Microservices: https://cnfl.io/3tsqlhu
► Event-Driven Microservices Architecture: https://cnfl.io/48FSYbj
► Microservices: An Introduction https://cnfl.io/3ZMt3up
CHAPTERS
00:00 - Intro
00:22 - Long Releases
00:59 - Testing and the Testing Pyramid
02:17 - Continuous Integration
02:51 - Automating Deployment
03:17 - Continuous Delivery
04:22 - Deployment vs Release
05:04 - Canary Deployments
06:01 - Closing
ABOUT CONFLUENT
Confluent is pioneering a fundamentally new category of data infrastructure focused on data in motion. Confluent’s cloud-native offering is the foundational platform for data in motion – designed to be the intelligent connective tissue enabling real-time data, from multiple sources, to constantly stream across the organization. With Confluent, organizations can meet the new business imperative of delivering rich, digital front-end customer experiences and transitioning to sophisticated, real-time, software-driven backend operations. To learn more, please visit www.confluent.io.
#microservices #apachekafka #kafka #confluent