In my last blog and video, I went through some of the issues you can have when having a single pipeline do both CI and CD for your applications. In this blog we go into HOW you can split these concepts. Mostly we dive into separation of concerns. Yes, I went there, another buzzword!
Fabian is a Cloud-Native Architect and Open Source Enthusiast. As one of the founders of Fullstaq, he is the technical heart and conscience of the company, helping customers and engineers with guidance and being a nice sparring partner.
To encompass Fabian's roles, we like to call him the TechFluencer. There is often a negative association with influencing or preaching some gospel and forcing opinions on others; instead, Fabian works closely with people to find out what those people and companies really want and need and makes sure the right resources from Fullstaq are made available to achieve those goals. Also, writing in the third person is something Fabian finds odd to do...
Please talk nerdy to Fabian; it is what he likes best!
We have used pipelines for the regular implementation of CI/CD principles for years, but we have come to a point where splitting CI from CD makes a lot of sense. Have you ever had to rethink your standard pipelines because it was growing in complexity and difficulty? In this blog, I go into the differences between CI and CD in the often-used acronym CI/CD. This blog is the …
Subscribe and Stay up to date
We are a fast-growing cloud-native IT Services company that helps both start-ups and enterprises realize their Kubernetes ambitions.