ThoughtWorks
  • 联系我们
  • Español
  • Português
  • Deutsch
  • English
概况
  • 工匠精神和科技思维

    采用现代的软件开发方法,更快地交付价值

    智能驱动的决策机制

    利用数据资产解锁新价值来源

  • 低摩擦的运营模式

    提升组织的变革响应力

    企业级平台战略

    创建与经营战略发展同步的灵活的技术平台

  • 客户洞察和数字化产品能力

    快速设计、交付及演进优质产品和卓越体验

    合作伙伴

    利用我们可靠的合作商网络来扩大我们为客户提供的成果

概况
  • 汽车企业
  • 清洁技术,能源与公用事业
  • 金融和保险企业
  • 医疗企业
  • 媒体和出版业
  • 非盈利性组织
  • 公共服务机构
  • 零售业和电商
  • 旅游业和运输业
概况

特色

  • 技术

    深入探索企业技术与卓越工程管理

  • 商业

    及时了解数字领导者的最新业务和行业见解

  • 文化

    分享职业发展心得,以及我们对社会公正和包容性的见解

数字出版物和工具

  • 技术雷达

    对前沿技术提供意见和指引

  • 视野

    服务数字读者的出版物

  • 数字化流畅度模型

    可以将应对不确定性所需的数字能力进行优先级划分的模型

  • 解码器

    业务主管的A-Z技术指南

所有洞见

  • 文章

    助力商业的专业洞见

  • 博客

    ThoughtWorks 全球员工的洞见及观点

  • 书籍

    浏览更多我们的书籍

  • 播客

    分析商业和技术最新趋势的精彩对话

概况
  • 申请流程

    面试准备

  • 毕业生和变换职业者

    正确开启技术生涯

  • 搜索工作

    在您所在的区域寻找正在招聘的岗位

  • 保持联系

    订阅我们的月度新闻简报

概况
  • 会议与活动
  • 多元与包容
  • 新闻
  • 开源
  • 领导层
  • 社会影响力
  • Español
  • Português
  • Deutsch
  • English
ThoughtWorks菜单
  • 关闭   ✕
  • 产品及服务
  • 合作伙伴
  • 洞见
  • 加入我们
  • 关于我们
  • 联系我们
  • 返回
  • 关闭   ✕
  • 概况
  • 工匠精神和科技思维

    采用现代的软件开发方法,更快地交付价值

  • 客户洞察和数字化产品能力

    快速设计、交付及演进优质产品和卓越体验

  • 低摩擦的运营模式

    提升组织的变革响应力

  • 智能驱动的决策机制

    利用数据资产解锁新价值来源

  • 合作伙伴

    利用我们可靠的合作商网络来扩大我们为客户提供的成果

  • 企业级平台战略

    创建与经营战略发展同步的灵活的技术平台

  • 返回
  • 关闭   ✕
  • 概况
  • 汽车企业
  • 清洁技术,能源与公用事业
  • 金融和保险企业
  • 医疗企业
  • 媒体和出版业
  • 非盈利性组织
  • 公共服务机构
  • 零售业和电商
  • 旅游业和运输业
  • 返回
  • 关闭   ✕
  • 概况
  • 特色

  • 技术

    深入探索企业技术与卓越工程管理

  • 商业

    及时了解数字领导者的最新业务和行业见解

  • 文化

    分享职业发展心得,以及我们对社会公正和包容性的见解

  • 数字出版物和工具

  • 技术雷达

    对前沿技术提供意见和指引

  • 视野

    服务数字读者的出版物

  • 数字化流畅度模型

    可以将应对不确定性所需的数字能力进行优先级划分的模型

  • 解码器

    业务主管的A-Z技术指南

  • 所有洞见

  • 文章

    助力商业的专业洞见

  • 博客

    ThoughtWorks 全球员工的洞见及观点

  • 书籍

    浏览更多我们的书籍

  • 播客

    分析商业和技术最新趋势的精彩对话

  • 返回
  • 关闭   ✕
  • 概况
  • 申请流程

    面试准备

  • 毕业生和变换职业者

    正确开启技术生涯

  • 搜索工作

    在您所在的区域寻找正在招聘的岗位

  • 保持联系

    订阅我们的月度新闻简报

  • 返回
  • 关闭   ✕
  • 概况
  • 会议与活动
  • 多元与包容
  • 新闻
  • 开源
  • 领导层
  • 社会影响力
