I am working on this website that catalogues products with their basic information and all. I checked and all the different input features required were possible using a combination of fields(cck) and some related modules, features like multi image upload, multiple field values, dependent fields, node reference. My only fear is this would result in a good number of tables that would effect performance. How serious would that performance hit be is what I am curious about? The website is for a niche segment and wont be expecting thousands of users at the same time, maybe a couple hundred simultaneous users during some promotional event, thats it.
I can code everything from scratch but the last time I tried it in drupal 6, there were a lot many hurdles, specially for ajax based dynamic forms and we are a bit tight on schedule. So i just need some help figuring out if the extra effort would be really worth it.
Thanks.
(ALSO: Why did field/cck have to take a table for each field route instead of a table for a content type? Wouldn’t that have been more efficient?)
There is alot of ajax functionality out of the box, multi image upload etc … so that depends on what you need, and if the functionality is allready available.
I have drupal websites with 1000+ visitors a day, with the right caching this is no problem.
The content type fields have their own table now, because they restructured everything to entitys. This makes everything more generic and abstract, so that functionality is now not specific to cck, or one module, but for every module at the same time. Sure this propabely affect the performance, but again, with the right caching enabled this shouldn’t be a problem.
Conclussion: Is it worth the effort ? That totaly depends on what you need to create exactly, and how much you can use from existing modules. Also on how often you will have to change things, how large your catalogue …