DevOps: Difference between revisions

Revision as of 09:40, 6 July 2025

DevOps is a set of practices that combines software development (Dev) and information technology operations (Ops) aiming to shorten the development lifecycle while delivering features, fixes, and updates frequently in close alignment with business objectives. DevOps is characterized by the use of agile development practices, continuous integration and continuous delivery (CI/CD), automation, and a strong focus on collaboration between development and operations teams. This cultural shift facilitates collaboration and allows for more efficient software development processes.

History

DevOps emerged as a response to the increasing need for organizations to deliver software quickly and efficiently while maintaining high levels of service and reliability. The term "DevOps" was first coined by Patrick Debois in 2009 during the DevOpsDays conference in Ghent, Belgium. The movement sought to address the traditional silos that existed between development and operations teams, which often led to delays and service interruptions.

In the early 2000s, the Agile software development methodology gained popularity, emphasizing collaboration, iterative progress, and responsiveness to change. The principles of Agile laid the groundwork for DevOps, which adopted similar values with a focus on integration and faster delivery cycles. The rise of cloud computing and containerization in the 2010s further accelerated the adoption of DevOps practices, as these technologies allowed organizations to scale their operations more effectively and implement CI/CD pipelines.

Core Principles of DevOps

In order to understand the significance of DevOps, it is essential to explore its core principles, which pivot around four main pillars: culture, automation, measurement, and sharing (CAMS).

Culture

The cultural aspect of DevOps emphasizes collaboration, openness, and shared responsibility across development and operations teams. Organizations that embrace a DevOps culture prioritize creating an environment where employees can freely communicate, share knowledge, and experiment with new ideas without fear of failure. This cultural shift fosters innovation and encourages teams to adopt a growth mindset.

Automation

Automation is a crucial element in the DevOps toolkit. It seeks to streamline and optimize repetitive tasks, such as code deployment, infrastructure provisioning, and testing. By employing automation tools and scripts, teams can reduce human intervention, minimize errors, and ensure greater consistency in their processes. Automation frameworks, including configuration management tools like Puppet and Ansible, as well as CI/CD tools such as Jenkins and GitLab CI, play a significant role in enabling efficient workflows and enabling teams to deliver software more rapidly.

Measurement

Measurement refers to the ability to collect and analyze performance metrics that inform decision-making. This principle encourages teams to define key performance indicators (KPIs) relevant to their processes and objectives. By continuously monitoring aspects such as application performance, deployment frequency, lead time, and mean time to recovery (MTTR), organizations can identify areas for improvement and enhance their software delivery capabilities.

Sharing fosters knowledge exchange and collaboration among teams, promoting a culture of learning and improvement. This principle encourages stakeholders to communicate openly about successes, failures, and lessons learned. By sharing experiences, organizations can cultivate a collective intelligence that leads to better solutions and more efficient processes. Practices such as blameless post-mortems and regular retrospectives strengthen this aspect of DevOps, as they provide a structured approach for reviewing incidents and implementing improvements.

Tools and Technologies

The implementation of DevOps practices often relies on an array of tools and technologies that facilitate the automation, collaboration, and integration of software development and operations tasks. These tools can be categorized into several categories, each serving a distinct purpose in the software development lifecycle.

Source Control Management

Source control management (SCM) systems are essential for version control and collaborative coding. Tools such as Git and Subversion allow multiple developers to work on code simultaneously while maintaining a history of changes. Using SCM systems helps track all alterations, facilitate rollbacks, and enable efficient collaboration among team members.

Continuous Integration/Continuous Delivery (CI/CD)

CI/CD serves as a fundamental component of DevOps by automating the processes of software integration, testing, and deployment. Tools such as Jenkins, Travis CI, and CircleCI allow teams to build automated pipelines that can run tests and deploy applications whenever new code is committed, ensuring consistent and reliable releases.

Configuration Management

Configuration management tools, including Puppet, Chef, and Ansible, provide solutions for automating the configuration and management of infrastructure. By treating infrastructure as code, these tools enable teams to ensure consistent environments across development, testing, and production stages, reducing configuration drift and simplifying maintenance.

Containerization and Orchestration

The rise of containerization technologies, particularly Docker, has drastically affected DevOps practices. Containers encapsulate an application and its dependencies, providing a lightweight and portable environment for deployment. Container orchestration platforms such as Kubernetes facilitate the management and scaling of containerized applications, enabling organizations to achieve high levels of availability and resource efficiency.

