DevOps uses a capability model, not a maturity model

Re:DevOps uses a capability model, not a maturity model by samsquire on Thursday April 06, 2023 @08:22AM (#35467371)

I'm imagining something similar to a 3D wireframe model of networks and systems, with particles that move around between nodes that represent requests or IOPS.

Circuit breakers, bottlenecks, IOPs, load shedding, traffic behaviours can all be visualised.

I'm not sure how you would represent latency with this visualization but that's also important. It more represents throughput.

Can also be used to represent human work/tasks itself.

[ Parent | on HN ]

Re:DevOps uses a capability model, not a maturity model by hendry on Thursday April 06, 2023 @09:02AM (#35467794)

Sounds a bit complex, I usually stick to the R.E.D. method for services and from the devops perspective largely iteration speed.

[ Parent | on HN ]

Re:DevOps uses a capability model, not a maturity model by Leo_Germond on Friday April 07, 2023 @01:14AM (#35478279)

Well you could use some heatmap to represent latency, where the hottest part would be those of high latency, turn those particles and boxes red or blue depending on their mean latency...

[ Parent | on HN ]