Browserless Drupal: Render Unto Caesar, Don't Render Unto APIs


Drupal is fantastic at rendering content for people, but increasingly, people aren't the consumers of web traffic; machines are.  You may already be using Drupal as an API endpoint, perhaps by posting content via Services or rendering content with AngularJS, but Drupal can also serve a system integration role where no people are involved at all in real time, and then you get a top notch human interface for auditing and reporting more or less built-in. We'll talk about the strategic advantages (and disadvantages) of the approach, and look at a few common models for talking to machines and reporting results:

  • Synchronous REST
  • Asynchronous AMQP
  • Using nodes to aggregate batch operations
  • Reporting results on the node itself

Session Track

Coding and Development

Experience Level


Drupal Version