MULTISITECONTENT DEPLOYMENT

DICK OLSSON TWITTER: @dickolsson

Challenges for media organizations

Content deployment scenarios

A solution

Demo

AGENDA

Dick Olsson

dixon_ on drupal.org

@dickolsson on Twitter

Drupal contributor

Working at Pfizer Inc.

WHO AM I?

Developer at NodeOneBig media clients

around Scandinavia

Lead Drupal Developer atAl Jazeera Media Network

Live bloggingNews

Programmes

MY PAST

CHALLENGES

FOR MEDIA

Publishing companies often runmany different sites

Managing content across all sitesbecomes complex

Complexity slows you down

BIG PORTFOLIO

Organizations work differently with content

Content should be shared across properties and channels

Content needs be stored carefully

CONTENT IS KING

Time to market is crucial

Agility is key

...applies to both youreditorial and engineering teams

FAST MOVING

How to build a content platform that encourage agility and flexibility?

How to cater for different workflows?

How to move content between systems?

CHALLENGES

CONTENT DEPLOYMENT

SCENARIOS

SIMPLE WORKFLOW

ProdStage

MERGE WORKFLOW

Stage

Edit 1

Edit 2

Edit 3

Prod

HUB/SPOKE WORKFLOW

Editorial BD

A

C

NETWORK MODEL

BD

A

C

Content staging

Content sharing

Replication

Syndication

IT'S SORT OF...

WHAT DO WE WANT

FROM A SOLUTION?

Loosely coupled system

Freedom in choosing workflows

Freedom in choosing apps and tools

WHAT WE WANTON A HIGH LEVEL

MEDIA ORGANIZATIONS

??

Revisions everywhere

Bi-directional replication

Conflict detection

REST API

WHAT WE WANTON A TECH LEVEL

A SOLUTION

“We are working to expand the definition and specification to encompass the

growing family of applications that support HTTP-based, multi-master

replication.”

www.replication.io

HTTP API and replication protocolfrom CouchDB

Revision and conflict modelis inspired by Git

THE PROTOCOL

Drupal

CouchDB

Angular / PouchDB

Hood.ie

(or other systems using the protocol)

REUSABLE PROTOCOL

Contrib:

Multiversion

Relaxed Web Services

Core:

Serialization

Restful Web Services

DRUPAL 8

Provides revision supportfor all content entities

Tracks entity revisions like Git

Delete operation creates new revisions

multiversion.module

Provides a RESTful JSON API

Endpoints for entities, comparing revisions, starting/stopping replications etc.

Drush plugin for running replications

relaxed.module

Revisions everywhere

Bi-directional replication

Conflict detection

REST API

Multiversion + Relaxed= replication.io

DEMO

Flexible workflows for any organizational needs

Freedom in choosing tools

Loosely coupled systemsdecreases time to market

CONCLUSIONS

THANK YOU!QUESTIONS?

DICK OLSSON TWITTER: @dickolsson