Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
How and Why 
To Dogfood 
Your API 
Open path to innovation and 
growth
“Pay close attention to the APIs - 
That’s all that really matters.” - Feb 
1st , 2007
“Faster… Launch is tomorrow” 
- Feb 2nd , 2007 
• “They’re using SharePoint…” (and then others) 
• “This customer has 1,00...
1. All teams expose data and functionality via 
interfaces. 
2. Teams must only communicate via these 
interfaces. 
3. The...
Let’s throw some big words… 
1. Interoperability 
2. Flexibility and Innovation 
3. Cost-Efficiency 
4. Automation of Proc...
Sign up 
Review with 
Bus.Dev 
Wait for 
decision 
Sign Legal 
Agreements 
Pay 
Get API 
Access 
Start 
Building 
It’s 201...
Open API 
Sign up 
Start 
Building
Make Your API, Your Core
Evolve. Never Break. 
• Versioning 
• Naming Conventions 
• Consistent Behavior
Simple. Accessible. 
• Standards, 
don’t be afraid to break {:reinvent} them. 
• Workflows, 
build atomic APIs, then multi...
What’s Next? 
• University, 
personalized & structured learning, certifications. 
• BPaaS, 
creating workflows without wri...
What you already knew… 
• Be a platform. API first, then apps. 
• No backdoors, be your own first customer. 
• Distributed...
Zohar Babin, Sr. Director of Ecosystem, Kaltura 
Zohar.Babin@Kaltura.com 
@zohar 
NEW YORK . SAN FRANCISCO . LONDON . TEL-...
Upcoming SlideShare
Loading in …5
×

How and Why to Dogfood Your API - Kaltura Video Platform - ProgrammableWeb APIConUK 2014

1,007 views

Published on

How and Why To Dogfood Your API
While a great many API enthusiasts will tell you that achieving API utopia means re-architecting all of your applications (Web, mobile, or otherwise) on top of the same APIs that you make available to external developers, very few organizations have actually succeeded at doing what's necessary; turning their infrastructures inside out. Many organizations can't envision having the time, patience, or resources to fly a plane while the wings are being ripped-off and reinstalled. But open source video platform provider Kaltura pulled it off. As a result, Kaltura's core infrastructure -- back end servers, core applications, etc. --- rely on the same APIs that front-facing partners' applications rely on. The result was a highly flexible future-proof platform that enables customers, partners, developers and startups to rapidly extend the platform with innovative implementations that continuously push the limits of what Kaltura can do. In this presentation, Kaltura willl cover the principles of what makes a great, dogfoodable API, how to make it resilient, future-proof and yet backward compatible, and most importantly how to enable and support customers and partners looking to extend an API platform.

- See more at: http://www.apiconuk.com/apiconukspeakerdetail?id=babin

Published in: Technology
  • Be the first to comment

  • Be the first to like this

How and Why to Dogfood Your API - Kaltura Video Platform - ProgrammableWeb APIConUK 2014

  1. 1. How and Why To Dogfood Your API Open path to innovation and growth
  2. 2. “Pay close attention to the APIs - That’s all that really matters.” - Feb 1st , 2007
  3. 3. “Faster… Launch is tomorrow” - Feb 2nd , 2007 • “They’re using SharePoint…” (and then others) • “This customer has 1,000 editors in 23 countries, and 100,000 shops, each requires different editions of the video, but all changes are to be approved by 20 people.”
  4. 4. 1. All teams expose data and functionality via interfaces. 2. Teams must only communicate via these interfaces. 3. There will be no other form of communication allowed. 4. It doesn’t matter what technology is used. 5. All service interfaces, without exception, must be designed from the ground up to be externalizable. 6. Anyone who doesn’t do this will be fired.
  5. 5. Let’s throw some big words… 1. Interoperability 2. Flexibility and Innovation 3. Cost-Efficiency 4. Automation of Processes 5. Accessible Functionality 6. Delegation of Work 7. Democratizing of Data 8. Marketplace
  6. 6. Sign up Review with Bus.Dev Wait for decision Sign Legal Agreements Pay Get API Access Start Building It’s 2014 (end of almost)… and many APIs are still like that =
  7. 7. Open API Sign up Start Building
  8. 8. Make Your API, Your Core
  9. 9. Evolve. Never Break. • Versioning • Naming Conventions • Consistent Behavior
  10. 10. Simple. Accessible. • Standards, don’t be afraid to break {:reinvent} them. • Workflows, build atomic APIs, then multirequest. • Caching, make it work seamlessly. • Be mindful, don’t assume people read, or even want to.
  11. 11. What’s Next? • University, personalized & structured learning, certifications. • BPaaS, creating workflows without writing code. • Adaptive and proactive docs, distributing new best practices safely & timely. • Faster, personalized on-boarding, your own personalized cloud consultant.
  12. 12. What you already knew… • Be a platform. API first, then apps. • No backdoors, be your own first customer. • Distributed scale – design your core with APIs. • Nobody cares – make it seamless. • Nobody reads – make it literal. • Remove all barriers for participation. • Use atomic APIs, automate with multirequest. • Use the right technology for the situation/user, don’t be afraid to reinvent standards.
  13. 13. Zohar Babin, Sr. Director of Ecosystem, Kaltura Zohar.Babin@Kaltura.com @zohar NEW YORK . SAN FRANCISCO . LONDON . TEL-AVIV . SINGAPORE . SAO PAULO

×