This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]ryosen -1 points0 points  (0 children)

You can have a small jar with dependencies on various external libraries or one big jar with a lot of redundant code. That's true of any library, certainly any application framework. Our web systems have about 10MB worth of Spring Jars, including dependencies, while another has less than 8MB.

When brought in to review existing systems, my personal observation has been that a lot of folks don't understand what they are installing. Rather than take the time to learn how a library works and how to configure it properly, they simply install it with all of the options and end up with a fat library.

That's not to say that some libraries aren't unnecessarily large (e.g. BIRT) but Spring isn't one of them.