Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

How DevOps Accelerates ''Ideas to Prod'' at Google

DZone's Guide to

How DevOps Accelerates ''Ideas to Prod'' at Google

Powerful learning comes from letting go of your preconceptions. See what else we learned from the keynote at JFrog's swampUP! user conference.

· DevOps Zone ·
Free Resource

Monitor your CI/CD pipelines end-to-end with Hygieia, an open source dashboard from Capital One.

Great keynote by Melody Meckfessel, Vice President of Engineering and Sam Ramji, VP Product Management for Google Cloud Platform during JFrog's swampUP! user conference.

Melody manages more than 1,000 developers at Google and Alphabet. DevOps matters to her because she wants happy and productive people on her team.

She has insight and empathy to the challenges that exist in DevOps. She also understands the benefits of bringing ideas to market faster = concepts, business, development, operation, market (money). Agile solves business and development collaboration problems. DevOps solves development and operations collaboration problems.

The evolution and future of DevOps:

  • In 2010, it was all about developers, developer tools, and app platforms.

  • In 2015, it was about developers and operators, and DevOps tools.

  • In 2020, it will be about developers and operators, DevOps AI, PaaS, IaaS, and physical resources.

Organizations are adopting DevOps – even it if didn’t work, CIOs need to talk to their CEOs about it because CEOs are reading about the benefits at other organizations.

Companies will begin making the transition to software teams with developers, tools, operators. Top performing teams will get to pick their own tools.

IT must invest in observability and value-added insight beyond the scope of any one team without an operation tool proliferating in parallel. Teams become the basis of decisions, organization, and restructuring.

There are new rules for leadership – today’s most impactful technology strategies are built on openness, abundance, and empowerment

You empower developers and operators by giving them an API.

A day in the life of a Google developer: 1) Write a patch against a component with many dependencies; 2) Test against the entire Google codebase; Pass!; 3) Send for review. LGTM! Happy developer. Faster and more productive

Developers want an amazing dev stack: 1) A comprehensive set of integrated tools; 2) Access to high-quality libraries; 3) Minimal DevOps overhead.

Operators want a stable and reliable prod stack, consistency in the environment.

Google developer scale:

  • 9 million source files

  • 30,000 developers at Google using server-side tools

  • 60,000 commits per day

  • 4 million builds per day

  • 2 billion lines of code per day

  • 500 million test cases per day

  • 20,000 code reviews per workday

  • 2 PB output per day

What is developing the Google way? 1) readability; 2) transparency; 3) automation of the build and test stack for devs and ops

  • Readability = code reviews for everyone; style guides, formatters, linters, fixes; source indexing, cross-referencing.
  • Automation = rely on test automation, not QA; hermetic, deterministic builds, fast build/test.
  • Transparency = everyone sees everything, heavily reused common libraries, large-scale changes, refactoring.

DevOps for the world = ship as often as possible, don’t break anything. Living the DevOps principles enable engineering teams to frequently release new features and services safely.

  • Massively automate the execution of unit, integration, end-to-end tests, releasing with integrated monitoring and alerting capabilities.

  • Have the culture and environment to release rapidly and more reliably.

Culture in action: data guides us, collaboration and shared fate, transparency, blameless post-mortem culture. We don’t blame the people blame the process. We are hardened to solve for all the edge cases.

The tooling you're sitting on and the culture you are in impacts your life. Do you have the automation and the tools to keep in a mental state of flow? It takes 45 minutes to get there and then you want to be able to write code for two to three hours at a very high level of mental function.

Powerful learning comes from letting go. Surrender to try new things. Don’t ask how does this fit into what I already know. Give yourself a couple of months to accept the patterns, tools, food and then you can start to assess and evaluate.

There is no way to interpret the data so that you should be doing anything other than DevOps. Stop worrying and learn to love DevOps you’ll be more valuable and happier in a state of flow.

Track and monitor your entire CI/CD pipeline on a single pane of glass. Hygieia is an open source, visual dashboard for keeping CI/CD pipelines green.

Topics:
devops ,jfrog ,production

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}