API First (ZendCon 2013)

Slide 1

Slide 1 text

API First Ben Ramsey

Slide 2

Slide 2 text

No content

Slide 3

Slide 3 text

No content

Slide 4

Slide 4 text

6 billion mobile subscriptions globally

Slide 5

Slide 5 text

6 BILLION!!!

Slide 6

Slide 6 text

No content

Slide 7

Slide 7 text

No content

Slide 8

Slide 8 text

Website MVC Templates Static Assets Database

Slide 9

Slide 9 text

6 BILLION!!!

Slide 10

Slide 10 text

Website & Mobile MVC Templates Static Assets Database Mobile Templates Separate Mobile MVC Templates Static Assets Database Website & Mobile MVC Templates Static Assets Database Mobile Templates Mobi MVC

Slide 11

Slide 11 text

Mobile MVC Templates Static Assets Website MVC Templates Static Assets Database

Slide 12

Slide 12 text

No content

Slide 13

Slide 13 text

Mobile MVC Templates Static Assets Website MVC Templates Static Assets Database Native App API Native App

Slide 14

Slide 14 text

No content

Slide 15

Slide 15 text

Mobile MVC Templates Static Assets Website MVC Templates Static Assets Database Native App API Native App

Slide 16

Slide 16 text

Mobile MVC Templates Static Assets Website MVC Templates Static Assets Database Native App API Native App

Slide 17

Slide 17 text

Mobile MVC Templates Static Assets Website MVC Templates Static Assets Database Native App API Native App

Slide 18

Slide 18 text

Mobile MVC Templates Static Assets Website MVC Templates Static Assets Database Native App API Native App

Slide 19

Slide 19 text

No content

Slide 20

Slide 20 text

“A big ball of mud is haphazardly structured, sprawling, sloppy, duct-tape and bailing wire, spaghetti code jungle. We’ve all seen them. These systems show unmistakable signs of unregulated growth, and repeated, expedient repair. Information is shared promiscuously among distant elements of the system, often to the point where nearly all the important information becomes global or duplicated. The overall structure of the system may never have been well deﬁned. If it was, it may have eroded beyond recognition.” — Brian Foote and Joseph Yoder, laputan.org/mud

Slide 21

Slide 21 text

Start with the API ﬁrst

Slide 22

Slide 22 text

Mobile MVC Templates Static Assets Website MVC Templates Static Assets Database Native App API Native App

Slide 23

Slide 23 text

Start with the API ﬁrst

Slide 24

Slide 24 text

1. Separation of concerns

Slide 25

Slide 25 text

API Layer UI 1 UI 2 UI 3

Slide 26

Slide 26 text

2. Scalable

Slide 27

Slide 27 text

2a. Team

Slide 28

Slide 28 text

2b. Product

Slide 29

Slide 29 text

2c. Business

Slide 30

Slide 30 text

2d. Technology

Slide 31

Slide 31 text

API Layer UI 1 UI 2 UI 3 Users Assets Products Trx

Slide 32

Slide 32 text

3. Extensible

Slide 33

Slide 33 text

4. Seamless

Slide 34

Slide 34 text

5. Evolvable

Slide 35

Slide 35 text

SOLID

Slide 36

Slide 36 text

1. Single responsibility

Slide 37

Slide 37 text

2. Open/closed

Slide 38

Slide 38 text

3. Liskov substitution

Slide 39

Slide 39 text

Client Service 1 Service 2 Service 3

Slide 40

Slide 40 text

Client Service 1 Service 2 Service 3

Slide 41

Slide 41 text

4. Interface segregation

Slide 42

Slide 42 text

5. Dependency inversion

Slide 43

Slide 43 text

Client Service 1 Service 2 Service 3

Slide 44

Slide 44 text

Service-oriented architecture

Slide 45

Slide 45 text

Representational State Transfer (REST)

Slide 46

Slide 46 text

1. Client-server 2. Stateless 3. Cacheable 4. Layered system 5. Code on demand 6. Uniform interface

Slide 47

Slide 47 text

No content

Slide 48

Slide 48 text

API Layer Native App Website Mobile Users Assets Products Trx Database

Slide 49

Slide 49 text

What about “legacy” code?

Slide 50

Slide 50 text

Mobile MVC Templates Static Assets Website MVC Templates Static Assets Database Native App API Native App

Slide 51

Slide 51 text

Mobile MVC Templates Static Assets Website MVC Templates Static Assets Database API Layer Native App

Slide 52

Slide 52 text

Mobile MVC Templates Static Assets Website MVC Templates Static Assets Database API Layer Native App

Slide 53

Slide 53 text

But how do we “sell” it within our company?

Slide 54

Slide 54 text

1. Show how it adds value, increases throughput, and decreases time to implement change requests and new features 2. Demo a working prototype 3. Do this with a presentation 4. Tell a convincing story 5. Create a roadmap 6. Get help from a co-worker, boss, or mentor

Slide 55

Slide 55 text

Ben Ramsey benramsey.com @ramsey joind.in/9094 Thank you

Slide 56

Slide 56 text

API First Copyright © Ben Ramsey. Some rights reserved. This work is licensed under a Creative Commons Attribution-NonCommercial- NoDerivs 3.0 Unported. For uses not covered under this license, please contact the author. Ramsey, Ben. “API First.” ZendCon. Santa Clara Convention Center, Santa Clara, CA. 10 Oct. 2013. Conference Presentation.

Slide 57

Slide 57 text

Photo Credits 1. “Samsung to Launch Smart Feature Phone ‘REX Series’ in Emerging Markets” by Samsung Tomorrow, flickr.com/photos/samsungtomorrow/8475665954 2. “Danger D'Avalanche” by Peter Dutton, flickr.com/photos/joeshlabotnik/375149668 3. “Favela da Rocinha” by Scott Hadfield, flickr.com/photos/hadsie/3289716114 4. “Wrapping paper and bow” by Jonathan, flickr.com/photos/metabrilliant/4805163439