CHAPTER 1 Challenges in Adopting DevOps

DevOps practices like Continuous Delivery are being followed by some digital banking startups and other disruptive online fintech platforms, leveraging cloud services to get up and running quickly without spending too much up front on technology, and to take advantage of elastic on-demand computing capacity as they grow. But what about global investment banks, or a central securities depository or a stock exchange—large enterprises that have massiveinvestments in legacy technology?

采用DevOps时的挑战

像持续交付这样的DevOps实践被一些数字银行初创企业和其他颠覆性在线金融科技平台所推崇。它们利用云服务快速启动和运行，不会在技术上花费太多，并利用其计算能力按需弹性增长的优势。但全球投资银行、中央证券存管机构或证券交易所等对传统技术有着巨大投资的大型企业该怎么办呢？

Is DevOps Ready for the Enterprise?

So far, enterprise success for DevOps has been mostly modest and predictable: Continuous Delivery in consumer-facing web apps or greenfield mobile projects; moving data storage and analytics and general office functions into the cloud; and Agile programs to introduce automated testing and Continuous Integration, branded as DevOps to sound more hip.

DevOps是否为企业做好了准备？

到目前为止，DevOps的企业成功主要是温和的，而且可预测：面向消费者的Web应用程序或绿地(greenfield,指新建，译者注)的移动端项目；将数据存储和分析以及通用办公功能迁移至云端；在开发过程引入敏捷、自动化测试和持续集成。将上述过程打造成DevOps品牌，让其听起来更时髦。

In her May 2014 Wall Street Journal article “DevOps is Great for
Startups, but for Enterprises It Won’t Work—Yet”, Rachel Shannon-
Solomon outlines some of the major challenges that enterprises
need to overcome in adopting DevOps:
Rachel Shannon-Solomon 在她2014年5月的文章“DevOps对初创企业来说非常棒，但对大型企业来说，它还不起作用”（DevOps is Great for Startups, but for Enterprises It Won’t Work—Yet）一文中，概括了大型企业在引入DevOps时需要克服的一些主要挑战：
1. Siloed structures and organizational inertia make the kinds of
change that DevOps demands difficult and expensive.
2. Most of the popular DevOps toolkits are great if you have a web
system based on a LAMP stack, or if you need to solve specific automation problems. But these tools aren’t always enough if you have thousands of systems on different architectures and legacy technology platforms, and want to standardize on common enterprise tools and practices.
1 See http://on.mktw.net/1MdiuaF.
1。筒仓式组织结构和组织惯性使得DevOps需要的变革既困难又昂贵。
2。如果您的web应用基于LAMP技术栈，或者需要解决特定的自动化问题，那么大多数流行的DevOps工具包都是很好的。但如果您在不同的体系结构和遗留技术平台上拥有数千个系统，并希望在公共企业工具和实践上实现标准化的话，这些工具包并不总是足够的。
1 请参阅http://on.mktw.net/1mdiuaf。
3. Building the financial ROI case for a technology-driven business
process transformation that needs to cross organizational
silos doesn’t seem easy—although, as we’ll see by the end of this
book, the ROI for DevOps should become clear to all of the
stakeholders once they understand how DevOps works.
3. 为技术驱动的，特别是跨组织仓筒的业务流程转型构建财务投资回报率(ROI)案例看起来并不容易。不过，我们将在本书结尾处看到书中，DevOps的投资回报率应该对所有利益相关者来说是非常明确的，一旦他们了解了DevOps的工作原理的话。
4. Many people believe that DevOps requires a cultural revolution.
Large-scale cultural change is especially difficult to achieve in
enterprises. Where does the revolution start? In development,
or in operations, or in the business lines? Who will sponsor it?
Who will be the winners—and the losers?

许多人认为，DevOps需要一场文化革命。大规模的文化变革在大企业中尤其难以实现。革命从哪里开始？在开发部门，在运营部门，还是在业务部门？谁来支持它？谁将是赢家和输家？

These objections are valid, but they’re less convincing when you recognize

that DevOps organizations like Google and Amazon are enterprises in their own right, and when you see the success that some other organizations are beginning to have with DevOps at the enterprise level. They’ve already proven that DevOps can succeed at scale, if the management will and vision, and the engineering talent and discipline, are there.
这些反对意见是有效的，但当你意识到像谷歌和亚马逊这样的DevOps组织凭借自身能力成为大型企业时，这些反对意见就不那么具备说服力了，尤其是看到其他一些组织开始在企业级实施DevOps。他们已经证明了DevOps可以大规模取得成功，如果具备了管理层的愿意和愿景，以及工程人才还有纪律。
A shortage of engineering talent is a serious blocker for many organizations trying to implement DevOps. But this isn’t as much of a concern for the financial industry, which spends as much on IT talent as Silicon Valley, and competes directly with Internet technology companies for the best and the brightest. And adopting DevOps creates a virtuous circle in hiring: giving engineering and delivery teams more freedom and accountability, and a greater chance to learn and succeed, attracts more and better talent.1
工程人才短缺是许多试图实现DevOps的组织所面临的严重阻碍。但这对金融行业来说并不是一个很大的问题。它在IT人才上投入上与硅谷相当，并直接与互联网技术公司竞争最优秀和最聪明的人才。采用DevOps在招聘中创造了一个良性循环：提供工程和交付团队有更多的自由和责任感，有更大的机会学习和成功，并由此吸引更多更好的人才。1

So what is holding DevOps adoption back in the financial markets? Let’s look at other challenges that financial firms have to overcome:
1. The high risks and costs of failure in financial systems
2. Chaining interdependencies between systems, making changes
difficult to test and expensive (and high risk) to roll out
3. The weight of legacy technology and legacy controls
4. Perceived regulatory compliance roadblocks
5. Security risks and threats, and the fear that DevOps will make
IT less secure
Let’s look at each of these challenges in more detail.
那么，是什么阻碍了在金融市场的采用DevOps呢？让我们看看金融公司必须克服的其他挑战：
1、金融系统的高风险和失败成本
2、系统之间的链式相互依赖，让变更难以被测试，推出成本高（风险高）
3、大量的遗留技术和传统控制
4、公认的监管合规性障碍
5、安全风险和威胁，以及DevOps将使得IT不太安全的恐惧
让我们更详细地来看看这些挑战。