Christian Rolf - Speaker Deck

Slide 1

Slide 1 text

AutoCloud: Scalable Client-Side Replication Christian Rolf Corvid

Slide 2

Slide 2 text

AutoCloud: Scalable Client-Side Replication (work in little to no progress) Christian Rolf Corvid

Slide 3

Slide 3 text

Who is Corvid?

Slide 4

Slide 4 text

Who is Corvid? • My start-up, Dunedin-based

Slide 5

Slide 5 text

Who is Corvid? • My start-up, Dunedin-based • Mentored by Nicolas

Slide 6

Slide 6 text

Who is Corvid? • My start-up, Dunedin-based • Mentored by Nicolas • We develop cloud software for automatic rostering

Slide 7

Slide 7 text

Who is Corvid? • My start-up, Dunedin-based • Mentored by Nicolas • We develop cloud software for automatic rostering • Embarrassingly parallel problem, but NP-complete

Slide 8

Slide 8 text

AutoCloud in a single sentence • Lots of data on web-pages doesn’t change and can be retrieved from a local mirror

Slide 9

Slide 9 text

• Lots of data on web-pages doesn’t change and can be retrieved from a local mirror

Slide 10

Slide 10 text

• Lots of data on web-pages doesn’t change and can be retrieved from a local mirror

Slide 11

Slide 11 text

• Lots of data on web-pages doesn’t change and can be retrieved from a local mirror

Slide 12

Slide 12 text

• Lots of data on web-pages doesn’t change and can be retrieved from a local mirror

Slide 13

Slide 13 text

• Lots of data on web-pages doesn’t change and can be retrieved from a local mirror Static

Slide 14

Slide 14 text

• Lots of data on web-pages doesn’t change and can be retrieved from a local mirror Static Dynamic

Slide 15

Slide 15 text

• Lots of data on web-pages doesn’t change and can be retrieved from a local mirror Static Dynamic Semi-static

Slide 16

Slide 16 text

• Lots of data on web-pages doesn’t change and can be retrieved from a local mirror

Slide 17

Slide 17 text

• Lots of data on web-pages doesn’t change and can be retrieved from a local mirror 99%

Slide 18

Slide 18 text

• Lots of data on web-pages doesn’t change and can be retrieved from a local mirror 99% 1%

Slide 19

Slide 19 text

• Lots of data on web-pages doesn’t change and can be retrieved from a local mirror 99% 85% 1%

Slide 20

Slide 20 text

• Lots of data on web-pages doesn’t change and can be retrieved from a local mirror 99% 85% 1% 75%

Slide 21

Slide 21 text

• Lots of data on web-pages doesn’t change and can be retrieved from a local mirror 99% 85% 1% 75% 72%

Slide 22

Slide 22 text

Why?

Slide 23

Slide 23 text

Why? • To increase throughput in times of load

Slide 24

Slide 24 text

Why? • To increase throughput in times of load • To save bandwidth where it is limited (e.g. NZ)

Slide 25

Slide 25 text

Why? • To increase throughput in times of load • To save bandwidth where it is limited (e.g. NZ) • To reduce the cost of running popular sites

Slide 26

Slide 26 text

That said, some things are better on paper

Slide 27

Slide 27 text

Any questions before we get technical?

Slide 28

Slide 28 text

• Lots of data on web-pages doesn’t change and can be retrieved from a local mirror

Slide 29

Slide 29 text

• Lots of data on web-pages doesn’t change and can be retrieved from a local mirror A client that has a copy of a web page in its browser cache

Slide 30

Slide 30 text

• Lots of data on web-pages doesn’t change and can be retrieved from a local mirror

Slide 31

Slide 31 text

• Lots of data on web-pages doesn’t change and can be retrieved from a local mirror Run a web server inside the web browser, delivering data from the cache

Slide 32

Slide 32 text

Run a web server inside the web browser, delivering data from the cache

Slide 33

Slide 33 text

Run a web server inside the web browser, delivering data from the cache

Slide 34

Slide 34 text

Run a web server inside the web browser, delivering data from the cache The static and semi-static data stored in the cache

Slide 35

Slide 35 text

Run a web server inside the web browser, delivering data from the cache

Slide 36

Slide 36 text

Run a web server inside the web browser, delivering data from the cache

Slide 37

Slide 37 text

Run a web server inside the web browser, delivering data from the cache var http = require('http'); http.createServer(function (req, res) { res.writeHead(200, {'Content-Type': 'text/plain'}); res.end('Hello World\n'); }).listen(80, '127.0.0.1');

Slide 38

Slide 38 text

Run a web server inside the web browser, delivering data from the cache The overhead is small compared to the size of a web-page

Slide 39

Slide 39 text

Think; in-browser BitTorrent for web-pages

Slide 40

Slide 40 text

What’s needed

Slide 41

Slide 41 text

What’s needed • List of static & semi-static elements sent to clients from the web-server

Slide 42

Slide 42 text

What’s needed • List of static & semi-static elements sent to clients from the web-server • Clients notifying the web-server about their mirroring

Slide 43

Slide 43 text

What’s needed • List of static & semi-static elements sent to clients from the web-server • Clients notifying the web-server about their mirroring • Subsequent clients will get dynamic data from web-server and the rest from mirrors