Monitoring and Logging

To maintain applications and systems effectively, monitoring and logging tools are indispensable. Solutions such as Prometheus, Grafana, and ELK Stack (Elasticsearch, Logstash, and Kibana) provide real-time insights into the performance and health of applications and infrastructure. By setting up alerts and dashboards, teams can proactively address issues and optimize their systems.

Implementation and Applications

As organizations seek to adopt DevOps practices, implementation may vary depending on the unique context and goals of each organization. However, a set of common steps often serves as a framework for successful adoption.

Assessing Organizational Readiness

Before embarking on a DevOps journey, organizations should assess their readiness for change. This includes analyzing existing workflows, identifying potential bottlenecks, and determining the cultural and technological changes required to implement DevOps practices effectively. Conducting surveys or workshops can help gauge employee sentiments and highlight areas for improvement.

Defining Goals and KPIs

Establishing clear objectives and KPIs is vital for measuring the success of a DevOps initiative. Organizations should identify what they aim to achieve through DevOps, whether it is faster time-to-market, improved quality, or enhanced customer satisfaction. Defining relevant metrics helps monitor progress and demonstrates the business value of adopting DevOps practices.

Training and Skill Development

To successfully implement DevOps, organizations should invest in training programs and skill development for both development and operations teams. This can include workshops, certifications, and hands-on technical training focused on the tools and methodologies associated with DevOps practices. Fostering a culture of continuous learning and improvement is essential to keep abreast of evolving industry standards.

Incremental Adoption

Rather than attempting a full-scale transformation all at once, organizations are encouraged to adopt DevOps practices incrementally. This phased approach allows teams to test new processes, gather feedback, and make adjustments before scaling up. Pilot projects can serve as valuable learning experiences, paving the way for broader adoption across the organization.

Collaboration and Communication

Promoting collaboration and communication between development and operations teams is central to the success of DevOps initiatives. Tools such as chat applications, project management boards, and documentation platforms can facilitate real-time interactions and knowledge sharing. Establishing cross-functional teams composed of members from both domains can further enhance collaboration and accountability.

Real-world Examples

Many organizations have successfully implemented DevOps practices, leading to transformative outcomes in their software development processes and delivery capabilities. Examples from various sectors showcase the effectiveness of this approach.

Spotify

The music streaming platform Spotify is renowned for its innovative application of DevOps principles. Spotify employs a model known as “squads,” where small, cross-functional teams take ownership of specific product areas. Each squad is responsible for the entire lifecycle of their features, from development to deployment. This autonomy allows for rapid experimentation, iterative improvements, and greater responsiveness to customer needs, epitomizing the core values of DevOps.

Amazon

E-commerce giant Amazon is another prime example of successful DevOps adoption. The company has built a culture of experimentation and innovation, enabling it to deploy new features and updates frequently. Amazon leverages continuous deployment processes, allowing for thousands of releases daily. The efficient use of cloud infrastructure and automated monitoring enables teams to respond quickly to issues and enhance the customer experience promptly.

Netflix

Netflix, the leading entertainment subscription service, utilizes a comprehensive DevOps strategy to manage its cloud-based infrastructure. The company emphasizes automation, supporting its philosophy of “failure is an option.” Netflix employs chaos engineering to proactively test resiliency by deliberately introducing failures into production environments, allowing them to build systems that are robust and fault-tolerant.

Etsy

Etsy, an e-commerce platform for handmade and vintage goods, adopted DevOps practices to improve its software delivery capabilities. After transitioning to a CI/CD model, the company reduced deployment times significantly and diminished the number of failures experienced during releases. Etsy's commitment to collaboration between developers and operations teams has led to a more efficient and dependable deployment process while fostering a culture of innovation.

Criticism and Limitations

Although DevOps has gained significant traction and support within the software development community, its adoption is not without criticism and challenges. Some critiques stem from misconceptions about what DevOps entails and the potential pitfalls of implementation.

Misunderstandings of DevOps

One of the primary misconceptions about DevOps is that it solely refers to the use of tools and technologies. Many organizations mistakenly believe that merely adopting the latest software tools will yield the desired outcomes without considering the cultural changes and collaborative practices crucial to its success. This focus on tools over culture can lead to superficial implementation, where core principles of DevOps are overlooked.

Resistance to Change

