LF_APIStrat17_API Design in the Age of Bots, IoT, and Voice
•
0 likes•63 views
"Developers have been debating RPC vs. REST for some time, and now we have GraphQL and other options growing in popularity. But what happens to our API design when we add bots, edge devices, and voice into the mix? This talk examines how our APIs must change in the world of bots, voice, and edge devices. We'll also look at ways that we can future-proof our API design in light of these new ways of interaction. Finally, we'll identify design strategies to support the growing need for edge computing."
Recommended
Recommended
More Related Content
What's hot
Similar to LF_APIStrat17_API Design in the Age of Bots, IoT, and Voice
Similar to LF_APIStrat17_API Design in the Age of Bots, IoT, and Voice (20)
More from LF_APIStrat
More from LF_APIStrat (20)
Recently uploaded
Recently uploaded (20)
LF_APIStrat17_API Design in the Age of Bots, IoT, and Voice
- 1. API Design in the Age of Bots, IoT, and Voice James Higginbotham @launchany https://apideveloperweekly.com
- 2. The Road So Far… 1990s Distributed Object Integration 2000s Corp-to-Corp Integration 2010s + Mobile/Data Integration
- 3. The State of API Design in 2017
- 4. APIs are stuck in the land of CRUD
- 5. API Conversations with CRUD
- 6. API Design is an architectural concern that combines business, product design, and technology
- 9. 1. Hypermedia and HATEOAS (again)
- 10. Choose Your Own Adventure for APIs
- 11. When APIs Meet Jobs-To-Be-Done { … "_links": { “self": {"href": "/approval-requests/d796f2d0eb72492bb088"}, “approve": {"href": "/approval-requests/d796f2d0eb72492bb088/approve"}, “decline": {"href": "/approval-requests/d796f2d0eb72492bb088/decline"}, }, … }
- 15. 1_Blank
- 16. IoT
- 18. 3. User-First, Capability-Driven API Design
- 19. Visual Voice
- 20. GET https://api.myexample.com/projects Accept: application/json;q=0.5,text/html;q=1.0 4. Content Negotiation For Visualization HTTP/1.0 200 OK Date: Tue, 16 June 2015 06:57:43 GMT Content-Type: text/html <html>…</html>
- 21. Sessions and Context-Based Interaction
- 22. 5. Front-End APIs for Context u Map APIs to devices and manages interactive sessions u Ask for additional details before calling backend APIs u Adaptive to support optional context data (min, typical, max data input) { … "_links": { “self": {"href": "/sessions/d796f2d0eb72492"}, “accounts": {"href": "/ sessions/d796f2d0eb72492/accounts"}, “credit-lines": {"href": "/approval-requests/d796f2d0eb72492/credit-lines"}, }, … }
- 24. Edge Computing with NAS
- 25. AWS Snowball Edge + AWS Greengrass
- 26. 6. On-Device APIs u One interface, multiple implementations u Store-and-forward strategy with synchronization when offline u Local API gateway and management u Monitoring and managing edge nodes goes beyond the data center
- 27. Bots
- 29. 7. Bots as Next Generation APIs u Currently, the assumption is that bots are talking to humans u But, what if our apps could talk to bots as if it were an API? u What if natural language is better for some APIs? u What if a hybrid language is necessary to support next gen API integration?
- 30. API Design Is Changing 1. Hypermedia and HATEOAS 2. Event subscriptions 3. Capability-driven API design 4. Content negotiation 5. Front-end context APIs 6. On-device APIs 7. Bots as next generation APIs
- 31. The Road Ahead 1990s Distributed Object Integration 2000s Corp-to-Corp Integration 2010s + Mobile/Data Integration 2020s ? Capability Integration