The Anatomy of API ContentDistributionJosep M. Pujoljosep@3scale.net | @solso
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
Decoupling Logic from Control           Content            Control             Logic             Layer           Delivery
Decoupling Logic from Control     Logic             Control     Layer              Layer
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              ...
Content comes from everywhere... Jane     on browser Aggregator #1      via API RS #1            via API Joe              ...
Content comes from everywhere... Jane     on browser Aggregator #1      via API RS #1            via API Joe              ...
Content comes from everywhere... Jane     on browser Aggregator #1      via API RS #1            via API Joe              ...
...so you need control everywhere
...so you need control everywhereControl          API Layer
...so you need control everywhereControl          API Layer
...so you need control everywhereControl          API Layer
...so you need control everywhereControl          API Layer
Conclusions              “Power is nothing without control”, and              flexibility is key to achieve it
Upcoming SlideShare
Loading in …5
×

Anatomy of API Content Distribution

1,678 views

Published on

This presentation tackles new ways of distributing content that Application Programming Interfaces at the heart of distribution strategy
and show how APIs are set to become the primary channel for companies seeking to reach partners and users. The keynote covers technical scenarios and architectures as well customer examples.

Published in: Technology
0 Comments
4 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,678
On SlideShare
0
From Embeds
0
Number of Embeds
24
Actions
Shares
0
Downloads
24
Comments
0
Likes
4
Embeds 0
No embeds

No notes for slide
  • This talk will tackle new ways of distributing content that Application Programming Interfaces at the heart of distribution strategyand show how APIs are set to become the primary channel for companies seeking to reach partners and users. The talkwill cover technical scenarios and architectures as well customer examples.
  • This is what content used to look likeA finished product made of a solid piece delivered to for a single purpose
  • This is what content looks and will look like todayA product made of the aggregation of pieces that serves multiple purposesA bit freaky, no question, but way more modular
  • This is what content looks and will look like todayA product made of the aggregation of pieces that serves multiple purposesA bit freaky, no question, but way more modular
  • Anatomy of API Content Distribution

    1. 1. The Anatomy of API ContentDistributionJosep M. Pujoljosep@3scale.net | @solso
    2. 2. What Content used to be
    3. 3. What Content has become
    4. 4. What Content has become
    5. 5. The Content Onion
    6. 6. The Content Onion
    7. 7. The Content Onion
    8. 8. The Content Onion
    9. 9. The Content Onion API’s
    10. 10. Delivery needs Orchestration
    11. 11. Basics Requirements Access Control Traceabilty Analytics
    12. 12. Decoupling Logic from Control Content Control Logic Layer Delivery
    13. 13. Decoupling Logic from Control Logic Control Layer Layer
    14. 14. Decoupling Logic from Control• A more elegant design pattern: – Abstraction – Reutilization – Flexibility
    15. 15. Decoupling Logic from Control• A more elegant design pattern: – Abstraction – Reutilization –Flexibility
    16. 16. Decoupling Logic from Control• A more elegant design pattern: – Abstraction – Reutilization –Flexibility!
    17. 17. Content comes from everywhere...
    18. 18. Content comes from everywhere... Jane on browser
    19. 19. Content comes from everywhere... Jane on browser Aggregator #1 via API
    20. 20. Content comes from everywhere... Jane on browser Aggregator #1 via API RS #1 via API
    21. 21. 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
    22. 22. 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
    23. 23. 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
    24. 24. 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
    25. 25. ...so you need control everywhere
    26. 26. ...so you need control everywhereControl API Layer
    27. 27. ...so you need control everywhereControl API Layer
    28. 28. ...so you need control everywhereControl API Layer
    29. 29. ...so you need control everywhereControl API Layer
    30. 30. Conclusions “Power is nothing without control”, and flexibility is key to achieve it

    ×