One of the advantages of a modular architecture, where the modules are self contained, is that you can replace or add any module without affecting the rest of the system.
When it comes to Web development and high level frameworks, Symfony is the only one that gives you the option to implement modules, but because the system wasn't created with a Modular Architecture in mind, it fails to provide all the advantages this architecture has to offer.Quote:
A module is a self-contained component of a system, which has a well-defined interface to the other components; something is modular if it includes or uses modules which can be interchanged as units without disassembly of the module. Once the module exists, it can easily be connected to or disconnected from the system.
So, What if a high-level framework has components and modules. And those modules are self contained and they have their own MVC implementation. Their own Action Controllers, Models and Views. What if a website is built based on modules? For example:
It might take us 1 day to create the "contact-us" module, but once we have it, it will only take us 1 hour to implement it in another site. So, is the modular architecture a good approach to RAD?Code:
I'd like to know your opinion on this :)