My client wants to develop web app where huge pieces of functionality will be added over the next 3 years. And the product should be able to last for 10 years minimum.
I've suggested building the system in a very modular fashion.There will have to be a base framework and a set of core modules for database abstraction, accounts and other things specific to the business logic of the company, and then use modular MVC-Areas for the large pieces of functionality that depend on the core business modules.
The application must support theming too.I look at this and think "they want me to build a CMS."
Great, so as I look at building functionality for all these things I see Orchard and think to myself "This has everything a guy with a fetish for extensibility needs!" As good as orchard looks I am worried about relying on a 3rd-party framework, and any gotcha's I'll hit along the way, especially in years to come.So I'll summarise my points of interest:[*]Do you think I should use orchard as a base for my web-app and have all business functionality living in modules?[*]Using this architecture I would need module having dependancies to other "business core modules", does orchard support such a thing?[*]Are you aware of any possible gotcha's related to using orchard in this fashion?
I've suggested building the system in a very modular fashion.There will have to be a base framework and a set of core modules for database abstraction, accounts and other things specific to the business logic of the company, and then use modular MVC-Areas for the large pieces of functionality that depend on the core business modules.
The application must support theming too.I look at this and think "they want me to build a CMS."
Great, so as I look at building functionality for all these things I see Orchard and think to myself "This has everything a guy with a fetish for extensibility needs!" As good as orchard looks I am worried about relying on a 3rd-party framework, and any gotcha's I'll hit along the way, especially in years to come.So I'll summarise my points of interest:[*]Do you think I should use orchard as a base for my web-app and have all business functionality living in modules?[*]Using this architecture I would need module having dependancies to other "business core modules", does orchard support such a thing?[*]Are you aware of any possible gotcha's related to using orchard in this fashion?