DevOps Topologies

Different teams and topologies have differing levels of effectieness. Some are very effective, some are conditionally effective, and some are so commonly ineffective that they are known as anti-patterns. Ultimately, every topology should serve the purpose of enabling Continuous Compliance, and fostering Continuous Learning.

While each team might be different, there are some common Signs of a Highly Effective Architecture.

Throughout the common effective topologies, and examining the small differences between some types of effective teams and their ineffective “variants,” a few patterns emerge: Detecting Agile BS contains some useful advice for spotting signs of ineffective topologies; the differences are mostly in culture, which is why high performing teams view DevOps as a cultural movement.

  • Early Ops involvement and collaboration in application development lifecycle is essential to prevent costly technical debt from racking up.
  • Attempting to shoehorn ops skills and activities into a project can end up costing a lot of time and investment.
  • DevOps requires human communication skills to thrive in an organization.
  • Ops inside dev teams can lead to half-baked solutions as ops is treated as an annoyance for devs.

To combat some deficiencies:

resources:

Links to this page