Skip to main content

Command Palette

Search for a command to run...

🛠What is DevOps ?

Updated
4 min read
🛠What is DevOps ?
V

👩‍💻 Aspiring DevOps & Cloud Engineer | Learning in Public | Automation Enthusiast Hi! I’m Vaishnavi Landge, documenting my journey into DevOps, Cloud, CI/CD, and automation. I believe in learning by doing — this blog is my daily space to simplify concepts, share projects, and grow step by step. 🚀 Let’s build, automate, and deploy — together!

🚀 Welcome to Day 1 of “The CloudOps Journal” — my daily DevOps & Cloud learning journey! I’m Vaishnavi Landge, an aspiring DevOps Engineer, documenting everything I learn so others can follow along. In today’s article, let’s break down one of the most searched — yet misunderstood — questions: What exactly is DevOps?


📌 What is DevOps?

DevOps is a culture, practice, and set of tools that combines software development (Dev) and IT operations (Ops) to shorten the system development life cycle — while delivering high-quality software continuously.

But DevOps is not a tool or a single technology. It's a philosophy of collaboration, automation, and continuous improvement.


🔍 Why DevOps? (The “Before DevOps” Story)

Before DevOps came into the picture, the tech world had a serious problem: “The Wall of Confusion.”

🧱 Before DevOps:

  • Developers would write code and throw it over the wall to operations.

  • Operations would be responsible for deployment, stability, and uptime.

  • No feedback loop. Lots of blame. Slow releases. Tons of bugs.

This led to:

  • Delayed software delivery

  • Manual errors in deployments

  • Poor collaboration between dev & ops

  • "It works on my machine" syndrome

💡 Why DevOps Came Into Existence:

  • Companies needed to move fast and release often (think Amazon, Netflix).

  • Manual deployments weren’t scaling.

  • Collaboration was critical — not optional.

That’s where DevOps was born — to bridge the gap between Dev and Ops, and automate the pipeline from development to deployment.


🧠 Things to Know Before Getting Into DevOps

Before diving into tools like Docker or Kubernetes, it’s essential to understand the mindset and foundation of DevOps.

Here’s what you should get comfortable with:

AreaWhy It Matters
Basic Linux CommandsAlmost everything in DevOps runs on Linux
Networking ConceptsPorts, DNS, firewalls — crucial for deployments
Version Control (Git)CI/CD starts with source control
Programming Basics (Python/Shell)For scripting and automation
Cloud Basics (AWS/GCP/Azure)DevOps = Cloud-first approach
CI/CD ConceptsKnow what happens from push to production
Containers & VirtualizationUnderstand Docker before K8s

🔄 DevOps Lifecycle (The Real Flow)

Think of DevOps as a continuous loop where everything feeds into everything else. It’s not a start-to-end process — it’s a circle of improvement.

🌀 Key Phases in the DevOps Lifecycle:

  1. Plan – Gather requirements, plan features.

  2. Develop – Code using best practices.

  3. Build – Compile code into executable units.

  4. Test – Automate tests to catch bugs early.

  5. Release – Push code into staging/production.

  6. Deploy – Use tools like Jenkins, GitHub Actions, etc.

  7. Operate – Monitor system health, scale as needed.

  8. Monitor – Use logging and alerting tools for insights.

🔁 Then, go back to Plan based on feedback.

Tools involved (we’ll explore these later):

  • Git, Docker, Kubernetes

  • Jenkins, GitHub Actions, Terraform

  • Prometheus, Grafana, AWS, NGINX


👩‍💻 Roles & Responsibilities of a DevOps Engineer

As someone aspiring to become a DevOps Engineer, here’s what I’ve learned DevOps engineers actually do:

RoleDescription
CI/CD Pipeline CreatorAutomates the flow from code push to production
Infrastructure AutomatorUses tools like Terraform or Ansible
Cloud Architect (Lite)Knows how to deploy on AWS/GCP
Monitoring SpecialistUses tools to detect issues before users do
Security GatekeeperAdds security checks in pipelines
Collaboration ChampionWorks with developers, testers, ops, and cloud teams

DevOps isn’t a single job — it’s a mindset and a toolbox. You may not master it all in a week, but with daily practice (like this blog!), it’s totally doable.


✍️ My DevOps Learning Vision

As I begin this journey, I’m not just learning tools — I’m learning how to think like a DevOps Engineer. I’ll be writing daily about:

  • Real-world tools (Docker, AWS, Jenkins, Terraform)

  • Problems I face and how I solve them

  • Concepts I wish I understood earlier

If you're also starting out — let's grow together. 🌱


📢 Final Thoughts

DevOps isn’t just a buzzword — it’s a modern way of building software.

DevOps is no longer optional — it’s essential.

Stay tuned for Day 2: All about Linux.


✉️ Let’s Connect
If you’re learning DevOps like me or want to share your thoughts — feel free to comment, connect, or drop a question. Let’s build and grow together 💻✨

More from this blog

The CloudOps Journal

10 posts