DevOps and methodologies 1 introduction

DevOps and methodologies
1

INTRODUCTION
DevOps is a set of cultural concepts, practices, and technologies that improves an organization's capacity to produce high-velocity applications and services, allowing it to evolve and improve products at a faster rate than traditional software development and infrastructure management methods. This speed allows businesses to better service their clients and compete in the marketplace.
DevOps is the combination of people, process, and technology to continuously give value to consumers. It is a compound of development(Dev) and operations(Ops).
What does DevOps imply for organizations? DevOps allows previously compartmentalized disciplines like development, IT operations, quality engineering, and security to interact and coordinate to create better, more reliable products. Teams may better respond to customer requests, boost confidence in the apps they produce, and achieve business goals faster by adopting a DevOps culture and using DevOps principles and technologies.


2
DevOps History
The DevOps development begun to coalesce a few time between 2007 and 2008, when IT operations and computer program advancement communities raised concerns what they felt was a lethal level of brokenness within the industry. They railed against the conventional computer program improvement demonstrate, which called for those who compose code to be organizationally and practically separated from those who send and back that code. Developers and IT/Ops experts had isolated (and frequently competing) destinations, isolated office authority, partitioned key execution markers by which they were judged, and frequently worked on partitioned floors or indeed partitioned buildings. The result was siloed groups concerned as it were with their claim fiefdoms, long hours, botched discharges, and unhappy customers. Surely there’s distant better;a much better;a higher;a stronger;an improved a distant better way, they said. So, the two communities came together and begun talking – with individuals like Patrick Dubois, Quality Kim, and John Willis driving the discussion.
Numerous DevOps strategies for streamlining computer program improvement and sending have an early premise in spry computer program advancement and incline programming. But DevOps initially advanced from a few grassroots developments to harmonize the exercises of designers and their operations group counterparts. The early 2000s saw the ought to keep up accessibility of well known websites such as Google and Flickr against enormous hits. This require driven to the utilize of program unwavering quality engineers (SREs)—operations individuals working closely with engineers to guarantee that the locales would keep running after code was discharged into production. In 2009, Flickr engineers John Allspaw and Paul Hammond displayed their claim DevOps-like technique at a conference. Their introduction was entitled “10+ Conveys per Day: Dev and Ops Cooperation at Flickr.” The same year, Patrick Debois organized the primary “DevOps Day” in Belgium. A #DevOps hashtag was too consolidated and picked up force as more DevOps Days were held worldwide.
Numerous DevOps strategies for streamlining 

3
computer program improveme nt and sending have an