DevOps: From Silos to Superpowers - How Modern Practices are Revolutionizing Development

Hey everyone! As a fellow developer just starting to navigate the exciting world of DevOps, I've been diving headfirst into everything I can find to up my game. Fear not, because there's a whole new world of modern DevOps techniques out there, and I'm here to share my discoveries (and hopefully learn from yours too!)

Right now, I'm neck-deep in a fantastic book on Modern DevOps Techniques by Gaurav Agarwal, and I'm eager to dissect what I'm learning and explore how we can all leverage these modern practices to streamline our workflows and achieve DevOps nirvana! So, grab a cup of coffee (or chai, if you're like me!), settle in, and let's embark on this journey together!

I will keep posting my learnings on regular basis so that we can learn new things as I am in very much beginning stage of my career in Information technology field!!.

What is DevOps?

Well, You will be thinking, one more old boring definition. To be honest, I was thinking like that when I found various definitions for DevOps. Every person, Every organization has their own perspective and their own way of defining the DevOps. Some would heavily rely on tools and will present the focus on tools based outcome. Some would say it is a culture ! it is a mindset which the organization has to develop to be the best in the cutting-edge technologically advanced world!

Let us start with a proper context and definition and will understand in a beginner friendly approach so that you and I, we both can understand better.

DevOps bridges the gap between development and operations by promoting a culture of collaboration, shared responsibilities, and continuous feedback using automation throughout the software development life cycle.

Now it seems that it is just mixed up jargon of fancy technological words. Let us understand the above definition with a fascinating example. Well, I am Gujarati Indian person and I am a foodie as well, so we will understand with very simple example in layman terms😊.

Imagine I'm helping my Nani (grandmother) make her famous Thepla (Gujarati flatbread). Traditionally, there might be a bit of a divide:

Nani (Development): Nani has the secret recipe and knows exactly how to mix the dough, roll it out perfectly thin, and even add the right amount of spice. But once the Theplas are cooked, her job is done.
Me (Operations): I'm responsible for getting the Theplas piping hot to the table. I may heat up the tava (griddle), manage the flame, and ensure they don't burn.

This can sometimes lead to issues. Maybe Nani makes too many Theplas, and I end up scrambling to keep up with heating them all. Or perhaps, I accidentally burn a few because Nani forgot to mention the perfect heat level.

DevOps bridges this gap! It's like having a family meeting before making Theplas. Here's how:

Collaboration: I and Nani discuss how many Theplas everyone wants. Maybe I even write it down on a piece of paper (like a shared project plan). This way, Nani knows how much dough to prepare, and I know how many Theplas to manage on the tava.
Shared Responsibilities: Nani might show me her dough-making technique, and I can share some tips on managing the heat for perfect browning. Everyone contributes their expertise for a better outcome.
Continuous Feedback: As Nani rolls out the Theplas, I can give feedback on the thickness. Maybe they're a bit too thick – no problem! Nani adjusts her rolling technique for the next one. This continuous feedback ensures every Thepla comes out perfect.
Automation: Remember that old pressure cooker Nani uses to make perfect dal (lentils)? That's a form of automation! It ensures the dal cooks evenly without needing constant attention. Similarly, DevOps uses tools to automate repetitive tasks, like testing the code or deploying the software, freeing up time for more creative problem-solving.

By working together, sharing responsibilities, and constantly learning from each other, me and Nani can create a smooth Thepla-making process that's efficient and enjoyable for everyone. That's the essence of DevOps in the world of software development!

A DevOps team should ensure that instead of having a clear set of siloed groups that do development, operations, and QA, they have a single team that takes care of the entire SDLC life cycle – that is, the team will build, deploy, and monitor the software.

I hope you understood the concept and you may go to your Nani and tell her to prepare your favorite food and enjoy the process!😁

Modern Approach V/S Traditional Approach

Traditional Approach

DevOps’ traditional approach involved establishing a DevOps team consisting of Dev, QA, and Ops members and working toward creating better software faster. However, while there would be a focus on automating software delivery, automation tools were installed and maintained manually.

This led to another problem as organizations now had to manage another set of IT infrastructure. It finally boiled down to infrastructure and configuration, and the focus was to automate the automation process.

You will think, One more technical mixed jargon terminology, so let us make it simple by considering a simple example of this scorching summer season!

Imagine it's the peak of summer in your city. The heat is scorching, and everyone wants some relief – that's what good software should be like, delivered quickly and efficiently to solve problems.

Traditionally, companies trying to achieve this were like a family trying to beat the heat:

Dev (The Cooks): Mom (the developer) is in the kitchen whipping up delicious mango shrikhand, a cool summer treat. She knows the recipe by heart and can churn it out quickly.
QA (The Testers): Dad (the QA tester) is tasked with checking the shrikhand's quality. He tastes each batch to ensure it's perfectly sweet and creamy.
Ops (The Servers): You (representing operations) are responsible for getting the shrikhand to everyone. You run around with bowls, making sure everyone gets a cool treat.

Here's where things get tricky:

Manual Automation: While everyone wants the shrikhand fast, setting up fans (automation tools) to cool things down is a manual process. Dad might have to climb on a chair and adjust the fan every time a new batch comes out. It's time-consuming and not very efficient.
Limited Collaboration: There might not be a lot of communication between Mom and you. Maybe she accidentally makes a giant batch, and you're left scrambling to serve it all before it melts.

This traditional approach, just like the manual fan setup, can lead to bottlenecks and inefficiencies.

