The latest News and Information on DevOps, CI/CD, Automation and related technologies.
Continuous integration is the first half of the acronym CI/CD, with Continuous Delivery completing the second half. In this three-part article, we look at the two halves of CI/CD to define and understand them, and then, in part three, we talk about how Uptrends fits into your CI/CD processes. Let’s get started at the beginning with continuous integration.
Current cloud investments have been a boost for flexibility and productivity. The challenge is that there is a single point of failure with these platforms, requiring diversity of providers to reduce dependencies. The future of cloud computing will see effects from the ambitions and expansion of cloud providers themselves, as well as potential competition. This is especially true with Amazon, Google, and to a lesser extent Microsoft.
We’ve all been there. A new tool is trending, it is getting mentioned all over the place, and you get dropped into a conversation about it. The last thing you want to do is embarrass yourself by pronouncing something wrong and revealing you don’t know anything about the latest thing. We want to make sure you avoid that happening. When it comes to Kubernetes, there are really only four terms that you might need some help with pronouncing.
It’s 3 AM and you are roused out of sleep by the dull buzzing of your phone in the other room. Some sort of emergency, you conclude as you fumble with the lockscreen. There it is: an alert that the API governing user registration is acting up. When we think about the lag between time of incident and time to respond, it’s not just about how long the system went down. How long it physically takes us to respond to the problem also contributes to lost downtime.
