How to build a Unified API

39bb8762f3a25ebc00ebd75bc4f363af?s=47 Simon Wood
October 25, 2013

How to build a Unified API

Presentation on APIs at FOWA 2013

39bb8762f3a25ebc00ebd75bc4f363af?s=128

Simon Wood

October 25, 2013
Tweet

Transcript

  1. 3.
  2. 4.

    @hpoom Over 40m visits and 500k bookings in the last

    5 years Give £20m revenue to hotels each year
  3. 5.
  4. 6.

    Because of APIs I can tell you... Yesterday I walked

    6191 steps FitBit API The music I listen to most is Radiohead Last.fm API It is currently 13ºC in New York Yahoo Weather API The Brewery is located at lat: 51.520475 lon: -0.091471 Google Maps API @hpoom
  5. 8.

    The Future is mobile The Future is social The Future

    is cloud The Future is APIs @hpoom
  6. 10.

    What I am going to cover The Problem Solutions -

    Good and Bad Considerations Technology How you can do this too @hpoom
  7. 13.
  8. 16.
  9. 20.

    Source: Strangeloop Networks Case Study Amazon 100 milliseconds revenue 1%

    Mozilla 2.2 seconds downloads 60m per year @hpoom
  10. 29.

    Unified API Website Mobile App Affiliates Smart TV Hotels Tickets

    Transport Food Multiple consumers of data Multiple sources of data @hpoom
  11. 35.

    Website Application Layer Unified API Product API Content API Price

    & Availability Name Star Rating Facilities @hpoom
  12. 37.

    Website Application Layer Unified API Product API Content API Hotels

    Tickets Transport Legacy New Affiliate @hpoom
  13. 42.
  14. 44.

    PUBLIC SERVICE ANNOUNCEMENT @hpoom This is THE correct way to

    write numeric dates 2013-10-25 Source XKCD - http://bit.ly/iso-date
  15. 47.

    Unified API Website Mobile App Affiliates Smart TV Hotels Tickets

    Transport Food Async Total request time is only as slow as the slowest provider 1.2s 0.8s 1.1s 0.6s @hpoom
  16. 48.

    Unified API Website Mobile App Affiliates Smart TV Hotels Tickets

    Transport Food Cache Cache Cache Cache Cache If we hit the top cache respond in 0.04s @hpoom
  17. 49.

    In summary Solutions Unified API Standard Payloads Micro Services Proxy

    Cache & Async Hierarchical Problems Multi Data Sources Multi Consumers Decouple Hide Legacy Speed Scaleability @hpoom
  18. 60.
  19. 69.

    Consume your own APIs @hpoom uses to build Source Zach

    Holman - http://bit.ly/githubdogfood uses to build
  20. 70.

    @hpoom “You wouldn't really think that an online bookstore needs

    to be an extensible, programmable platform. Would you?” Steve Yegge Source Steve Yegge - http://bit.ly/yegge