Web APIs: The Past, The Present and The Future

Df5ef40f1ad5eb98550b41f00f08eaa9?s=47 Almad
March 29, 2019

Web APIs: The Past, The Present and The Future

Df5ef40f1ad5eb98550b41f00f08eaa9?s=128

Almad

March 29, 2019
Tweet

Transcript

  1. Web APIs: The Past, The Present and The Future Lukáš

    Linhart
  2. work@almad.net
 @almadcz
 http://www.almad.net

  3. 470.000 APIs 5M+ Consumers 350.000 Developers Apiary CTO @

  4. Web APIs (exchange of machine-readable, structured data where client has

    semantic understanding of the domain)
  5. Web ~= HTTP

  6. The Past-ish

  7. structured; data; definition; RO

  8. None
  9. None
  10. What went wrong? • “text” originally just ASCII • POST

    tunneling • Simplistic
  11. None
  12. None
  13. What went wrong? • (in the enterprise world) Nothing!!!!!!!1111!111 •

    POST tunneling • Way too complex • Sharing domain dictionaries across organisations
  14. None
  15. None
  16. What went wrong? • Easy to be done wrong •

    Tooling fragmentation • Be An Architect For This Simple Endpoint™
  17. None
  18. None
  19. AJAX/AJAJ (SPAs are API clients too!)

  20. The Present (based on personal perception)

  21. None
  22. The Rise of HTTP Contracts Swagger/OAS3, API Blueprint

  23. The Fall of HATEOAS Tooling is not here. Not enough

    benefits in affordances vs fixed (URL) contracts
  24. RPC reborn GraphQL & gRPC/protobuf rising

  25. None
  26. Client Has The Power GraphQL, cURL, “old” REST

  27. Return of the Binary HTTP/2-3, ProtoBuf, 0101s are less frowned

    upon
  28. Real-Time Rising Protocol winner unclear

  29. None
  30. The Future (Questions)

  31. Client generalisation Will we break out of domain-specific clients?

  32. Shared semantic/ domain model It (almost always) failed. Will we

    succeed?
  33. IoT pressure Scaling clients that can’t break, on low-power devices.

    Autonomy?
  34. ML usefullness Will ML be usable for protocol programming?

  35. Internal & External API unification Currently rarely same because of

    different contracts
  36. @almadcz http://www.almad.net Thank You @apiaryio https://apiary.io/

  37. Credits Closed eyes seagull: Photo Credit: <a href="https://www.flickr.com/photos/45409431@N00/4721821857/">marfis75</a> Flickr via

    <a href="http://compfight.com">Compfight</a> <a href="https://creativecommons.org/licenses/by-sa/ 2.0/">cc</a> Disaster Girl by Dave Roth, January 2004, CC BY-NC https://www.flickr.com/photos/travelingroths/2518727675/ Preacher: Photo Credit: <a href="https://www.flickr.com/photos/23596866@N04/37454762056/">redroofmontreal</a> Flickr via <a href="http://compfight.com">Compfight</a> <a href="https://creativecommons.org/licenses/by-nd/ 2.0/">cc</a> tester: Photo Credit: <a href="https://www.flickr.com/photos/136629440@N06/25798318315/">wocintechchat.com</a> Flickr via <a href="http://compfight.com">Compfight</a> <a href="https://creativecommons.org/licenses/by/2.0/">cc</a> devil: Photo Credit: <a href="https://www.flickr.com/photos/39715972@N00/34165937904/">H.KoPP</a> Flickr via <a href="http://compfight.com">Compfight</a> <a href="https://creativecommons.org/licenses/by-people in front of whiteboard: Photo Credit: <a href="https://www.flickr.com/photos/27647890@N03/26793116311/">strudelt</a> Flickr via <a href="http://compfight.com">Compfight</a> <a href="https://creativecommons.org/licenses/by/2.0/">cc</a> CommitStrip: https://www.commitstrip.com/en/2018/11/15/http-3/