By Steve Burton
January 9, 2018

Its 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 created a 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.

(Click To Enlarge)

Below are the high-resolution links to the DevOps Lifecycle Mesh:

JPEG (873KB)

PNG (1.2MB)

GIF (443KB)

TIFF (25.2MB)

PDF (2.6MB)

The above was used to print a 40″x30″ poster and it looks great:

Feel free to download, print, share, and comment. Something like this is never going to be 100% accurate but I did put in several hours of research and noodling to think this through.

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).

Cheers,
Steve.

@BurtonSays

➞ Back to Blog

14
Leave a Reply

avatar
8 Comment threads
6 Thread replies
2 Followers
 
Most reacted comment
Hottest comment thread
7 Comment authors
Cristian BalanKaren TaggartNabYaron ParasolSteve Burton Recent comment authors
  Subscribe  
newest oldest most voted
Notify of
Cristian Balan
Guest

Very good indeed. I’ll also recommend adding BitNinja.io under Security and Papertrail under Logs. Thank you.

Karen Taggart
Guest
Karen Taggart

Also, not to be picky, but you should extend Jenkins, specifically CloudBees Jenkins, into the CD and monitor sections. 🙂

Karen Taggart
Guest
Karen Taggart

This is wonderfully helpful! Thanks for doing this. I was just looking for a tool like this to do some training. Thank you for being so open and sharing your knowledge.

Nab
Guest
Nab

Any support for openshift containers orchestrator ?

Yaron Parasol
Guest
Yaron Parasol

Steve,
few suggestions
1. Add TICK to infra monitoring
2. Add security testing like ZAP
3. Add Chaos frameworks

Yaron Parasol
Guest
Yaron Parasol

Steve,
You are missing some important tools for the container world:
Image scanning, Image signing and registries in the build section
Also in terms of security missing source & dependencies scanning for vulenabilities

Chris Robertson
Guest

You missed Scalyr in the Log Management section (yes, I’m biased as I work there, but we really are better/faster).

Dexter Berkeley
Guest
Dexter Berkeley

I think you spelt Cisco wrong in the APM box.