DevOps.com

  • Latest
    • Articles
    • Features
    • Most Read
    • News
    • News Releases
  • Topics
    • AI
    • Continuous Delivery
    • Continuous Testing
    • Cloud
    • Culture
    • DataOps
    • DevSecOps
    • Enterprise DevOps
    • Leadership Suite
    • DevOps Practice
    • ROELBOB
    • DevOps Toolbox
    • IT as Code
  • Videos/Podcasts
    • Techstrong.tv Podcast
    • Techstrong.tv - Twitch
    • DevOps Unbound
  • Webinars
    • Upcoming
    • On-Demand Webinars
  • Library
  • Events
    • Upcoming Events
    • On-Demand Events
  • Sponsored Content
  • Related Sites
    • Techstrong Group
    • Container Journal
    • Security Boulevard
    • Techstrong Research
    • DevOps Chat
    • DevOps Dozen
    • DevOps TV
    • Techstrong TV
    • Techstrong.tv Podcast
    • Techstrong.tv - Twitch
  • Media Kit
  • About
  • Sponsor
  • AI
  • Cloud
  • Continuous Delivery
  • Continuous Testing
  • DataOps
  • DevSecOps
  • DevOps Onramp
  • Platform Engineering
  • Low-Code/No-Code
  • IT as Code
  • More
    • Application Performance Management/Monitoring
    • Culture
    • Enterprise DevOps
    • ROELBOB
Hot Topics
  • AWS Delivers on Latest Graviton3 Price/Performance Promise
  • Five Tips for Moving IT Ops to DevOps
  • Before ChatGPT, AIOps Powered Enterprises for Years
  • Five Great DevOps Job Opportunities
  • Report Identifies Top 10 Open Source Software Risks

Home » Blogs » DevOps Practice » Back to Basics

Back to Basics

Avatar photoBy: Don Macvittie on February 15, 2023 Leave a Comment

We here at DevOps.com do sometimes suffer from The Curse of Knowledge. We write about DevOps regularly for an audience that is doing or managing DevOps. We assume knowledge, but there are still a fair number of people and organizations who are unclear about some of the terminology/technology that we talk about.

So if you are a regular reader of my blog, this might be a redundant post—but read on because it might have info you haven’t had a reason to consider yet.

TechStrong Con 2023Sponsorships Available

I’m going to start with the obvious—how most readers got here to begin with: DevOps. DevOps is automating the build process so that builds are automated and repeatable. Teamed with Agile development, DevOps means that development teams can rapidly iterate through development and generate regular updates to their applications. Everything else in this blog is based on the premise that it is running in a DevOps environment.

Continuous integration: Typified by Jenkins, continuous integration (CI) is the part of DevOps that runs the automated builds. It includes reporting and defect resolution only in the sense that it feeds into other systems that track defects. With CI in place, a developer or DevOps engineer can say, “Okay, ready to test a build,” and with one command, can kick off a build that will result in a finished artifact. Or result in a built product, anyway. ‘Finished’ is optional, and the target of CI is not generally a running application.

Continuous delivery: One of the most confusing things for new DevOps people is CD. The way that the space evolved, there are actually two things that CD could stand for; continuous delivery–automated build of the complete application —or continuous deployment—delivery of a running application onto infrastructure. Continuous delivery is straightforward and means all the bits of the application are code complete–or at least the current state of the application is complete enough to build an application. Continuous deployment is much more convoluted. It might mean deployed to a development environment for developer-level testing or a test environment for running automated (continuous testing) tests on or in production. It might be a staged rollout, where users are siphoned over, or it might be a hard rollout where the old version is replaced by the new in a manner similar to ripping a Band-Aid off.

Continuous test: Automated testing is at the heart of continuous test (CT), and it is only now becoming a real possibility for most short-staffed enterprises. Advancements in machine learning (ML) mean that tests can be run, results filtered to eliminate false or duplicate results, and IT staff is only notified of the important bits. Unlike traditional testing, staff is required only to create the tests and to look at meaningful results.

Infrastructure-as-Code: Infrastructure-as-Code (IaC) is the ability to define all relevant elements of infrastructure with text files. Often this is done in YAML and sometimes in a variety of other formats. The idea is that infrastructure provisioning can be on-demand and adaptable. It is certainly more agile to change a text file from port 80 to 8080 and then run a command to process the text file–now the port is documented and whenever needed the command can be re-run to move to a known state. IaC largely relies upon software implementations over physical. While the idea of software-defined networking (SDN) has fallen out of favor, the underlying principles are everywhere and part of IaC, for example.

