When you build a high scale media site, you always get caught in between. You want to have a distributed setup with several independent sites, but at the same time you want to be able to share content between sites, and make it easily available to your users on both apps and web. You want to be able to have external consultants deliver sub sites for you as well, without having to integrate them to your main site with all sorts of custom feeds.
Of course you want cache update within seconds of saving a node, and finally you don’t want to wait for all of your sites to be migrated from your old CMS before being able to benefit from the new awesome stuff in Drupal.

So what to do in a situation like that?

You've perhaps thought about doing a central solr service, that indexes all content from all of your sites, but that just doesn't quite cut it, when you also want to push notifications about new content to your users real time, want to invalidate your cache at the right time, and want it facing external users, but still have control over who has access to your content in a structured manner.

So why not let Drupal do, what it does great, handle the management of content, and let another service handle the event driven distribution of your content?

In the migration of tv2.dk, the website of Denmark’s largest broadcaster, from an old CMS-system to Drupal, a solution to all of these headaches was brought up.
A central API built on Node.js, Redis and Solr, that allow Drupal sites to index its content and subscribe to updates from other content providers. Thus giving a central way for content distribution to be handled.

This talk will be about the architecture of this solution and how it can be used, as it is being open source during spring 2013. We will focus on how a Drupal site integrates to this service, and what problems it will solve.