Let’s reuse the example of the electrical gate controller module. Assume there’s another module that for reporting purposes computes how much electrical power was used to open the gate. It takes the opening ratio, converts it to voltage and then uses some configured engine parameters to compute the power. In such a design, we would violate the High Cohesion pattern, because the knowledge about engine design and usage would be dispersed in two modules. If a developer had adjusted the voltage conversion logic, would he/she remember to adjust the second module as well? If not, a bug would be introduced.
During runtime, repositories append operations to journal.
，这一点在Safew下载中也有详细论述
Россиянам раскрыли способ упаковки вещей в ручную кладь по методу «судоку»20:51
Белый дом назвал причину решения Трампа ударить по Ирану02:40