models and architecture - connected services and cloud computing

51
1 / 51 Connected Services Models & Architecture Dr.-Ing. Eueung Mulyana https://eueung.github.io/ET3010 ET-3010 | Attribution-ShareAlike CC BY-SA

Upload: eueung-mulyana

Post on 07-Feb-2017

185 views

Category:

Technology


0 download

TRANSCRIPT

1 / 51

Connected Services

Models &ArchitectureDr.-Ing. Eueung Mulyanahttps://eueung.github.io/ET3010ET-3010 | Attribution-ShareAlike CC BY-SA

Outline

Basic Model

Start Small - GMail

Model Mapping

Inside the Cloud

Data Center

Components, Models & Interactions

2 / 51

Connected Services

Basic Model

3 / 51

4 / 51

Connected Services & Cloud

Model

5 / 51

System-Boxes inside Cloud Nested Clouds

Zoom In

6 / 51

Historically, before the rise of CC, the termCloud was very common to be used to

refer to Networks or Interconnected-Systems.

Depending on context, Cloud in this lecture may refer to bothof them.

In CC concept, Network is a part of CC, but Network is not used only for CC.

Cloud (without "Computing") is sometimes usedinterchangebly with Networks or the Internet

Cloud vs.Network

GMail Service

Start Small

7 / 51

8 / 51

GMail ServiceThe Story of Send

9 / 51

GMail ServiceThe Story of Send

1. Sender2. Sender's Provider (ISP)3. Backbone4. Data Center - Front Server5. Data Center - GMail Backend (Cloud)6. Backbone7. Recipient's Provider8. Recipient

Model Mapping

10 / 51

(1) Sender e.g. Customer of an ISP (TLKM)11 / 51

(2) Sender's ISP e.g. TLKM12 / 51

13 / 51

(1) and (2)

(3) Outgoing Backbone - e.g. TLKM Peering / UpstreamChannels

14 / 51

(4) Google DC - Front Server15 / 51

(4) Google DC - Front Server16 / 51

(4) Google DC - Front Server17 / 51

(5) Google DC - GMail Backend18 / 51

(5) Google DC - GMail Backend19 / 51

20 / 51

(3), (4) and (5)

(6) Backbone - e.g. Google's Peering / Upstream Channels21 / 51

(7) Receipient's ISP e.g. XL22 / 51

(8) Recipient e.g. Customer of an ISP (XL)23 / 51

24 / 51

(6), (7) and (8)

Inside the Cloud

25 / 51

26 / 51

Providers' Cloud

An Example of Providers' Network (SPIRENT)

27 / 51

28 / 51

Google's Cloud

Mayes County, Oklahoma - Sunset & Landscape29 / 51

Council Blu�s, Iowa - Inside Google's Campus NetworkRoom

30 / 51

Mayes County, Oklahoma - Rack, 4 Switches, ColorfulCables

31 / 51

Douglas County, Georgia - Colorful Pipes & G-Bike32 / 51

33 / 51

Google DC 2004

From Jupiter Rising:... (ArjunSingh et.al.) SIGCOMM 2015

34 / 51

Transport &InterconnectionBackbone

Sumarine Cables Map35 / 51

36 / 51

Google's Cloud

Notes

Backbone in the Cloud - Google's Global DC Facility37 / 51

Data Center

38 / 51

39 / 51

Literal: Facility to store and process data.

A large group of networked computer serverstypically used by organizations for the remotestorage, processing, or distribution of largeamounts of data (Google Def).

A datacenter is a (centralized) facility, either physical or virtual, forthe storage, management, and dissemination of data andinformation organized around a particular body of knowledge orpertaining to a particular business (techtarget.com).

A data center is a facility that centralizes an organization's IToperations and equipment, and where it stores, manages, anddisseminates its data. Data centers house a network's most criticalsystems and are vital to the continuity of daily operations(paloaltonetworks.com).

Major Functional ComponentsCompute (Servers)StorageNetwork

40 / 51

Data CenterExample

A Look into a Google Data Center

Components, Models& Interactions

41 / 51

Legacy Service ProviderPrior to CS Era 42 / 51

Connected Service ProviderCS Era 43 / 51

Connected Service ProviderPart of the Global Cloud 44 / 51

Connected Service ProviderSimpli�cation 45 / 51

Connected ThingsCS is not only for Human, But also for Arbitrary Things 46 / 51

Connected ThingsSimpli�cation 47 / 51

48 / 51

ConnectedServices

Components

Hardware

Devices + Infrastructure

Software System

Client App + Backend

Software System

UI + Data (Local+Remote) + Process (Local+Remote)

Refs

49 / 51

References1. http://www.google.com/about/datacenters2. http://www.google.com/green/storyofsend (N/A)3. Urs Hoelzle, OpenFlow @ Google, ONS

50 / 51

51 / 51

ENDDr.-Ing. Eueung Mulyanahttps://eueung.github.io/ET3010ET-3010 | Attribution-ShareAlike CC BY-SA