Cultural resistance is a significant barrier to effective DevOps adoption. Employees may feel apprehensive about changes to established workflows and practices, particularly in organizations with long-standing processes. Change management strategies must be employed to address concerns and help employees adapt to new ways of working. Transparent communication about the benefits of DevOps practices can alleviate fears and encourage buy-in from stakeholders.

Overemphasis on Speed

While DevOps aims to reduce time-to-market, an excessive focus on speed can lead to negative consequences. Pushing teams to release updates too quickly without proper testing, for example, may compromise quality and reliability. Organizations must strive for a balance between agility and robustness, ensuring that the pace of development does not come at the expense of application performance and user experience.

Tool Overload

The vast array of tools available for DevOps can be overwhelming and may lead to “tool sprawl.” Organizations might feel pressured to adopt multiple tools that appear necessary for success, resulting in integration challenges and inconsistencies. Establishing a clear strategy for selecting tools that align with specific goals and workflows is essential to avoid the pitfalls of tool overload.

References

@@ Line 1: / Line 1: @@
-== Introduction ==
+'''DevOps''' is a set of practices that combines software development (Dev) and information technology operations (Ops) aiming to shorten the development lifecycle while delivering features, fixes, and updates frequently in close alignment with business objectives. DevOps is characterized by the use of agile development practices, continuous integration and continuous delivery (CI/CD), automation, and a strong focus on collaboration between development and operations teams. This cultural shift facilitates collaboration and allows for more efficient software development processes.
-DevOps is a set of practices that combines software development (Dev) and information technology operations (Ops) with the aim of shortening the system development life cycle while delivering features, fixes, and updates frequently in close alignment with business objectives. DevOps seeks to help an organization produce software and IT services more rapidly, with a focus on improving collaboration between developers and IT operations teams. The term is also described as a cultural shift wherein the development and operations teams collaborate throughout the entire service lifecycle, from design through the development process to production support.
 == History ==
