The latest articles on DEV Community by Babush (@selfbabush). https://dev.to/selfbabush https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F925135%2F9e7f3bd4-0de6-4da6-83da-44fa6eb5f0d0.jpeg https://dev.to/selfbabush en Babush Fri, 04 Nov 2022 06:17:51 +0000 https://dev.to/selfbabush/devops-2j4a https://dev.to/selfbabush/devops-2j4a <p>Once upon a time and also in the present, there lived/live two groups of people, <strong>developers</strong> and <strong>operators</strong> . </p> <p>Developers built and ship software/features. They focused on building and shipping new features as quickly as possible. <strong>Agility</strong> was the 'magic' word.</p> <p>Operators ran and oversaw the production systems. They focussed on having a stable, reliable and safe system . The main concern of the operators was <strong>Stability</strong> .</p> <p>The competing/conflicting interests of Developers and Operators caused friction and thus there was an element of impedance towards the goal of achieving speedy delivery of features whilst not compromising on the stability, reliability and safety of the system.</p> <p>In order to achieve the goal, some organizations started adopting/following certain practices that tried to address this concern and collectively they were termed as <strong>DevOps</strong></p> <p>DevOps, can be considered an organizational and cultural movement that aims to increase software delivery velocity, improve service reliability, and build shared ownership among software stakeholders.</p> <p>DevOps can be considered as consisting of 5 Principles or key areas of focus.</p> <p><strong>1) Reduce Organizational Silos</strong><br> This can be achieved by having the operators in the same room(physical or virtual) as the developers, facilitating conversation and collaboration in the daily stand-ups. The next step would be to involve the product and the sales team too.</p> <p><strong>2) Accept Failure as Normal</strong><br> Foster a culture wherein we accept that failure is normal and we actively plan for it.</p> <p><strong>3) Implement Gradual Change</strong><br> Adhere to methodologies that espouse small changes at regular intervals. Its easier to detect issues in small changes and either fix them or rollback.</p> <p><strong>4) Leveraging Tooling and Automation.</strong> <br> Tools such as Terraform which codify infrastructure and bring repeatability into the forefront allow automation.</p> <p><strong>5) Measure Everything</strong><br> Unless we measure, its difficult to reach consensus if we have reached our goals and achieved success . Hence to achieve business objectives its important to measure and identify the appropriate metrics. Measure, Monitor and setup Alerts</p> <p>DevOps is a bunch of abstract concepts. It says this is what we could do in order to achieve such and such a thing . But it is silent about the ways of going about achieving it. </p> <p>In the next <strong><a href="https://dev.tourl">post </a></strong>I would be talking about <strong>SRE</strong> which can be considered as a concrete implementation of DevOps principles</p> devops agile