CAPE - Create Anywhere, Publish Everywhere

by Irakli Nadareishvili @ Apistrat NYC (Feb. 2013)

Transcript

1. NPR API Irakli Nadareishvili Director of Engineering, Digital Media, @NPR Twitter: @inadarei @NPRTechTeam
2. Create Once, Publish Everywhere • • • • http://bit.ly/capeapi
3. Today: No Single CMS http://bit.ly/capeapi
4. http://bit.ly/capeapi
5. Create Anywhere, Publish Everywhere • • • • • • • • http://bit.ly/capeapi
6. Everything Is an API à la Jeff Bezos + Amazon. Do not create access dualities. All features and content must be accessible through an API. http://bit.ly/capeapi
7. Speed Is a Feature Faster the API, the more it gets used. Lowering response time is exponentially hard. http://bit.ly/capeapi
8. API: Search Index For a distributed publishing system, API is the content integration point, not: the database of record or federated content. Search engine is a great backend for such APIs. http://bit.ly/capeapi
9. Granular Security Publishers need control on a single content item level. Sometimes: even on the level of assets of a content item. http://bit.ly/capeapi
10. Design for users Forget what they taught you in CS classes. UML is for Suits. APIs should be designed around real-world queries. http://bit.ly/capeapi
11. Create Anywhere, Publish Everywhere • • • • • • • • http://bit.ly/capeapi
12. http://bit.ly/capeapi