-The emergence of DevOps can be traced back to several factors impacting software development and IT operations in the late 2000s. The Agile Software Development movement spurred the need for more collaboration and adaptability between developers and operations. As Agile practices emphasized rapid iteration and responsiveness to change, the limitations of traditional IT operations became increasingly evident. Furthermore, the advent of cloud computing and containerization introduced new deployment strategies, fostering a more dynamic environment conducive to DevOps practices.
-The term "DevOps" was popularized by Patrick Debois in 2009 during the first DevOpsDays conference held in Ghent, Belgium. The conference brought together development and operations professionals, leading to discussions on ways to improve collaboration between these historically silos. Since then, numerous methodologies, tools, and practices have emerged, refining and expanding upon the initial concepts of DevOps.
+DevOps emerged as a response to the increasing need for organizations to deliver software quickly and efficiently while maintaining high levels of service and reliability. The term "DevOps" was first coined by Patrick Debois in 2009 during the DevOpsDays conference in Ghent, Belgium. The movement sought to address the traditional silos that existed between development and operations teams, which often led to delays and service interruptions.
-== Design and Architecture ==
+In the early 2000s, the Agile software development methodology gained popularity, emphasizing collaboration, iterative progress, and responsiveness to change. The principles of Agile laid the groundwork for DevOps, which adopted similar values with a focus on integration and faster delivery cycles. The rise of cloud computing and containerization in the 2010s further accelerated the adoption of DevOps practices, as these technologies allowed organizations to scale their operations more effectively and implement CI/CD pipelines.
-A fundamental aspect of DevOps is its emphasis on architecture and design philosophies that support automation, continuous integration, and continuous delivery (CI/CD). These practices facilitate rapid deployment pipelines that allow for efficient and error-free releases. Microservices architecture is often associated with the DevOps model, as it enables teams to manage application features as independent services, thereby allowing teams to update, deploy, and scale applications rapidly without impacting the entire system.
-DevOps architecture typically incorporates several key components, including version control systems, automated testing frameworks, configuration management tools, and monitoring solutions. Tools such as Git for code versioning, Jenkins for continuous integration, Docker for containerization, and Kubernetes for orchestration have become staples in the DevOps toolkit. By fostering greater automation and integration, DevOps architectures enable organizations to achieve higher levels of efficiency and reliability.
+== Core Principles of DevOps ==
-== Usage and Implementation ==
+In order to understand the significance of DevOps, it is essential to explore its core principles, which pivot around four main pillars: culture, automation, measurement, and sharing (CAMS).
-Organizations adopting DevOps principles typically follow a structured approach to implementation that involves cultural transformation, process changes, and the adoption of supporting technologies. The initial step often includes assessing current workflows and identifying areas for improvement. Companies may implement CI/CD pipelines, deploy containerization technologies, and integrate effective monitoring solutions to facilitate rapid feedback loops.
-Training and skill development are critical components during DevOps implementation. Teams require training in various areas, such as scripting, automated testing, and cloud infrastructure management. Furthermore, organizations often establish cross-functional teams that include members from both development and operations to ensure shared ownership and accountability throughout the development lifecycle.
+=== Culture ===
-Organizations may also utilize various maturity models to assess their DevOps capabilities and guide their improvement efforts. These models, like the DevOps Maturity Model, typically outline stages of transformation that measure the extent to which an organization has embraced DevOps practices across different dimensions, including culture, automation, and architecture.
+The cultural aspect of DevOps emphasizes collaboration, openness, and shared responsibility across development and operations teams. Organizations that embrace a DevOps culture prioritize creating an environment where employees can freely communicate, share knowledge, and experiment with new ideas without fear of failure. This cultural shift fosters innovation and encourages teams to adopt a growth mindset.
+=== Automation ===
+Automation is a crucial element in the DevOps toolkit. It seeks to streamline and optimize repetitive tasks, such as code deployment, infrastructure provisioning, and testing. By employing automation tools and scripts, teams can reduce human intervention, minimize errors, and ensure greater consistency in their processes. Automation frameworks, including configuration management tools like Puppet and Ansible, as well as CI/CD tools such as Jenkins and GitLab CI, play a significant role in enabling efficient workflows and enabling teams to deliver software more rapidly.
+=== Measurement ===
+Measurement refers to the ability to collect and analyze performance metrics that inform decision-making. This principle encourages teams to define key performance indicators (KPIs) relevant to their processes and objectives. By continuously monitoring aspects such as application performance, deployment frequency, lead time, and mean time to recovery (MTTR), organizations can identify areas for improvement and enhance their software delivery capabilities.
+=== Sharing ===
+Sharing fosters knowledge exchange and collaboration among teams, promoting a culture of learning and improvement. This principle encourages stakeholders to communicate openly about successes, failures, and lessons learned. By sharing experiences, organizations can cultivate a collective intelligence that leads to better solutions and more efficient processes. Practices such as blameless post-mortems and regular retrospectives strengthen this aspect of DevOps, as they provide a structured approach for reviewing incidents and implementing improvements.
+== Tools and Technologies ==
+The implementation of DevOps practices often relies on an array of tools and technologies that facilitate the automation, collaboration, and integration of software development and operations tasks. These tools can be categorized into several categories, each serving a distinct purpose in the software development lifecycle.
+=== Source Control Management ===
+Source control management (SCM) systems are essential for version control and collaborative coding. Tools such as [[Git]] and [[Subversion]] allow multiple developers to work on code simultaneously while maintaining a history of changes. Using SCM systems helps track all alterations, facilitate rollbacks, and enable efficient collaboration among team members.
+=== Continuous Integration/Continuous Delivery (CI/CD) ===
+CI/CD serves as a fundamental component of DevOps by automating the processes of software integration, testing, and deployment. Tools such as [[Jenkins]], [[Travis CI]], and [[CircleCI]] allow teams to build automated pipelines that can run tests and deploy applications whenever new code is committed, ensuring consistent and reliable releases.
+=== Configuration Management ===
+Configuration management tools, including [[Puppet]], [[Chef]], and [[Ansible]], provide solutions for automating the configuration and management of infrastructure. By treating infrastructure as code, these tools enable teams to ensure consistent environments across development, testing, and production stages, reducing configuration drift and simplifying maintenance.
+=== Containerization and Orchestration ===
+The rise of containerization technologies, particularly [[Docker]], has drastically affected DevOps practices. Containers encapsulate an application and its dependencies, providing a lightweight and portable environment for deployment. Container orchestration platforms such as [[Kubernetes]] facilitate the management and scaling of containerized applications, enabling organizations to achieve high levels of availability and resource efficiency.
+=== Monitoring and Logging ===
+To maintain applications and systems effectively, monitoring and logging tools are indispensable. Solutions such as [[Prometheus]], [[Grafana]], and [[ELK Stack (Elasticsearch, Logstash, and Kibana)]] provide real-time insights into the performance and health of applications and infrastructure. By setting up alerts and dashboards, teams can proactively address issues and optimize their systems.
+== Implementation and Applications ==
+As organizations seek to adopt DevOps practices, implementation may vary depending on the unique context and goals of each organization. However, a set of common steps often serves as a framework for successful adoption.
+=== Assessing Organizational Readiness ===
+Before embarking on a DevOps journey, organizations should assess their readiness for change. This includes analyzing existing workflows, identifying potential bottlenecks, and determining the cultural and technological changes required to implement DevOps practices effectively. Conducting surveys or workshops can help gauge employee sentiments and highlight areas for improvement.
+=== Defining Goals and KPIs ===
+Establishing clear objectives and KPIs is vital for measuring the success of a DevOps initiative. Organizations should identify what they aim to achieve through DevOps, whether it is faster time-to-market, improved quality, or enhanced customer satisfaction. Defining relevant metrics helps monitor progress and demonstrates the business value of adopting DevOps practices.
+=== Training and Skill Development ===
+To successfully implement DevOps, organizations should invest in training programs and skill development for both development and operations teams. This can include workshops, certifications, and hands-on technical training focused on the tools and methodologies associated with DevOps practices. Fostering a culture of continuous learning and improvement is essential to keep abreast of evolving industry standards.
+=== Incremental Adoption ===
+Rather than attempting a full-scale transformation all at once, organizations are encouraged to adopt DevOps practices incrementally. This phased approach allows teams to test new processes, gather feedback, and make adjustments before scaling up. Pilot projects can serve as valuable learning experiences, paving the way for broader adoption across the organization.
+=== Collaboration and Communication ===
+Promoting collaboration and communication between development and operations teams is central to the success of DevOps initiatives. Tools such as chat applications, project management boards, and documentation platforms can facilitate real-time interactions and knowledge sharing. Establishing cross-functional teams composed of members from both domains can further enhance collaboration and accountability.
 == Real-world Examples ==
