multisite content deployments for media organizations
TRANSCRIPT
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
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
Loosely coupled system
Freedom in choosing workflows
Freedom in choosing apps and tools
WHAT WE WANTON A HIGH LEVEL
Revisions everywhere
Bi-directional replication
Conflict detection
REST API
WHAT WE WANTON A TECH LEVEL
“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
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
Flexible workflows for any organizational needs
Freedom in choosing tools
Loosely coupled systemsdecreases time to market
CONCLUSIONS