Operations | Monitoring | ITSM | DevOps | Cloud

My favorite ice cream store is just off Richmond Green, close to where I live in West London. On sunny days, locals queue around the block to buy their fantastic gelatos and sorbets. Every one of their customers knows that they could easily nip into the supermarket around the corner to buy hermetically sealed chocolate ice cream, but they queue anyway. Why?

Fulfillment pipelines for order management in e-commerce have a lot of intricate moving parts that depend on one another. Sales orders, fulfillment, negotiation, shipment, and receipt are closely interconnected but require different actions while depending on one another closely. You also need messaging around order statuses, conditions, actions, rules, and inventory, just to name a few of the important parts of these complex systems.

Long release cycles are no longer viable in the world of software development. The promise of DevOps has been to materially shrink time to value. Like most meaningful transitions, this one hasn’t always been a simple flip of a switch. For many organizations, development teams have become complex and unwieldy. So, the custodians of DevOps have found it difficult to achieve broader adoption of DevOps principles across engineering teams.