Continuous Delivery is not a Commodity

Anton WeissOtomato : http://otomato.link

Footer

Definition

• The term commodity is used for an good or service when the demand for it has no qualitative differentiation across a market.

• Commoditization occurs as a goods or services market loses differentiation across its supply base, often by the diffusion of the intellectual capital necessary to acquire or produce it efficiently.

Wikipedia

Footer

Examples:

• Sugar• Oil• Gold• Unskilled Manual Labour• Flash memory

Footer

Examples in Software Development:

• Java app servers• Cloud Instances• Hosted VCS, Change Management, etc.• CloudStack and OpenStack are commoditising

virtualisation providers and cloud providers• Microservices (?)

Footer

Commodity Software Properties

• A well-defined and limited set of:• required features• required interfaces• use cases

• Easy to learn and master• As a result:

• Weak lock in (if any)

Footer

But Continuous Delivery is simple, isn’t it?

Footer

It’s Babylon!

Footer

Continuous Delivery Requires

• Integration with multiple tools and frameworks• Support for multiple OS• Customizable flows• Customizable dashboards and reporting• Pluggable architecture

Footer

Conclusions

• No one CD pipeline is exactly the same as another• You can learn from others but you can not copy• You can’t buy Continuous Delivery• CD is a process and not a tool• CD is more art than science

Footer

Butler to the Rescue!!!

• Flexibe• Extendable• REST API• Groovy scripting• More than a 1000 plugins• Strong community support

Footer

But most importantly:

• We need CD professionals who:• understand the software development workflow• realize that CD is more about people than

technology• are eager to learn, contribute and share

Footer

Thank You Sponsors