Drupal 8 Lessons From the Field: Part 3 - The Drupal Backend

Pavithra Raman - Solutions Architect Team Lead, Acquia
Ron Northcutt - Senior Solutions Architect, Acquia

Coming back to our discussion on fast internet, we have so far covered how to optimize a developer’s journey and enhancing frontend website delivery.

In our next session, we shall look into a very core part of the Drupal ecosystem - the Drupal backend. These are the components that create, update and get the content that you show to your end users. It controls user permissions, what content to show on which page, and uses modules like views to get more content to show as a list or a slideshow. It powers the search features, menu system, every page structure and more. The more work you give it, heavier is the load on it. And that makes it slow.

So why don’t we help our Drupal backend system, to ease the load, speed up what it is looking for, cache a few frequent tasks its performs and give it a nice booster! Why? If the backend system fails, it will timeout and not render any output for the requests that come in. Each request will be put in a long and slow queue to get a response. Only when we get an initial response to the browser or an API call, can the rest of the page rendering begin.

To learn how to alleviate these problems, join our tech talk to learn about:

  • Drupal Architecture - module selection, content structure, page structure
  • Content displays
  • Content reuse
  • Views, Blocks, Panels
  • Caching data - memcache
  • Caching code - APC
  • MySQL tuning - Check Slow queries
  • XHProf - Check any heavy PHP code
  • Contrib v/s Custom
  • Dynamic page cache
  • Disable non-Prod modules
  • Database Logs - switch it to syslog
  • Acquia Insight Tool
  • API first & Decoupled Drupal