Tweet
Tweet

Slide 1

Slide 1 text

paolofragomeni github.com/hij1nx co-founder of nodejitsu and the node firm twitter.com/hij1nx Saturday, September 29, 12

Slide 2

Slide 2 text

is not easy distributed thinking 1 Saturday, September 29, 12

Slide 3

Slide 3 text

2 “scale” more vertical more memory more power more cpu Saturday, September 29, 12

Slide 4

Slide 4 text

3 wtf Saturday, September 29, 12

Slide 5

Slide 5 text

4 plateau monolithic code A Saturday, September 29, 12

Slide 6

Slide 6 text

4 plateau monolithic code A B cognitive indigestion Saturday, September 29, 12

Slide 7

Slide 7 text

4 plateau monolithic code A C responsibility overload B cognitive indigestion Saturday, September 29, 12

Slide 8

Slide 8 text

4 plateau monolithic code A D individual failures become system failures C responsibility overload B cognitive indigestion Saturday, September 29, 12

Slide 9

Slide 9 text

complexity 5 quantifiable as the number of steps required to bring a system to its intended state. Saturday, September 29, 12

Slide 10

Slide 10 text

FAILURE 6 Saturday, September 29, 12

Slide 11

Slide 11 text

api endpoint img processing email processing auth 7 separation of concerns img email auth client client api Saturday, September 29, 12

Slide 12

Slide 12 text

8 tradition service oriented clients usually fail and the process ends when the endpoint is unreachable. Saturday, September 29, 12

Slide 13

Slide 13 text

a case study jitsu is a deployment tool written in javascript 9 Saturday, September 29, 12

Slide 14

Slide 14 text

another case study github is a hosting solution for git projects. wut? 10 “ssh: Could not resolve hostname github.com: nodename nor servname provided, or not known fatal: The remote end hung up unexpectedly” Saturday, September 29, 12

Slide 15

Slide 15 text

a solution d is a generic deployment tool and the basis for the next version of jitsu. 11 Saturday, September 29, 12

Slide 16

Slide 16 text

distribution of 12 api endpoint img processing email processing auth img email auth client client api responsibility Saturday, September 29, 12

Slide 17

Slide 17 text

distribution of 12 api endpoint img processing email processing auth img email auth client client api api api responsibility Saturday, September 29, 12

Slide 18

Slide 18 text

a demonstration 13 Saturday, September 29, 12

Slide 19

Slide 19 text

conclusion 14 in a network context, centralized systems are less reliable. A Saturday, September 29, 12

Slide 20

Slide 20 text

conclusion 14 in a network context, centralized systems are less reliable. A the number of end points should correlate to the demand on the service. B Saturday, September 29, 12

Slide 21

Slide 21 text

conclusion 14 in a network context, centralized systems are less reliable. A the number of end points should correlate to the demand on the service. B no single end point should be more important than another. C Saturday, September 29, 12

Slide 22

Slide 22 text

thanks X Saturday, September 29, 12