Главная
Study mode:
on
1
Introduction
2
Why Rapid Release
3
Criteria That Influence Design
4
Making It Easy To Release
5
Deployment Impacts
6
Incremental Changes
7
Shared Libraries
8
Managing Risk
9
Circuit Breakers
10
AntiPatterns
11
Capabilities
12
Services
13
Shared Serialization
14
Postelles Law
15
Databases
16
Service
17
Summary
18
Question
Description:
Explore the architectural considerations for enabling rapid and frequent software releases in this 51-minute conference talk from GOTO Aarhus 2012. Delve into the constraints and patterns that influence system design for Continuous Delivery, moving beyond build pipelines and infrastructure automation. Learn how to identify and address design issues in your own systems that may hinder incremental feature rollouts. Discover key topics such as deployment impacts, shared libraries, risk management, circuit breakers, anti-patterns, capabilities, services, shared serialization, Postel's Law, and databases. Gain insights from ThoughtWorks technical consultant Sam Newman on evolving system architecture to support rapid release cycles and improve your Continuous Delivery practices.

Designing for Rapid Release

GOTO Conferences
Add to list