APIs from the Trenches - FOWA 2014

@hpoom APIs FROM THE TRENCHES By Simon Wood 1 FOWA
London 2014

a @hpoom Technology Director for Shortbreaks Holiday Extras Simon Wood
2 @hpoom About Me

b @hpoom 3 Holiday Extras

b @hpoom 4 @hpoom miDrive

b @hpoom Our Mission 5 Consumer Debugging Author Debugging Considerations

@hpoom j Consumer Deibugging 6

@hpoom m Selection 7

@hpoom f Discovery 8

@hpoom f Micro Services 9

@hpoom f Abstraction 10

@hpoom f Version Monitoring 11

b @hpoom API Changelog 12 bit.ly/apiChange

b @hpoom API Changelog 13

@hpoom m Network 14

@hpoom f Connection 15

b @hpoom Connection 16 bit.ly/DiagNet

@hpoom f Auth 17

@hpoom e Auth 18 Use a Library

@hpoom e Auth Test in Isolation 19

b @hpoom Token Gen 20 bit.ly/TokenGen

b @hpoom Token Gen 21 bit.ly/TokenGen

@hpoom f Direct API Calls 22

@hpoom e Why Direct Calls? 23 Quick

@hpoom e Why Direct Calls? Scope 24

@hpoom h Direct API calls 25

@hpoom h Direct API calls 25 Browser

@hpoom h Direct API calls 25 Browser cURL

@hpoom h Direct API calls 25 Browser cURL Postman

b @hpoom Postman 26

b @hpoom Postman 27

@hpoom m Payload 28

@hpoom f Mock API 29

” @hpoom p “Developing an application and an API in
parallel can be quite the tricky task” Ryan Able bit.ly/FakeAPI 30

@hpoom e Why Mock? Schema 31

@hpoom e Why Mock? Change 32

@hpoom e Why Mock? Rate Limits 33

@hpoom e Why Mock? Efficiency 34

@hpoom h Mock API 35

@hpoom h Mock API 35 Mockable mockable.io

@hpoom h Mock API 35 Apiary apiary.io Mockable mockable.io

@hpoom h Mock API 35 Mocky mocky.io Apiary apiary.io Mockable
mockable.io

b @hpoom Mocky 36

@hpoom f 37 Fake API

@hpoom e Why Fake? Offline 38

@hpoom e Why Fake? Security 39

@hpoom e Why Fake? Dynamic 40

@hpoom h Fake API 41 dyson webpro/dyson JSON Server typicode/json-server
Interfake basicallydan/interfake

b @hpoom 42 Interfake npm install interfake --save var Interfake
= require('interfake'); var interfake = new Interfake(); interfake.get('/whats-next').body({ next : 'more stuff '}); interfake.listen(3000); // Listen on port 3000 { "next":"more stuff" } Install Code http://localhost:3000/whats-next

@hpoom f Proxy 43

@hpoom e Why Proxy? Snoop 44

@hpoom e Why Proxy? Replay 45

@hpoom e Why Proxy? 46 Tunnel

@hpoom h Proxies 47

@hpoom h Proxies 47 Wiretap

@hpoom h Proxies 47 Runscope Wiretap

@hpoom h Proxies 47 Ngrok Runscope Wiretap

@hpoom f Turn Off Cache 48

@hpoom j Author Deibugging 49

@hpoom m Logging 50

@hpoom e Why Logging? 51 Audit Trail

@hpoom e Why Logging? 52 Pinpoint

@hpoom e Why Logging? Analysis 53

@hpoom f Cloud Logging 54

@hpoom h Cloud Logging 55

@hpoom h Cloud Logging 55 Sumo Logic

@hpoom h Cloud Logging 55 Sumo Logic Logstash

@hpoom h Cloud Logging 55 Sumo Logic Loggly Logstash

b @hpoom 56 Loggly

b @hpoom 57 Loggly

b @hpoom 58 Loggly

@hpoom m Error Reporting 59

@hpoom e Why Error Reporting? 60 Exceptions

@hpoom h Error Reporting 61

@hpoom h Error Reporting 61 Bugsnag

@hpoom h Error Reporting 61 Bugsnag Airbreak

@hpoom h Error Reporting 61 Bugsnag Sentry Airbreak

b @hpoom 62 Sentry

b @hpoom 63 Sentry

@hpoom m Monitoring 64

@hpoom h Monitor 65

@hpoom h Monitor 65 Zapier

@hpoom h Monitor 65 Runscope Zapier

@hpoom h Monitor 65 Runscope Zapier Ducksboard

@hpoom m Load Testing 66

@hpoom h Load Testing 67

@hpoom h Load Testing 67 Siege

@hpoom h Load Testing 67 Loader.io Siege

@hpoom h Load Testing 67 wrk Loader.io Siege

b @hpoom 68 wrk wrk -t12 -c400 -d30s http://127.0.0.1:8080/index.html Running
30s test @ http://127.0.0.1:8080/index.html 12 threads and 400 connections Thread Stats Avg Stdev Max +/- Stdev Latency 635.91us 0.89ms 12.92ms 93.69% Req/Sec 56.20k 8.07k 62.00k 86.54% 22464657 requests in 30.00s, 17.76GB read Requests/sec: 748868.53 Transfer/sec: 606.33MB Basic Example Output

@hpoom j 69 Author Considerations

@hpoom m Docs 70

@hpoom h Swagger RAML API Blueprint API Design 71

b @hpoom 72 API Design bit.ly/designApi

@hpoom m SDKs 73

@hpoom j 74 Human Help

@hpoom j FOLLOW 75 @kinlane @johnsheehan @synedra

” @hpoom p Kin Lane bit.ly/trenchesOfAPI “API design is often
done in the trenches of API operations, iterating and perfecting as an API initiative evolves.” 76

@hpoom Thank you please contact me if you have any
questions Twitter: @hpoom Links: http://bit.ly/ApiTrenches logo 77 By Simon Wood FOWA London 2014 join.holidayextras.co.uk

APIs from the Trenches - FOWA 2014

APIs from the Trenches - FOWA 2014

More Decks by Simon Wood

Other Decks in Technology

Featured

Transcript