c.- Architectural Keys: Correct definition of needs in terms of system architecture
The product in question is quite complex, but that complexity is an ongoing challenge and a constant basis in the same capacity.
Certainly a simple product can hardly be a product of quality, as it will increase the range of features grows equally complex.
This is why we consider a good selection of modules, component.
It's transcendental analysis of hardware requirements for the portals, memory and system configuration.
Caching mechanisms.
The modules that can increase this efficiency.
And of course make a comprehensive approach taking into account the current needs and state of the art product.
If we use a version 5.x know we can not use a version of php 5.3.
Instability has been shown with modules such as Content Templates.
Turn as modules which are only there for another version, which have no other continuity.
It is important to continued study of all modules and opcodes that requires the product.
At the same time is important to consider that a system is not just Drupal.
There are great strides to achieve a more efficient system both by Acquia as other companies like inviting Chapter 3 bet on a system with Mercury.
But in this system is very complex attach to a control panel.
Currently there are no instructions for installing Mercury with WHM / Cpanel, so we must consider the needs of the portal to ask if we can really use Mercury or only whole Varnish, Memcached , PRESSFLOW, etc.
It is a proof that the state of the art of these technologies is constantly changing, so it is very important to keep in mind to fit the needs of the system to the most appropriate settings for it.