FINAL WORD
What is DevOps ?
In the old world , delivering changes and new software into a production environment would involve developers working in their own siloed teams , who would then plan for software to be released via operations teams . This operation might involve handover processes and procedures and change boards .
The traditional model is that you take your software to the wall that separates development and operations , and throw it over and then forget about it . But at Amazon . You build it , you run it .
This brings developers into contact with the day-to-day operation of their software . It also brings them into day-to-day contact with the customer . This customer feedback loop is essential for improving the quality of the service .
DevOps is the ethos of breaking down the development and operations silos in order to create end-to-end processes that deliver software into production with minimal friction . As DevOps has evolved , an industry wide consensus has emerged for the practices that the ethos involves :
• Release small , fast and often
• Remove functional silos
• Automate and script processes that are painful
• Continuously monitor all changes deployed to production in order to gain feedback for new releases and fixes
• Favour immutable components , rather than patch and update components , replace them
• Component failure should be fast and when this happens the focus should be on fixing the root cause as expediently as possible
An organisation ’ s legacy storage infrastructure may create several pain points , causing it to work against you and not for you when it comes to process automation and orchestration .
Once the functional silos have been removed and development to production endto-end processes are in place , a number of software tool related capabilities can add tremendous value to an organisation embarking on its DevOps journey .
Excerpted from blog written by Christopher Adkin
Additionally , platform engineers handle data on Kubernetes , managing storage resources , backup , disaster recovery , databases and data services under the Kubernetes umbrella . We are witnessing the efficiencies firsthand , with a small number of platform engineers catering to hundreds of users .
When a technology becomes ubiquitous , it gradually fades into the background . Consider semiconductors as an example , they are present everywhere , powering our remote controls , phones , and cars . However , as end-users , we rarely consider their existence , they have become invisible . Kubernetes is experiencing a similar transformation .
In the enterprise realm , Kubernetes is becoming deeply ingrained in various systems , and the self-service paradigm makes it inconspicuous to users . In the past , every developer needed to possess comprehensive knowledge of Kubernetes . Now , developers only need to use it , leaving the intricacies to the platform engineer . Platform engineering will make Kubernetes invisible .
Platform engineering bestows a valuable gift upon developers by relieving them of the burden of comprehending Kubernetes at a granular level as part of their daily responsibilities . This eliminates a skills gap issue as Kubernetes continues to flourish , and is relied upon by all of the world ’ s largest and most successful organisations . Platform engineers and Kubernetes are a match made in heaven to aid a company ’ s innovation and competitive edge . •
76 www . intelligenttechchannels . com