Slide 1

Slide 1 text

API First Ben Ramsey

Slide 2

Slide 2 text

No content

Slide 3

Slide 3 text

I write

Slide 4

Slide 4 text

I blog

Slide 5

Slide 5 text

I tweet @ramsey

Slide 6

Slide 6 text

No content

Slide 7

Slide 7 text

I work

Slide 8

Slide 8 text

I user group

Slide 9

Slide 9 text

I play

Slide 10

Slide 10 text

No content

Slide 11

Slide 11 text

No content

Slide 12

Slide 12 text

6 billion mobile subscriptions globally

Slide 13

Slide 13 text

6 BILLION!!!

Slide 14

Slide 14 text

No content

Slide 15

Slide 15 text

No content

Slide 16

Slide 16 text

No content

Slide 17

Slide 17 text

Website MVC Templates Static Assets Database

Slide 18

Slide 18 text

6 BILLION!!!

Slide 19

Slide 19 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 20

Slide 20 text

Mobile MVC Templates Static Assets Website MVC Templates Static Assets Database

Slide 21

Slide 21 text

No content

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

No content

Slide 24

Slide 24 text

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

Slide 25

Slide 25 text

No content

Slide 26

Slide 26 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 defined. If it was, it may have eroded beyond recognition.” — Brian Foote and Joseph Yoder, laputan.org/mud

Slide 27

Slide 27 text

Start with the API first

Slide 28

Slide 28 text

1. Separation of concerns

Slide 29

Slide 29 text

API Layer UI 1 UI 2 UI 3

Slide 30

Slide 30 text

2. Scalable

Slide 31

Slide 31 text

2a. Team

Slide 32

Slide 32 text

2b. Product

Slide 33

Slide 33 text

2c. Business

Slide 34

Slide 34 text

2d. Technology

Slide 35

Slide 35 text

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

Slide 36

Slide 36 text

3. Extensible

Slide 37

Slide 37 text

4. Seamless

Slide 38

Slide 38 text

5. Evolvable

Slide 39

Slide 39 text

SOLID

Slide 40

Slide 40 text

1. Single responsibility

Slide 41

Slide 41 text

2. Open/closed

Slide 42

Slide 42 text

3. Liskov substitution

Slide 43

Slide 43 text

Client Service 1 Service 2 Service 3

Slide 44

Slide 44 text

Client Service 1 Service 2 Service 3

Slide 45

Slide 45 text

4. Interface segregation

Slide 46

Slide 46 text

5. Dependency inversion

Slide 47

Slide 47 text

Client Service 1 Service 2 Service 3

Slide 48

Slide 48 text

Service-oriented architecture

Slide 49

Slide 49 text

Representational State Transfer (REST)

Slide 50

Slide 50 text

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

Slide 51

Slide 51 text

No content

Slide 52

Slide 52 text

API Layer Native App Website Mobile Users Assets Products Trx Database

Slide 53

Slide 53 text

What about “legacy” code?

Slide 54

Slide 54 text

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

Slide 55

Slide 55 text

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

Slide 56

Slide 56 text

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

Slide 57

Slide 57 text

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

Slide 58

Slide 58 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 59

Slide 59 text

Thank you

Slide 60

Slide 60 text

No content

Slide 61

Slide 61 text

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

Slide 62

Slide 62 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.” PHP Tek. Sheraton Chicago O’Hare Airport Hotel, Rosemont, IL. 17 May 2013. Conference Presentation.

Slide 63

Slide 63 text

Photo Credits 1. http://www.flickr.com/photos/sebastian_bergmann/286847543/ 2. http://www.flickr.com/photos/samsungtomorrow/8475665954/ 3. http://www.flickr.com/photos/statefarm/8203770426/ 4. http://www.flickr.com/photos/supersum/4949860764/