Do not transfer sites to Drupal!

    I will begin my first post with a small note about Drupal, which I recently started using, as well as which I fell in love with and at the same time disappointed. Fell in love because of the immense breadth of opportunities that this engine provides. A bunch of modules, a nice architecture for a programmer (to modify a file or write your own module), incredible flexibility - all this will not leave indifferent, like, in other things, and how all this economy starts to slow down when it grows!

    I had a website and I decided to refresh it with the help of a modern community-oriented engine, which is Drupal. The site was self-written, simple. Worked quickly because used caching in statics and return of this statics on nginx. He had the dignity of human-readable URLs (CNCs). When translating to Drupal, it was required to use the Path module, which is included in the standard package, to recreate the CNC on the site. This led to the fact that when forming the page occurs: - for the main 400-600 queries to the database; - for nested 200-400 queries to the database. Drupal searches for each taxonomy tag in its URL alias.

    With a small number of tags in the database, the situation can be corrected by editing the module code so that it receives the entire alias table in one request. But when the base grows and starts to include the entire vocabulary of the site’s subject, there’s nothing to be done ...

    Drupal has additional problems with fouling with modules. On shared hosting, the 16MB limit for PHP may not be enough. If anyone knows about 32MB virtual hosting, let me know! On VPS, sprawling Drupal runs slowly due to MySQL hanging out on the same VPS. You can get out of this by spacing Drupal and MySQL into different hosts (you can keep MySQL on a shared hosting - there is usually a separate server for it). Someone will say that you need to take a separate server, but for this the project should at least pay off, and Drupal usually does amateur projects, sometimes not at all profitable, but existing for the soul.

    Last summary
    At Drupal, it's best to do projects from scratch, while preserving its internal obscure addressing. In advance, you need to think through the structure of the site in order to understand which modules will need to be used. If you are planning a project with high attendance, then consider writing your own engine, as you’ll certainly spend less time optimizing Drupal later.

    Also popular now: