Tag: Consumer Driven Contracts

Application Pattern: Proxy Consumer Driven Contracts

Proxy Consumer Driven Contracts simulate provider-side testing When Continuous Delivery is applied to an estate of interdependent applications we want to release as frequently as possible to minimise batch size and lead times, and Consumer Driven Contracts is an effective build-time method of verifying consumer-provider interactions. However, Consumer Driven Contracts assumes the provider will readily share responsibility…

Read More

Application Pattern: Consumer Driven Contracts

Consumer Driven Contracts enable independent, interdependent releases When applying Continuous Delivery to an application estate, our ability to rapidly release individual applications is constrained by inter-application dependencies. We want to release applications independently in order to minimise batch size and cycle time, but the traditional risk reduction methods associated with inter-application dependencies compromise lead times and…

Read More

Application Antipattern: Serialisation

Serialisation increases batch size and cycle time When designing applications for Continuous Delivery, our goal is to grow an architecture that minimises batch size and facilitates a low cycle time. However, architectural decisions are often local optimisations that value efficiency over effectiveness and compromise our ability to rapidly release software, and a good example is the…

Read More