GitOps: All the rage these days, GitOps is probably best defined as applying DevOps to operations. That does sound weird, but I like to break it up as “traditional DevOps is DevOps, while IaC (to a lesser extent) and GitOps (to a huge extent) are DevOps.” The point being that GitOps uses the text files generated in IaC and worker nodes generally designed for continuous deployment and then performs operations tasks based on those text files. If IaC defines the entire environment that an application needs and DevOps defines all of the sources that an application is composed of, bundling the two together will enable full-on automation from conception to decommissioning. When a new version of a source file or configuration file is checked into Git, the system then makes certain that every instance of the application is updated with the new version. Of course, this process, like every one listed here, is far more complex than that in implementation; we are talking about ‘what, not how’ at this level.

All of this really is the very tip of the iceberg, but that was the goal here – to offer readers a place to start if they’re finding themselves looking at DevOps for the first time. As you dig deeper, things like DevSecOps and test driven development (TDD), or defect tracking and Agile methodologies start to play into the landscape, and maybe I’ll write an intro bit for those also. But this time, we’re out of space.

As always, keep rocking it. No matter which or how much of the above you are using, if the organization’s applications are up and running, that’s you. And you deserve more kudos than you are likely getting. But keep grinding through—the rest of us get it, and thank you.

Image source: Photo by Towfiqu barbhuiya on Unsplash

Recent Posts By Don Macvittie
  • In DevOps, Chatbots are a People Problem
  • Managing Risk
  • We Are Living in an Ephemeral World
Avatar photo More from Don Macvittie
Related Posts
  • Back to Basics
  • Are You Ready for Your DevOps Transformation?
  • What is a DevOps ‘Best Practice’?
    Related Categories
  • Blogs
  • DevOps 101
  • DevOps Onramp
  • DevOps Practice
    Related Topics
  • agile
  • continous deployment
  • continuous delivery
  • continuous integration
  • Continuous Test
  • gitops
  • IaC
  • infrastructure
  • introduction
Show more
Show less

Filed Under: Blogs, DevOps 101, DevOps Onramp, DevOps Practice Tagged With: agile, continous deployment, continuous delivery, continuous integration, Continuous Test, gitops, IaC, infrastructure, introduction

« Organizations Prioritizing Java Application Modernization
Watching the Watchers: Solving the Problem of Meta-Permissions »

Techstrong TV – Live

Click full-screen to enable volume control
Watch latest episodes and shows

Upcoming Webinars

Best Practices for Monitoring AWS
Tuesday, March 7, 2023 - 1:00 pm EST
Getting Kubernetes Costs Under Control
Wednesday, March 8, 2023 - 1:00 pm EST
Terraform Cloud Workshop: Security Beyond Static Misconfiguration Checking
Thursday, March 9, 2023 - 11:00 am EST

Sponsored Content

The Google Cloud DevOps Awards: Apply Now!

January 10, 2023 | Brenna Washington

Codenotary Extends Dynamic SBOM Reach to Serverless Computing Platforms

December 9, 2022 | Mike Vizard

Why a Low-Code Platform Should Have Pro-Code Capabilities

March 24, 2021 | Andrew Manby

AWS Well-Architected Framework Elevates Agility

December 17, 2020 | JT Giri

Practical Approaches to Long-Term Cloud-Native Security

December 5, 2019 | Chris Tozzi

Latest from DevOps.com

AWS Delivers on Latest Graviton3 Price/Performance Promise
March 6, 2023 | Mike Vizard
Five Tips for Moving IT Ops to DevOps
March 6, 2023 | Itzik Reich
Before ChatGPT, AIOps Powered Enterprises for Years
March 6, 2023 | Thomas LaRock
Five Great DevOps Job Opportunities
March 6, 2023 | Mike Vizard
Report Identifies Top 10 Open Source Software Risks
March 6, 2023 | Mike Vizard

TSTV Podcast

On-Demand Webinars

DevOps.com Webinar ReplaysDevOps.com Webinar Replays

GET THE TOP STORIES OF THE WEEK

Most Read on DevOps.com

The Economic Downturn and DevOps Hiring Trends
February 28, 2023 | Mike Vizard
LinkedIn Job Scams: Out of Hand ¦ 4-Day Workweek: Let’s Get Serious
March 2, 2023 | Richi Jennings
Day in the Life of a Chief Developer Experience Officer (CDXO)
February 28, 2023 | Bill Doerrfeld
How GitHub Actions Simplifies Your CI/CD Workflow
March 2, 2023 | Sirish Patel
Vercel Adds Observability Tools to Web Application Framework
February 28, 2023 | Mike Vizard
  • Home
  • About DevOps.com
  • Meet our Authors
  • Write for DevOps.com
  • Media Kit
  • Sponsor Info
  • Copyright
  • TOS
  • Privacy Policy

Powered by Techstrong Group, Inc.

© 2023 ·Techstrong Group, Inc.All rights reserved.