The Value of DevOps
The Value of DevOps
See how adopting automation can bring you speed, quality, and peace of mind in this interview with JFrog co-founder and CTO, Yoav Landman.
Join the DZone community and get the full member experience.Join For Free
What are the most important elements of a successful DevOps methodology implementation?
Begin by accomplishing trust along the pipeline. You earn trust in the pipeline process by providing visibility, automation, metrics, flawless execution, will all components being highly available in immutable infrastructures, and the ability to scale economically as needed. We're seeing hybrid multi-cloud with big players while many smaller companies are committing to a single public cloud and then looking for other providers as they scale and look to manage expense.
How is security being integrated into DevOps?
Make sure what ends up in runtime is flawless. Xray scans for vulnerabilities, and license variation and custom issues like poorly performing components. All of this is baked into the pipeline. The distribution of artifacts to production or gateway to IoT device. JFrog distribution allows you to sign artifacts and see what you have in runtime verify they were produced by an authenticated entity and not changed. We also ensure that you're moving one atomic bundle in the runtime. A special version of Artifactory edge node only deals with certified release manuals and cannot deploy discrete artifacts that are not certified.
What are the most significant changes in the past year?
Kubernetes -- it's apparent to everyone it's achieving the same adoption as Docker. While it's complex it but provides tremendous flexibility.
What’s the greatest value of DevOps?
Quality with speed through automation and security via automated testing. You maintain very tight control over runtime. To run faster you need better shoes. Software must be more resilient as its running faster and processing more data.
What are some use cases you would like to highlight?
We have clients provisioning software to production data centers globally around the world. Financial, medical, intelligence, the vertical doesn't matter as much as the applications.
A lot of artifacts are getting bigger as the apps get bigger. We help clients bring changes quicker to edge locations, once there they scale according to load and may provision new versions of software.
If a client has 300 nodes, they go to Artifactory pull latest versions and run them in production. Just the fact you have a service or application, even a website driven by UI, deployed globally you have to update everywhere in a controlled way.
A big launch can affect demand for service in your European operations so you go from 10 to 50 servers dynamically provisioning the latest version of software from Artifactory closest to the client.
What's the future of DevOps from your perspective?
We have a vision of liquid software with automated software updates with full control over the operations. "As a service" is a utopia with regards to making updates without new releases.
What are your suggestions for developers with regards to DevOps?
Embrace automation unless you want to be woken up in the middle of the night. Adopt automation -- you get quality, speed, and eventually peace of mind.
Opinions expressed by DZone contributors are their own.