Continuous Delivery asks that we optimise lead times in order to grow product revenues, but all too often the cost of the technical change outweighs the value of the business change.
We will discuss how software architecture is often an impediment to Continuous Delivery. Also outline some design patterns - Tolerant Reader, API Examples, Consumer Driven Contracts - that form a low-cost risk reduction strategy.
YOU MAY ALSO LIKE:
- Release Testing Is Risk Management Theatre (SkillsCast recorded in August 2014)
- Invitation to Systems Thinking with Jessica Kerr and Kent Beck (Online Course on 21st - 23rd June 2021)
- Better Software Faster with Dave Farley (Online Course on 12th - 13th July 2021)
- CloudNative eXchange Forum 2021 (Online Conference on 21st - 23rd June 2021)
- Software Architecture Gathering Digital 2021 (Online Conference on 13th - 14th October 2021)
- Tooling Up! - Contract testing with Pact (Online Meetup on 7th July 2021)
- Managing Commercial Platforms: The Architect’s Emerging Skill (SkillsCast recorded in June 2021)
- Embracing Hexagonal Architecture with Serverless (SkillsCast recorded in June 2021)
Breaking the Mold for Continuous Delivery
An XP / Lean developer with 10+ years of experience in enterprise software development in Britain and New Zealand, Steve Smith favours practices such as Pair Programming and Test Driven Development to build quality into software products.