Taming the Rate of Change

Thanks to the cloud, micro-services, and investments in CI/CD pipelines, teams that used to release code once or twice a month to production until a few years ago are now introducing production changes several times a day. Conversely, low change frequency indicates high time to create value and low team performance. Our systems are an interconnected heterogeneous set of fast-changing and slow changing experience, we can make the following observations of such architectures:
Since not every part of the architecture has the same need for high change frequency, each part may get different levels of people and time investments.

Source: m.subbu.org