Drupal 8's decoupled architecture is one of the biggest and most significant changes from previous versions of Drupal, and as a result, it is important for decision-makers to obtain a more thorough understanding of their expanding architectural options. Far from being an abstract technical decision, choosing a Drupal architecture type has real business implications and should be rooted in long-term goals.
That's why we wrote a white paper giving a detailed breakdown of four of the most common Drupal architecture solutions: the end-to-end framework, the content aggregator, the content repository, and decoupled Drupal. The white paper, written for non-technical stakeholders, explains how to evaluate each type in light of your business objectives. You can download the entire white paper here, but in the meantime enjoy a quick excerpt...
Drupal as a Content Aggregator
When Drupal is used as a content aggregator, it is primarily a tool for pooling data together from other sources. In this instance, the term data applies to any type of consumable content, including text, images, videos, news wires, statistics, and more. Using both push and pull mechanisms, Drupal “consumes” content. Then Drupal acts as the centralized place to assemble content, organize it, and send it out.
Drupal’s Push and Pull
How does Drupal acquire all this data? Some organizations opt to pull for content, a technique in which Drupal is constantly searching for relevant information through APIs. Drupal 8 is an even more powerful content “puller” than previous versions of Drupal: the introduction of RESTful web services directly in core allows Drupal to consume exposed information or services without the need to install contributed modules.Another alternative is to push content into Drupal using an ingestion service, which allows you to obtain and import data into the CMS. This is an extremely useful way to control what content you end up with.Of course, it is possible to utilize both push and pull methods. Either way, try to automate as much of the process as possible. Drupal (and in particular, Drupal 8) is a powerful ingestion engine -- it knows how to do the work for you.
Why Media Organizations Love Drupal
Media organizations -- like Time Inc., Thomson Reuters, and Turner Broadcasting -- need a platform capable of handling hundreds of thousands of media, news stories, and content produced around the world. Drupal, with its careful balance of automation and editor control, is an effective tool for providing the right combination of power and customization. Drupal 8 makes this even easier.Drupal works well with content syndication tools like MediaConnect and Outbrain to receive and process thousands of assets, creating a natural flow of content for editors to review, curate, and publish quickly. This saves editors from having to go looking for content manually; instead, they have it at their fingertips.Most media organizations have more than one output stream; they publish multiple websites targeting different demographics, promote content on social media platforms, and even get some content printed (yes - on paper!). Automated tagging systems allows Drupal to do more than simply aggregate information, but organize and categorize it. What’s more, Drupal 8’s omni-channel capabilities enable organizations to create a unified experience across all their touchpoints.
Learn more about content aggregators and other kinds of solutions in our white paper, Drupal 8 Architecture Solutions: Architecture Options Explained for Business Stakeholders.