Pivotal + VMware: Transforming how more of the world builds software

DevOps: 신속하고 신뢰 가능하게 앱을 전달하는 협업적 사고 방식

잘 설계되어 강력한 DevOps 적용으로 소프트웨어 배포 속도와 안정성이 증가하는 동시에 오류 복원 시간과 소프트웨어 업데이트 지연 시간이 줄어들고 있음을 보여주는 증거가 늘어가고 있습니다.

Back to Perspectives

DevOps as Overarching Process
A Pivotal Perspective by Michael Coté, Director, Marketing at Pivotal Software, Inc.

Large organizations in the thick of improving how they do software refer to their journeys in many ways: digital transformation, putting a cloud strategy in place, DevOps, or as Pivotal typically puts it, “cloud-native.”

The Origins of DevOps

Sometime in the mid-2000s, consumer-centric websites were battling for “eyeballs” and loyalty. To grab user attention, companies had to compete by constantly pushing out new features.

Yet deploying new changes to production frequently—weekly, if not daily!—carried the risk of exposing previously hidden bugs that hadn't had enough time to be found and fixed in development, negatively dinging uptime. Worse, changes in software might not work well with other services not under IT’s control. The fear was that nothing would work. DevOps launched as a way to solve the paradox of deploying frequently to production to stay competitive while reducing the risk of production failure and damage to the business.

The theory (which has proven to be successful) was that if you could get developers to be more aware of operational concerns and operators to be more involved in the development process, the software might stay up longer and the business could survive to compete another day.

Key DevOps Principles and Practices

One of the first principles to emerge was putting both roles—developers (Dev) and operators (Ops)—on the same team and giving everyone on that team responsibility for keeping the software up. This gave rise to the lore of developers carrying pagers. As this happened, developers started writing their software much differently to avoid being woken up late at night, while operations staff started adding in more automation and process standardization. The two groups started actually working together instead of battling each other. New practices, processes, and culture (much of it borrowed from agile and lean software development) were soon joined to the body of thought that became known as DevOps.

A helpful selection of the core practices—leading to high-performing organizations—is represented in the following charts as described in the DevOps Reports:

The Value of DevOps

High-performing organizations prioritize enabling small batch feature deployment because it keeps them competitive. In an era of transient advantage, custom-written software is a major enabler of innovation. However to be successful, businesses must focus IT on user interaction improvement and ensuring the software always works. Both of these, of course, are the goals of DevOps.

More from Coté about DevOps

Read the eBook: Crafting Your Cloud-Native Strategy
Listen to presentations: DevOps for Normals, Not Actually a DevOps Talk
Check out: recent blog posts

Back to Perspectives