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.
Thanks for reading! Wanna work with me?I'm open to software engineering and technical writing projects: growingswe at proton dot me，推荐阅读体育直播获取更多信息
，更多细节参见体育直播
Трамп допустил ужесточение торговых соглашений с другими странами20:46
《酒管财经》认为，万豪需要在品牌矩阵上加大对于存量市场的重视程度，通过覆盖奢华、高端、精选服务等产品，全方位切入我国存量市场，或将有利于提升大中华区的市场地位。，更多细节参见谷歌浏览器【最新下载地址】
新秩序的塑造，就像建造罗马，并非一朝一夕之功，在AI时代的新秩序中，怎么让技术与生态缓慢发酵，让产品与用户共同生长，才是阿里所要回答的终极之问。