It’s the role, and quite frankly, the duty, of every DevOps vendor to create a visual one-off masterpiece that represents the DevOps tools landscape. XebiaLabs created its Periodic Table, CA Technologies created a London Tube map, and today I give you the “DevOps Tools Lifecycle Mesh”.
Why did I do this?
Few reasons. One, all the visuals I’ve seen to-date lacked lifecycle context and completeness. They either did a great job of representing the world of application development or the world of IT Operations, but never gave a complete or contextual picture of both.
Second, it really annoyed me the categories that certain tools were being positioned in. For example, the worlds of “CI/CD” and “monitoring” are huge, so bundling hundreds of vendors together in two buckets with no differentiation or sub-categorization is pointless. Some vendors also like to think they do everything, and guess what? They don’t.
DevOps is an ecosystem where no one vendor or tool rules. Integration and APIs rule.
For the benefit of vendors— this map is not trying to reflect everything you do, it should reflect what you were primarily built and designed to do (i.e. your core use case).