API Infrastructure Evolution

By Evan Broder and Nelson Elhage @ API Strategy & Practice Conference
San Francisco, October 23-24-25, 2013

Transcript

1. API INFRASTRUCTURE EVOLUTION EVAN BRODER @ebroder NELSON ELHAGE @nelhage
2. WHY INFRA? KEEPS US UP
3. VERSION 1.0
5. WHAT GOES WRONG?
9. LOOK FOR PRECEDENT
11. Routing Presentation Logic Storage MySQL Tweet Store Flock Redis Memcached Cache TFE Monorail Tweet Service User Service Timeline Service SocialGraph Service DirectMessa ge Service User Store API Web Search Feature-X Feature-Y HTTP THRIFT THRIFT*
12. WHY SOA LIMITS LOCALIZED COMPLEXITY STRONGER ABSTRACTIONS / LOOSER COUPLING REDUCED SCOPE OF COORDINATION ISOLATED FAILURES
13. WHY NOT SOA MAKES BROAD CHANGES HARDER LOTS OF CENTRALIZED CODE INFRA HIGH TRANSITION COSTS
14. APP
15. www api
16. www api
17. www api
18. app1 app2 app3 api
19. HOORAY! WE ARE NOW SERVICE ORIENTED (ISH)
20. SOLVE THE PROBLEM YOU HAVE TODAY THINK ABOUT WHERE TO BE TOMORROW HELP THOSE TWO FEED OFF EACH OTHER