DevOps.com Unpacks Opsani’s Continuous Optimization

At Opsani, we believe that DevOps needs a full-scale culture shift. For good reason, modern enterprises are rushing to adopt containers, and move their infrastructure into a DevOps paradigm, where new releases can arrive daily rather than quarterly. But as Don Macvittie asks over at DevOps.com: “What keeps track of the volume of change all of this introduces and delivers optimizations faster?”

The answer is usually: nothing. This is exactly the gap that Opsani is trying to fill. 

In his DevOps.com article, Macvittie does a great job of explaining the problem, and exploring how Opsani attempts to solve that problem. It’s an insightful, balanced and neutral write-up:

“The idea of continuous optimization appeals to me. Opsani have got the interfaces that one would expect to gather inputs, names such as Jenkins, DataDog and New Relic. They’ve got the interfaces to enact and test out changes too, with interfaces to products such as Kubernetes, Terraform, Rancher and Wavefront. So it certainly appears they’ve got the basics covered. Of course there are vendor interfaces I’d like to see that aren’t in the list of integrations, and no doubt the same is true for you. But the core is here, getting to the monitoring and management tools most companies use regularly.”

(The good news is: the integrations are coming!)

Head over here for the full write-up. Thanks to Don for a great article.

To learn more about Continuous Optimization, check out our whitepaper:

Download Continuous Optimization Whitepaper

 

Share This