Ooyala Customers

… and

• Data sync with Ooyala Backlot
• APIs that work at scale
  • Thousands of movies
  • Tens of Thousands of users
  • Support website and applications

Oh, right, 2013...

So now what?

1. Drupal 7 with Services
2. Drupal 7 with RestWs
3. Symfony
4. Silex

Why choose?

Drupal 7

Pro: CMS and page display

Con: Mediocre at REST

Silex

Pro: HTTP handling

Con: Hand-rolled artisinal UI

Communication?

• Drupal data is Drupal's
• Editorial structure != API structure

Answer

Major content

• Program
• Asset
• Offer
• Collections
• Various app-specific content

<featureexport>
  <header>
    <exhibitionwindow start="2013-03-12T13:00:00.0Z" end="2014-07-30T13:00:00.0Z">
    <destinations>
      <destination destinationid="svod" deviceid="STBmanaged">
    </destination></destinations>
  </exhibitionwindow></header>
  <feature>
    <description>
      <title>The Dark Night</title>
      <sorttitle>
      <shortsynopsis>When Batman, Gordon and Harvey Dent...</shortsynopsis>
      <genre sub="1" main="4">Movie:Action/Adventure</genre>
      <production>
        <credits><credit role="Actor"><person>Christian Bale</person></credit></credits>
      </production>
    </sorttitle></description>
  </feature>
  <media>
    <videos>
      <video class="feature">
        <duration>PT152M0S</duration>
        <files base="">
          <file filename="ON600007.gxf" assetid="ON600007">
        </file></files>
      </video>
    </videos>
    <images>
      <imagesource base="">
        <img filename="the_dark_knight.jpg" imageid="I@023072">
      </imagesource>
    </images>
  </media>
</featureexport>

Importing

• Migrate
• Feeds
• Services
• Custom

Importing

HTTP

• Cheat: POST-only, no REST
• 3 page callbacks, common code
• Vanilla Drupal
• Http Basic (over SSL) (simplehttpauth)

One more thing…

• Guzzle
• Guzzle lib for Rotten Tomatoes
• Rotten Tomatoes module
• Map nodes by IMDB ID
• Refetch periodically

Content index

Editorial content

Program editing

Program editing

Program editing

Program editing

Program editing

Program editing

Export to ElasticSearch

• Lots of preprocessing needed
• Existing contribs weak (2013)
• Rules has too many moving parts
• Exporting some nodes requires others

Another mini-custom OOP system!

When?

• Published == Public
• Public == In Elasticsearch
• Published == In Elasticsearch

So when should it be public?

Publication rules

A Program is publishable when:

• It is curatorially approved

Actually it's a bit more complex than that

Publication rules

An Offer is publishable when:

• It is curatorially approved
• … and the Offer is within its Publication window
• … or it's about to be

Actually it's a bit more complex than that

Publication rules

An Asset is publishable when:

• It is curatorially approved
• … and it has an Offer that is approved
• … or the Offer is within its Publication window
• … or it's about to be

Actually it's a bit more complex than that

Publication rules

It's complicated…

…And potentially expensive

Cron & Queues

• Lightweight microframework
• Same Kernel/Routing as Symfony (and Drupal 8)
• Bare-bones, add what you need
  • Elastica (Elasticsearch)
  • Guzzle (talk back to Ooyala)
  • Nocarrier/Hal (the API format)

• Hypertext Application Language
• IETF Draft
• JSON and XML (but who uses the XML version?)

Silex overview

The HAL Browser

Program resource

Person resource

High availability?

• Silex is stateless: Spin up several, load balance
• Elasticsearch clusters easily
• Varnish caching = FAST!

And growing

• Highly reliable (No? downtime)
• Library of thousands of assets
• Thousands of subscribers
• New features added regularly; architecture held up