Environment parity
Originally called the dev/prod parity in the 12 principles, the goal was to ensure that gaps between development and production were small or non-existent. This has been expanded to be Environment parity to achieve the goal that the application when built and released as per guidelines, should 'work anywhere' in any related environment. There are three factors known to affect parity, and they are time, people, and resources. The time relates to the situation where an application takes days, weeks, or even months to go into production. By then, multiple changes or factors (business, bug fixes, external, and so forth) may have affected the outcome of the application to go into production. By reducing the time, it is possible ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access