Building a Delivery Ecosystem: Part 1
Confused about which teams need DevOps engineers? Even more confused about whether you need a standalone DevOps team, or perhaps a DevSecOps, NetDevOps, or SecDevNetOps team? Do you have FOMO (fear of missing out) over all things mesh?
We enjoy increasingly diverse ways to create value using technology, but the way in which we deliver software, configuration, and data can be complex. Engineers are more successful when they share an understanding of what they build and operate, along with their dependencies on value delivery processes. In this post, we refer to the collection of processes, products, and services that an engineering team relies on to publish products or deliver value to their customers as a delivery ecosystem.
What is a delivery ecosystem?
Imagine a shipping company. To deliver packages in an accurate and timely fashion, this company requires physical infrastructure around the country or world including sorting centers, warehouses, major hubs, and airports. In addition, the company builds transportation capabilities using planes, trains, trucks, drivers, workers, and more to move goods.
If one sorting center follows a different procedure than the others, then it may send a package to the wrong recipient. If there are not enough drivers to deliver presents for the holiday season, then packages are delivered two months later than expected. If a storm sweeps through a region and routes…
