Modules add another layer above the current access control constructs in Java world (public, private, etc). There are several benefits to them, like discovering a missing dependency much earlier on (statically), not importing the code we are not using, avoiding cyclic dependencies between modules, etc. More importantly it enforces better design and provides some tooling to have a better 10000-feet view of your project. I think its going to come in very handy in managing larger codebases.
You could visit these links to know more from a web-dev backend point of view.
Ps... I created a library in Nodejs that implements concepts of modularity in JS codebases. Its known as archiejs (on github). I think modularity is a very useful feature that lot of people are going to want to use in Java (and also other programming languages).
You could visit these links to know more from a web-dev backend point of view.
* https://www.oreilly.com/ideas/modules-vs-microservices
* https://www.youtube.com/watch?v=fDoiydWS3D4
* https://www.youtube.com/watch?v=O77777Zy_HE
Ps... I created a library in Nodejs that implements concepts of modularity in JS codebases. Its known as archiejs (on github). I think modularity is a very useful feature that lot of people are going to want to use in Java (and also other programming languages).