博客
选择主题
查看所有话题关闭
技术 
敏捷项目管理 云 持续交付 数据科学与工程 捍卫网络自由 演进式架构 体验设计 物联网 语言、工具与框架 遗留资产现代化 Machine Learning & Artificial Intelligence 微服务 平台 安全 软件测试 技术策略 
商业 
金融服务 全球医疗 创新 零售行业 转型 
招聘 
职业心得 多元与融合 社会改变 
博客

话题

选择主题
  • 技术
    技术
  • 技术 概观
  • 敏捷项目管理
  • 云
  • 持续交付
  • 数据科学与工程
  • 捍卫网络自由
  • 演进式架构
  • 体验设计
  • 物联网
  • 语言、工具与框架
  • 遗留资产现代化
  • Machine Learning & Artificial Intelligence
  • 微服务
  • 平台
  • 安全
  • 软件测试
  • 技术策略
  • 商业
    商业
  • 商业 概观
  • 金融服务
  • 全球医疗
  • 创新
  • 零售行业
  • 转型
  • 招聘
    招聘
  • 招聘 概观
  • 职业心得
  • 多元与融合
  • 社会改变
持续交付职业心得技术招聘

Getting into DevOps: Part 2

Carlos Nuñez Carlos Nuñez

Published: May 8, 2017

In the first section of this two-part series, we looked briefly into the state of IT teams before the DevOps movement gained traction, and some skills that might be useful to those looking to get into infrastructure work. In this section, we will explore different variations of DevOps teams I’ve seen, as well as, their positives and advantages.

DevOps In Action

I have seen two common models of DevOps at work that have been effective at bridging the gap between development, operations and business outcomes. These aren’t set in stone and can vary in implementation from company to company. For more examples and a deeper discussion of DevOps anti-patterns, I highly recommend reading Matt Skelton’s blog post on DevOps team structures [1].

Trunk and Leaf

The trunk and lead model for software development.
In the trunk and leaf model, every development team has a small group of engineers, or leaves, that are partially or wholly dedicated to creating and maintaining the platform for their service or feature. These groups are members of a larger community of engineers, or trunks, that collaborate on setting standards, best practices and guidelines for the infrastructure and tooling for which they are responsible.

This model is similar to engineering organizations found at many well-known tech companies, including Spotify’s “chapters” [2] and Google’s SRE model as described by Beyer and Jones Site Reliability Engineering book. It is also ideal for teams that are looking to have closer and more dedicated working relationships with platform engineers or teams for other tech or business functions that do not fit the typical “development team” mold. Network (DevNetOps), security (DevSecOps) and business operations (DevBizOps) come to mind here.

Hub and Spoke

A hub and spoke model team within DevOps
I’ve also seen companies employ a single platform team, or a platform hub, that is responsible for maintaining the platform that powers the entire software stack of a company. Product teams consume well-defined infrastructure services from the platform team (and are therefore the spoke in this analogy).

While members of this team might provide advisory services to development teams on how to best design their software to work on their infrastructure, the onus of publishing changes to said infrastructure or tools used to interact with it, ultimately falls on the platform team.

This model is fairly common amongst small and large companies alike. This team goes by many different names, such as the “Platform”, “Production” or “Infrastructure” engineering teams. Others typically call this the “DevOps” or “SRE” team. Regardless of the name, they usually share a few common attributes:
  • Responsibility over scaling, architecture and maintenance of physical or virtual hardware on which the application sits, and,
  • Responsibility over tools and services used to deploy software onto this infrastructure.

