What Content used to be
What Content has become
What Content has become
The Content Onion
The Content Onion
The Content Onion
The Content Onion
The Content Onion
API’s
Delivery needs Orchestration
Basics Requirements
Access Control
Traceabilty
Analytics
Control Layer
Decoupling Logic from Control
LogicLayer
Content Delivery
Control Layer
Decoupling Logic from Control
LogicLayer
Decoupling Logic from Control
• A more elegant design pattern:– Abstraction– Reutilization– Flexibility
Decoupling Logic from Control
• A more elegant design pattern:– Abstraction– Reutilization
–Flexibility
Decoupling Logic from Control
• A more elegant design pattern:– Abstraction– Reutilization
–Flexibility!
Content comes from everywhere...
Content comes from everywhere...
Jane on browser
Content comes from everywhere...
Jane on browser
Aggregator #1 via API
Content comes from everywhere...
Jane on browser
Aggregator #1 via API
RS #1 via API
Content comes from everywhere...
Jane on browser
Aggregator #1 via API
RS #1 via API
Joe on TV found by an app combining data from the Aggregator app #1 and the recommendations of RS #1
Content comes from everywhere...
Jane on browser
Aggregator #1 via API
RS #1 via API
Joe on TV found by an app combining data from the Aggregator app #1 and the recommendations of RS #1
Content comes from everywhere...
Jane on browser
Aggregator #1 via API
RS #1 via API
Joe on TV found by an app combining data from the Aggregator app #1 and the recommendations of RS #1
Content comes from everywhere...
Jane on browser
Aggregator #1 via API
RS #1 via API
Joe on TV found by an app combining data from the Aggregator app #1 and the recommendations of RS #1
...so you need control everywhere
...so you need control everywhere
Control Layer
API
...so you need control everywhere
Control Layer
API
...so you need control everywhere
Control Layer
API
...so you need control everywhere
Control Layer
API
Conclusions
“Power is nothing without control”, and flexibility is key to achieve it
Recommended