Modern Approach

With the recent boom in the public cloud landscape, DevOps’ modern approach came into the picture, which involved automating everything. From provisioning infrastructure to configuring tools and processes, there is code for everything.

Let us continue the simple example of Mango shrikhand for understanding the concept.

Imagine your family decided to invest in a smart home system for the next summer:

Infrastructure as Code (The Smart AC): Instead of manual fans, you now have a smart AC unit. Just like infrastructure as code, it's essentially a set of instructions written in code that automatically configures the ideal cooling temperature for the entire house. No more climbing chairs or adjusting settings – it's all automated!
Configuration as Code (The Smart Thermostat): Remember Dad constantly checking the shrikhand quality? Configuration as code acts like a smart thermostat. It defines the ideal settings for making the perfect shrikhand every time, automatically adjusting sugar levels or churning speed based on pre-defined parameters.
Immutable Infrastructure (The Pre-Measured Ingredients): Mom is now using pre-measured ingredient packets for the shrikhand. This ensures consistency and eliminates the risk of accidentally making a giant batch. Similarly, with immutable infrastructure, every new server deployment starts with a fresh, pre-configured "recipe" to avoid inconsistencies and errors.

Benefits of Modern DevOps (The Cool Summer Breeze):

Faster Delivery: Just like the smart AC cools the house quickly, modern DevOps automates tasks, leading to faster software delivery and deployment.
Reduced Errors: Pre-configured settings and automated processes minimize human error, ensuring consistent and reliable software.
Scalability: The smart home system can adjust cooling based on the number of people in the house. Similarly, modern DevOps allows for easy scaling of infrastructure resources to meet changing demands.
Less Maintenance: You no longer need to constantly adjust the fans – the smart AC takes care of it. Modern DevOps automates maintenance tasks, freeing up time for developers and operations teams to focus on innovation.

In essence, modern DevOps is like having a well-oiled machine for software development. Everything is automated, configured, and works together seamlessly, just like your smart home system keeping you cool during the hottest summer days!

I hope you have understood both the approaches in DevOps. Now Let us discuss how the modern approaches affected the Software Development and Deployment eco-system with interesting example.

Modern DevOps Techniques - A New Horizon!

The modern DevOps approach generally focuses on leveraging cloud technologies, automation, containerization and other principles to enhance collaboration, agility, and software development and deployment efficiency.

Let us understand it by very recent and interesting example. Currently, in the summer, more than 70% Indians spend their evenings by watching the IPL and there is always a mandatory post on LinkedIn about the handling of live streaming of cricket matches😁.

Imagine the thrill of the IPL season! Millions of fans tune in to Jio Cinema to catch every ball, every boundary, and every wicket. To handle this massive surge in viewership, these streaming platforms rely heavily on modern DevOps practices. Let's see how:

The Challenge: Scaling Up for the Big Game

Think of the traditional approach as a single-server stadium. It might handle a regular season crowd, but during the IPL, it would be overwhelmed. Modern DevOps is like a modern, expandable stadium:

Cloud Technologies: Instead of a single server, Jio Cinema utilizes the cloud (think of it as renting space in a massive stadium complex). This allows them to easily scale up resources (servers) during the IPL to handle the spike in viewers. Imagine additional stands appearing out of thin air to accommodate the IPL crowd!
Automation: Adding and configuring these servers wouldn't be practical manually. That's where automation comes in. DevOps uses tools to automate tasks like server provisioning and configuration. Think of these tools as pre-programmed robots that can quickly set up additional servers like building pre-fabricated sections of the stadium.
Containerization: Even with automation, managing individual servers can be complex. Modern DevOps uses containerization. Imagine each server being a shipping container pre-loaded with all the software needed for the streaming service. These containers can be easily deployed and scaled independently, making it even faster to adjust resources during the IPL. Think of each container as a pre-assembled concession stand, ready to serve refreshments to the IPL audience!

The Benefits: A Seamless Viewing Experience

These modern DevOps practices lead to several advantages for both Jio Cinema and viewers:

Enhanced Collaboration: DevOps fosters communication between developers, operations, and security teams. This ensures everyone is on the same page, working together to deliver a smooth streaming experience. Imagine clear communication between stadium staff - security, maintenance, and vendors - ensuring a smooth experience for fans.
Increased Agility: Modern DevOps allows for faster changes and deployments. If a bug is identified during the IPL, the team can quickly fix and deploy the update without significant downtime. This agility is like the stadium staff quickly responding to any issue, like a toilet overflowing or a power outage, minimizing disruption for the fans.
Improved Efficiency: Automation and containerization free up valuable time and resources. Developers can focus on innovation, while operations teams can manage the infrastructure more effectively. This efficiency translates to a more cost-effective streaming service and potentially lower subscription fees for viewers. Imagine the stadium staff working efficiently, reducing costs and keeping ticket prices affordable for fans.

So, there you have it! Modern DevOps is like the secret sauce that keeps your favorite IPL streaming app running smoothly, even when millions of cricket fanatics are glued to their screens. It's the automation superhero that swoops in to save the day, the communication champion that keeps everyone on the same page, and the efficiency expert that ensures a win-win for both the streaming service and cricket lovers.

Stay tuned for more posts like this as I have just begun the journey of exploration!

Now, if you'll excuse me, I have some important research to do – figuring out the most efficient way to deliver endless cups of chai during the next IPL season. Wish me luck !

The Accidental Techie signs off!!!!