In Closing

From companies deploying everything to bare metal (there are plenty that still do, for good reasons) to trail blazers doing everything serverless, the practices and ideas behind DevOps are here to stay. The skill and tool surface area is large, and the manifestations can vary depending on the company. Regardless, the work is interesting, the results are impactful, and, most importantly, it gets teams tearing down walls and working together to make businesses faster and more responsive.

It’s a wonderful thing to experience.

Theory Books

Which are the other books you can read about getting into DevOps

You might have heard of or read The Phoenix Project by Gene Kim. It covers much of the history I explained earlier (with much more color) and describes their journey to a lean company running on Agile and DevOps. It’s a great book.

Here are some others that are worth a read:
  • Driving Technical Change by Terrance Ryan. Awesome little book on common personalities within most technology organizations and how to deal with them. This helped me out more than I expected.
  • PeopleWare by Tom DeMarco and Tim Lister. A classic on managing engineering organizations. A bit dated, but still relevant.
  • Time Management for System Administrators by Tom Limoncelli from Stack Overflow. While this is heavily geared towards sysadmins, it provides great insight into the life of a systems administrator at most large organizations. If you want to learn more about the war between sysadmins and developers, this book might explain more.
  • The Lean Startup by Eric Ries. Describes how Eric’s 3D avatar company, IMVU, discovered how to work lean, fail fast and find profit faster. Lean Enterprise by Jez Humble and friends is an adaption of this book for the enterprise. Both are great reads and do a good job of explaining the business motivation behind DevOps.
  • Infrastructure As Code by our very own Kief Morris. Awesome primer on, well, infrastructure as code! Does a great job of describing why it’s essential for any business to adopt this for their infrastructure.
  • Site Reliability Engineering by Betsy Beyer, Chris Jones and others. A book explaining how Google does SRE, or also known as “DevOps before DevOps was a thing.” Provides interesting opinions on how to handle uptime, latency and keeping engineers happy.

Technical Books

If you’re looking for books that’ll take you straight to code, you’ve come to the right section.
  • TCP/IP Illustrated by the late W. Richard Stevens. This is the classic (and, arguably, complete) tome on the fundamental networking protocols, with special emphasis on TCP/IP. If you’ve heard of Layers 1, 2, 3 and 4 and are interested in learning more, you’ll need this book.
  • UNIX and Linux System Administration Handbook by Ben Whaley and Evi Nemeth. A great primer into how Linux and UNIX works and how to navigate around them.
  • Learn Windows Powershell In A Month of Lunches by Don Jones and Jeffrey Hicks. If you’re doing anything automated with Windows, you will need to learn how to use Powershell. This is the book that will help you do that. Don Jones is a well-known MVP in this space.
  • Practically anything by James Turnbull. He puts out great technical primers on popular DevOps-related tools.

References

[1] https://blog.matthewskelton.net/2013/10/22/what-team-structure-is-right-for-devops-to-flourish/
[2] http://www.full-stackagile.com/2016/02/14/team-organisation-squads-chapters-tribes-and-guilds/
[3] https://github.com/garystafford/voter-service
[4] https://github.com/maxamg/cd-office-hours

Ready to shape the future of tech?

Join our team of passionate and bright technologists.

Join us
相关博客
技术

Analysing the DevOps Silo

Abigail Bangser
了解更多
持续交付

Getting into DevOps: Part 1

Carlos Nuñez
了解更多
技术

Treat DevOps Stories like User Stories

Abigail Bangser
了解更多
  • 产品及服务
  • 合作伙伴
  • 洞见
  • 加入我们
  • 关于我们
  • 联系我们

WeChat

×
QR code to ThoughtWorks China WeChat subscription account

媒体与第三方机构垂询 | 政策声明 | Modern Slavery statement ThoughtWorks| 辅助功能 | © 2021 ThoughtWorks, Inc.