-Numerous organizations across diverse industries have successfully adopted DevOps practices, yielding significant improvements in their software delivery processes. For example, companies such as Netflix have incorporated DevOps principles to enhance their video streaming platform. Through a focus on continuous delivery and the use of microservices architecture, Netflix can deploy thousands of code changes daily, ensuring rapid updates and feature releases.
-Another notable example is Amazon, which employs DevOps methodologies to support its e-commerce and cloud services. The company's emphasis on automation and scalability allows it to maintain a competitive edge by rapidly deploying new features and swiftly addressing customer feedback.
+Many organizations have successfully implemented DevOps practices, leading to transformative outcomes in their software development processes and delivery capabilities. Examples from various sectors showcase the effectiveness of this approach.
+=== Spotify ===
+The music streaming platform [[Spotify]] is renowned for its innovative application of DevOps principles. Spotify employs a model known as “squads,” where small, cross-functional teams take ownership of specific product areas. Each squad is responsible for the entire lifecycle of their features, from development to deployment. This autonomy allows for rapid experimentation, iterative improvements, and greater responsiveness to customer needs, epitomizing the core values of DevOps.
+=== Amazon ===
+E-commerce giant [[Amazon]] is another prime example of successful DevOps adoption. The company has built a culture of experimentation and innovation, enabling it to deploy new features and updates frequently. Amazon leverages continuous deployment processes, allowing for thousands of releases daily. The efficient use of cloud infrastructure and automated monitoring enables teams to respond quickly to issues and enhance the customer experience promptly.
+=== Netflix ===
+[[Netflix]], the leading entertainment subscription service, utilizes a comprehensive DevOps strategy to manage its cloud-based infrastructure. The company emphasizes automation, supporting its philosophy of “failure is an option.” Netflix employs chaos engineering to proactively test resiliency by deliberately introducing failures into production environments, allowing them to build systems that are robust and fault-tolerant.
+=== Etsy ===
+Etsy, an e-commerce platform for handmade and vintage goods, adopted DevOps practices to improve its software delivery capabilities. After transitioning to a CI/CD model, the company reduced deployment times significantly and diminished the number of failures experienced during releases. Etsy's commitment to collaboration between developers and operations teams has led to a more efficient and dependable deployment process while fostering a culture of innovation.
+== Criticism and Limitations ==
+Although DevOps has gained significant traction and support within the software development community, its adoption is not without criticism and challenges. Some critiques stem from misconceptions about what DevOps entails and the potential pitfalls of implementation.
+=== Misunderstandings of DevOps ===
-Many enterprises in sectors such as finance, healthcare, and telecommunications are also integrating DevOps practices to enhance their service delivery. By fostering collaboration between development and operations teams, these organizations can respond more quickly to market changes and improve service reliability.
+One of the primary misconceptions about DevOps is that it solely refers to the use of tools and technologies. Many organizations mistakenly believe that merely adopting the latest software tools will yield the desired outcomes without considering the cultural changes and collaborative practices crucial to its success. This focus on tools over culture can lead to superficial implementation, where core principles of DevOps are overlooked.
-== Criticism or Controversies ==
+=== Resistance to Change ===
-Despite its growing popularity, DevOps has faced criticism and scrutiny over its implementation and effectiveness. Some industry experts argue that the term "DevOps" can become a catch-all phrase that lacks substance and clarity. They caution that organizations might adopt its principles superficially without fully realizing the cultural shift required for genuine transformation.
-Additionally, some detractors note that the focus on speed and agility can occasionally lead to the neglect of security practices, an issue often referred to as DevSecOps. As organizations prioritize rapid software delivery, vulnerabilities may emerge if security considerations are not integrated into the DevOps process.
+Cultural resistance is a significant barrier to effective DevOps adoption. Employees may feel apprehensive about changes to established workflows and practices, particularly in organizations with long-standing processes. Change management strategies must be employed to address concerns and help employees adapt to new ways of working. Transparent communication about the benefits of DevOps practices can alleviate fears and encourage buy-in from stakeholders.
-Another criticism pertains to the scalability of DevOps practices. While smaller teams may swiftly adopt DevOps methodologies, larger organizations could struggle to coordinate efforts across multiple departments, leading to inconsistent practices and difficulties in achieving a shared vision.
+=== Overemphasis on Speed ===
-== Influence and Impact ==
+While DevOps aims to reduce time-to-market, an excessive focus on speed can lead to negative consequences. Pushing teams to release updates too quickly without proper testing, for example, may compromise quality and reliability. Organizations must strive for a balance between agility and robustness, ensuring that the pace of development does not come at the expense of application performance and user experience.
-The influence of DevOps extends far beyond individual companies; it has permeated the broader software development culture and industry practices. The movement has prompted the growth of tooling ecosystems designed to support continuous integration, delivery, and deployment. As organizations increasingly embrace cloud computing and microservices, the need for DevOps expertise continues to rise.
-DevOps has also led to the emergence of complementary practices such as Site Reliability Engineering (SRE), which marries development and operations further while emphasizing reliability and scalability within system designs. SRE practices have been adopted widely by tech giants like Google to enhance their service reliability.
+=== Tool Overload ===
-Furthermore, various industries are recognizing and establishing their own GitOps and NoOps initiatives, where the focus is on leveraging Git as the source of truth for the entire deployment process, alongside minimizing manual intervention in operations, respectively. These methodologies showcase the continual evolution and embedding of DevOps principles across the tech landscape.
+The vast array of tools available for DevOps can be overwhelming and may lead to “tool sprawl.” Organizations might feel pressured to adopt multiple tools that appear necessary for success, resulting in integration challenges and inconsistencies. Establishing a clear strategy for selecting tools that align with specific goals and workflows is essential to avoid the pitfalls of tool overload.
 == See also ==
@@ Line 44: / Line 119: @@
 * [[Continuous integration]]
 * [[Continuous delivery]]
-* [[Microservices]]
+* [[Infrastructure as Code]]
-* [[Site Reliability Engineering]]
+* [[Site reliability engineering]]
+* [[Cloud computing]]
 == References ==
-* [https://www.devops.com DevOps.com]
+* [https://aws.amazon.com/devops/ AWS DevOps]
-* [https://www.atlassian.com/devops Atlassian DevOps Resources]
+* [https://azure.microsoft.com/en-us/overview/devops/ Azure DevOps]
-* [https://www.redhat.com/en/topics/devops DevOps Overview by Red Hat]
+* [https://www.ibm.com/cloud/learn/devops IBM DevOps]
-* [https://aws.amazon.com/devops/ Amazon Web Services DevOps]
+* [https://www.atlassian.com/devops Atlassian DevOps]
-* [https://www.ibm.com/cloud/learn/devops/overview IBM Cloud DevOps Overview]
+* [https://www.redhat.com/en/topics/devops Red Hat DevOps]
+* [https://devops.com DevOps.com]
 [[Category:Software development]]
-[[Category:Information technology]]
+[[Category:IT operations]]
 [[Category:DevOps]]