![]() ![]() So, in short, a module should adhere to three core principles – 1.1. To complete its tasks, it may be dependent on other modules, which it should declare explicitly. ![]() It should be self-sufficient for that capability and should expose only interfaces to use the module functionality. In terms of application architecture, a module shall represent a specific business capability. Any application generally is a combination of multiple modules which work together to perform the business objectives. Ideally, these artifacts are recognizable from compile-time all the way through runtime. In any programming language, modules are (package-like) artifacts containing code, with metadata describing the module and its relation to other modules. Difference between modular and non-modular code Introduction to Java Platform Module System
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |