a0002
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.
We are all partakers of inadequate documentation in most projects.
Excessive, impractical, too complete.
The aim is to prepare a dossier closest to the customer's needs, a documentation Abstract unnecessary details and get closer to the real objectives of each project.
We have a system that simply can represent almost any web project.
This methodology is partially detailed on our website Agile Methodologies .
We want to minimize all documents involved in a project and transform the traditional documentation system in a more agile system made fully operational documents and a documentation system that provides all the information that supports fully categorized and documentary aspects of each project.
It's time to forget about PDF documents, Word of countless pages.
It's time to address adequately the concerns and deploy a system to streamline the consultation process, to avoid redundancy and bet on the philosophy of "living document".
This role is vital to good architecture.
We analyze the needs of each role and to prepare documents according to them, and wrapped in a flexible, intuitive and well categorized.
Therefore the definition of the abstractions necessary to achieve this goal both content and in terms of final documentation will be another parameter to consider in a portal architecture.
An overview to help you consolidate the required needs and better serve them with existing systems implies an appropriate approach for future performance and sizing of the portal.
Can use other tools such as Apache Solr to handle searches and filters is a decision that allows our portals to perform at a level better than with the structure of Drupal search.
Delegate to other products and use the modules as containers for configuration information and is a successful approach already followed by Drupal, from the famous Jquery to other modules that allow you to use products or services in order to realize their functionality.
Acquia offers Solr Apache as a service, for example.
It is one of many ways to combine efforts and see the success of the system as a relationship.
So make a good architecture is about making a good relationship with the possibilities of each moment and be aware that the state of the art is constantly changing these relations, which is directly related to the current version of Drupal and any other improvements in other components decant that our architecture can become obsolete.
That is why an ongoing study of the state of the art systems is essential for proper architectural approach with Drupal.
How we get closer to the problems so that the documents are speedy and simple to interpret.
We must simplify the system.
We forget all the methodologies such as UML or others that they have only managed to complicate their representation and closer to the programmer or not so, but emphasize the need for an intermediate position to interpret it.
We must make simplicity to the case, betting on a new air into a single system of components.
This methodology has been a party of architecture defended before the independent entity Red.es of the Ministry of Industry of Spain.
I present a documentation system out of the ordinary:
Agile Methodologies - System Documentation.
We have succeeded in loosening the document all the components, auto components associate requirements and focus exclusively on business customers.
We simplify the model.
And this simplification is architecture
