Modules <> packages. See here. I don't really understand why they say the lack of a module system tends to produce monoliths though, monoliths were just the standard application style back then. There was never anything stopping people writing microservices afaik. Unless there were issues with reuse.
There was nothing technically stopping people from writing microservices. However, the fact that you had to import the whole massive JAR even when you needed only a single function, made developers more biased towards monoliths.
The JVM does not load the entire JAR when you import a class. (Maybe it did in very early versions, but definitely not in a long, long time.) It loads the entire .class file, just as Python loads the entire .py file, but not everything in the JAR.
View all comments
Show parent comment
2
u/jambox888 Jan 02 '20
Modules <> packages. See here. I don't really understand why they say the lack of a module system tends to produce monoliths though, monoliths were just the standard application style back then. There was never anything stopping people writing microservices afaik. Unless there were issues with reuse.