Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Questions about modularity

 
Damian Cardozo
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello, I would like to know if modularity is recommended even for small-sized applications. Can I see its benefits even there? I'm afraid to add complexity and don't get so much in return..
Also, does MVC fit anywhere in modularity? Can the model, view and controller be considered as modules? Or should modules be more fine-grained?

Thanks
 
Kirk Knoernschild
author
Ranch Hand
Posts: 41
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I firmly believe modularity is a requirement for large software systems. For small software systems (say > 10k loc), modularity isn't absolutely necessary, at least from a design perspective since smaller systems are inherently easier to understand. Of course, there are other reasons to use modularity, such as deploying different versions of a module alongside each other in the same JVM, hot deployment, or plugin architecture. Even for small systems, modularity can be beneficial. Like all things, modularity is a valuable tool in your arsenal of tools. I tend to shy away from absolutes, because there is always an exception. But I'd have to believe a system must be very small with very simple requirements not to benefit from modularity.

Visit the book's website at modularity.kirkk.com where you can review all 18 patterns and download an excerpt of the book. There is also a mobile web application available that you can take with you wherever you go.

--kirk
Twitter: @pragkirk
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic