Let’s illustrate the concept of modules by an example. Assume there’s a requirement for a rich-client application to perform an auto-update process. This requirement during the design process will become the application’s responsibility. If we assign it to an Auto-Updater Module, it will mean that fulfillment of this responsibility lies solely with this module. Not-modular approaches often lead to scattering responsibility among so-called “modules” like “model”, “database”, “infrastructure”, “domain”. But in the modular approach, if it’s decided that auto-update is not needed anymore, we should be able to get rid of this responsibility by deleting just one module (and its wiring to other modules), without the need for the shotgun surgery throughout layers.
Материалы по теме:。51吃瓜对此有专业解读
Иран назвал путь к прекращению войны14:05，详情可参考wps下载
Стало известно о брошенных на севере Украины наемниках ВСУ08:51
Min: 0.128 ms | 0.069 ms