DevOps Practice

From GM-RKB
(Redirected from DevOps Methodology)
Jump to navigation Jump to search

A DevOps Practice is a software development practice that can be used to create software development and operation systems (that support continuous software delivery tasks).

References

2024

  • Perplexity
    • Based on the search results provided, here are the organizations that have shared details about their internal DevOps practices:
      1. Atlassian - In the article [1], Atlassian mentions conducting a survey of 500 DevOps practitioners and finding that 50% of organizations have been practicing DevOps for more than three years. However, it does not provide specific details on the DevOps practices of particular companies.
      2. Stack Overflow - The blog post [2] from Stack Overflow discusses their internal DevOps mindset and practices like one-team thinking, automation to eliminate "hell months" during releases, and the need for standardization and eliminating variables. It provides some insights into Stack Overflow's approach to DevOps.
      3. TIAA-CREF - The article [4] cites TIAA-CREF as an example of an organization that has seen significant improvements by adopting an "agile-based DevOps approach", resulting in a four-fold increase in development productivity and faster release cycles. However, it does not delve into the specific DevOps practices implemented by TIAA-CREF.
    • The other search results [3] and [5] do not mention any specific organizations and their internal DevOps practices in detail. They provide general statistics, trends, and strategies related to DevOps adoption and implementation, but do not cite examples of companies sharing comprehensive details about their DevOps workflows and operational practices.
    • Citations:
[1] https://www.atlassian.com/devops/what-is-devops/history-of-devops
[2] https://stackoverflow.blog/2020/06/10/the-rise-of-the-devops-mindset/
[3] https://www.cloudzero.com/blog/devops-statistics/
[4] https://www.toptal.com/insights/innovation/what-is-devops
[5] https://www.cprime.com/resources/blog/devops-implementation-plan-a-comprehensive-6-step-strategy/

2022

  • (RanSom, 2022) ⇒ Aeris Ransom (2022). "How Is Platform Engineering Different from DevOps and SRE?". In: https://thenewstack.io/ TheNewStack].
    • QUOTE: ... “You build it, you run it.” In 2006, this is how Amazon’s CTO Werner Vogels described the company’s approach to software engineering. Amazon’s developers had abandoned the traditional “throw it over the wall” to operations model. Instead, they deployed and ran their applications and services end to end. And so, DevOps was born. ...

2020

  • (Wikipedia, 2020) ⇒ https://en.wikipedia.org/wiki/Continuous_delivery#Relationship_to_DevOps Retrieved:2020-8-26.
    • Continuous delivery and DevOps are similar in their meanings and are often conflated, but they are two different concepts. DevOps has a broader scope, and centers around the cultural change, specifically the collaboration of the various teams involved in software delivery (developers, operations, quality assurance, management, etc.), as well as automating the processes in software delivery. Continuous delivery, on the other hand, is an approach to automate the delivery aspect, and focuses on bringing together different processes and executing them more quickly and more frequently. Thus, DevOps can be a product of continuous delivery, and CD flows directly into DevOps.

2020

  • (Lev, 2020) ⇒ Nir Bar Lev (2020). "The Rise of the Data Engineer". In: BLOG@CACM.
    • QUOTE: ... Moreover, unlike traditional DevOps (where the core task is to replicate the core software applet in as many instances as needed and maintain high availability), here the core task is one of both replicating big training jobs and also running multiple, ongoing, disparate training and experiment jobs in parallel so as to enable an efficient and timely development process. …

2019

2017

  • (Puppet Enterprise, 2017) ⇒ https://puppet.com/solutions/devops
    • QUOTE: DevOps is a way to release better software. It is not just technical tools or workflows. DevOps is also a cultural practice. Devops produces better software, faster by aligning development, staging, and deployment.

      While it is not a fixed methodology, automation and a collaborative culture are the foundation for accepted Devops practices, which include:

      • Measuring the things that have an impact on your organization’s goals
      • Making those measurements visible to everyone
      • Using a shared set of software development tools and best practices
      • Including all teams in the software delivery process from planning to production
      • Automating the development pipeline and removing bottlenecks for faster delivery

2018

2015

Retrieved from "http://www.gabormelli.com/RKB/index.php?title=DevOps_Practice&oldid=946445"