Cloud Computing and Edge Computing - Lecture Slides | CS 5410, Study notes of Computer Science

Download Cloud Computing and Edge Computing - Lecture Slides | CS 5410 and more Study notes Computer Science in PDF only on Docsity!

i

Ken

Birman

Cornell

University.

CS

Fall

Welcome

to

CS5140!

y^ A

course

on

cloud

computing,

edge

computing,

and

related

systems

technologies

W ’

i^

b^

k^

i^

b^

P^

f^

Bi^

y^ W

e’re

using

a^ textbook

written

by

Professor

Birman,

(a

bit

out

of

date).

Copies

on

reserve.

y^ Grading

mostly

based

on

three

assignments

aimed

at

y^ Grading

mostly

based

on

three

assignments

aimed

at

hands

‐on

experience

with

the

things

we’re

learning

in

class y Background:

Java

or

C++

(or

C#),

familiar

with

threads,

comfortable

writing

programs,

had

an

hi^

d^

i

architecture

course

and

an

operating

systems

course.

Cloud

Computing

Concept

Email, file storage,

IM, search

Databases, spreadsheets,

office apps

Client systems useweb technologies

Web services

web technologies

Google/IBM/Amazon/Yahoo! host the services

Web services

Supporting

technologies

y^ Infrastructure

y^ Core

management

and

h d li

f^

ti

y^ Cloud

“enablers”

y^ Map

‐Reducebl

scheduling

functions

y^ Event

notification

services

y^ Storage

systems

(GFS)

y^ BigTable y^ Astrolabe y^ Amazon’s

shopping

cart

y^ Storage

systems

(GFS)

y^ Monitoring,

debugging,

tuning

assistance

y^ Amazon s

shopping

cart

y^ Even

higher

level?

y^ Increasingly:

virtualization

Even

higher

level?

y^ Tools

for

building

and

analyzing

massive

graphs

Will

the

next

big

thing

happen

g^

g^

pp

on

the

edge

of

the

network?

VR

i^

i^

Di t ib t d

….

VR

immersion…

Distributed

programming

by

“drag

and

drop”

http://liveobjects.cs.cornell.eduhttp://liveobjects.cs.cornell.edu

But

they

also

depend

on

data

y^

p

center

resources

y^ Data

centers

host

maps,

databases,

rendering

software

y^ Think

of

the

“static”

content

as

coming

from

a^ data

center,

and

streams

of

events

reflecting

real

‐time

content

coming

directly

from

sensors

and

“synthetic

content

coming

directly

from

sensors

and

synthetic

content

sources”,

combined

on

your

end

‐user

node

y^ All

of

this

needs

to

scale

to

massive

deployments

It’s a big, big

g,

g

world out onworld out onthe edgethe edge….

How

does

this

overlap

withp

edge

technologies?

y^ The

edge

is^

a^ world

of

peer

‐to

‐peer

solutions

y^ BitTorrent,

Napster/Gnutella,

PPLive,

Skype,

and

even

Li^

Obj

t

Live

Objects y^ How

are

these

built?

What

issues

need

to be

addressed

when

systems

live

out

in^

the

wild

(in

the

Internet)?

y^

(^

y^ But

those

edge

solutions

are

invariably

supported

by

some

kind

of

cloud

service,

and

in

the

future

the

integration

is^

going

to

become

more

significant

Wh

h^

h^

f^

d^

l^

i^

l^

d

y^ Wh

at^

happens

when

we

graft

edge

solutions

to

cloud

platforms?

Connecting

the

cloud

to

the

edge

y^ The

cloud

is^

a^ good

place

to

y^ Store

massive

amounts

of^

content

y^ Keep

precomputed information,

account

information

y^ Run

scalable

services

y^ The

edge

is^

a^ good

place

to

y^ Capture

data

from

the

real

world

(sensors

cameras

y^ Capture

data

from

the

real

world

(sensors,

cameras…)

y^ Share

high

‐rate

video,

voice,

event

streams,

“updates”

y^ Support

direct

collaboration,

interaction

pp^

Stylistic

comments

y^ One

way

to

approach

CS

would

focus

on

a^ how

‐to

way

of

using

standards

and

packages

F^

l^

Mi

f^ f

I di

h i

b

y^ F

or^ example,

Microsoft

favors

Indigo

as^

their

web

services

solution

for

Windows

platforms

y^ We

could

spend

weeks

learning

everything

we

can

We

could

spend

weeks

learning

everything

we

can

about

Indigo,

do

projects

using

Indigo,

etc.

y^ You

would

emerge

as^

an^

“Indigo

expert”

Stylistic

comments

y^ A

second

extreme

would

be

to

completely

ignore

the

web

services

standards

and

focus

entirely

on

the

theorytheory^ y^

We

would

discuss

ways

of^

thinking

about

distributed

systemsy y Models

for

describing

protocols

y^ Ways

of^

proving

things

about

them

y^ You

would

be

left

to

apply

these

ideas

“as

an

exercise”

Let’s

look

at

an

example

y^ To

illustrate

the

way

the

class

will

operate,

let’s

look

at

a^ typical

example

of

a^ problem

that

cuts

across

these

three

elements

three

elements

y^ It

arises

in^

a^ standard

web

services

context

y^ But

it^ raises

harder

questions

y^ But

it^ raises

harder

questions

y^ Ultimately,

theoretical

tools

help

us

gain

needed

clarity

ATC

Architecture

NETWORK INFRASTRUCTURENETWORK INFRASTRUCTURE

ATC StateATC State

ATC status is a kind of temporal database: for each ATC sector, it tellsus what flights might be in that sector and when they will be there