Connected Services - Models and Architecture

Slide 1

Slide 1 text

  LTKA #2 Connected Services - Models & Architecture Dr.-Ing. Eueung Mulyana http://eueung.github.io/ET3010 ET-3010 | Connected Services and Cloud Computing | Attribution-ShareAlike CC BY-SA 1 / 51

Slide 2

Slide 2 text

Outline Basic Model Start Small - Gmail Model Mapping Inside the Cloud Data Center Components, Models & Interactions 2 / 51

Slide 3

Slide 3 text

  CS Basic Model Revisited 3 / 51

Slide 4

Slide 4 text

CS - Model Connected Services & Cloud 4 / 51

Slide 5

Slide 5 text

Model (Zoom-In) System-Boxes Inside Cloud Nested Clouds 5 / 51

Slide 6

Slide 6 text

Convention: Cloud vs. Network Historically, before the rise of CC, the term Cloud was very common to be used to refer to Networks or Interconnected-Systems Thus, in this lecture, Cloud may refer to both of them, depends on context. Notes In CC concept, Network is a part of CC, but Network is not used only for CC 6 / 51

Slide 7

Slide 7 text

  Start Small Gmail Service 7 / 51

Slide 8

Slide 8 text

Gmail Service The Story of Send  8 / 51

Slide 9

Slide 9 text

Gmail Service The Story of Send Steps 1. Sender 2. Sender's Provider (ISP) 3. Backbone 4. Data Center - Front Server 5. Data Center - Gmail Backend (Cloud) 6. Backbone 7. Recipient's Provider 8. Recipient 9 / 51

Slide 10

Slide 10 text

  Model Mapping 10 / 51

Slide 11

Slide 11 text

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

Slide 12

Slide 12 text

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

Slide 13

Slide 13 text

Model TLKM 1 2 (1) and (2) 13 / 51

Slide 14

Slide 14 text

Backbone (Outgoing) (3) Backbone - e.g. TLKM Peering / Upstream Channels 14 / 51

Slide 15

Slide 15 text

Data Center - Front Server (4) Google DC - Front Server 15 / 51

Slide 16

Slide 16 text

Data Center - Front Server (4) Google DC - Front Server 16 / 51

Slide 17

Slide 17 text

Data Center - Front Server (4) Google DC - Front Server 17 / 51

Slide 18

Slide 18 text

Data Center - Gmail Backend (5) Google DC - Gmail Backend 18 / 51

Slide 19

Slide 19 text

Data Center - Gmail Backend (5) Google DC - Gmail Backend 19 / 51

Slide 20

Slide 20 text

Model TLKM 3 4,5 Google (3), (4) and (5) 20 / 51

Slide 21

Slide 21 text

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

Slide 22

Slide 22 text

Recipient's ISP (7) Receipient's ISP e.g. XL 22 / 51

Slide 23

Slide 23 text

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

Slide 24

Slide 24 text

Model TLKM 6 7 Google XL 8 (6), (7) and (8) 24 / 51

Slide 25

Slide 25 text

  Inside the Cloud 25 / 51

Slide 26

Slide 26 text

Providers (ISPs) TLKM Google XL Providers' Cloud Next: An Example of Providers' Network (SPIRENT) 26 / 51

Slide 27

Slide 27 text

27 / 51

Slide 28

Slide 28 text

Google TLKM Google XL Google's Cloud 28 / 51

Slide 29

Slide 29 text

29 / 51

Slide 30

Slide 30 text

30 / 51

Slide 31

Slide 31 text

31 / 51

Slide 32

Slide 32 text

32 / 51

Slide 33

Slide 33 text

Google DC 2004, From Jupiter Rising:... (Arjun Singh et.al.) SIGCOMM 2015 33 / 51

Slide 34

Slide 34 text

Backbone TLKM Google XL Transport & Interconnection Backbone 34 / 51

Slide 35

Slide 35 text

35 / 51

Slide 36

Slide 36 text

Notes TLKM Google XL Google's Cloud 36 / 51

Slide 37

Slide 37 text

Google's Global DC Facility Backbone in the Cloud 37 / 51

Slide 38

Slide 38 text

  Data Center 38 / 51

Slide 39

Slide 39 text

Some Defs Literal: Facility to store and process data. A large group of networked computer servers typically used by organizations for the remote storage, processing, or distribution of large amounts of data (Google Def). A datacenter is a (centralized) facility, either physical or virtual, for the storage, management, and dissemination of data and information organized around a particular body of knowledge or pertaining to a particular business (techtarget.com). A data center is a facility that centralizes an organization's IT operations and equipment, and where it stores, manages, and disseminates its data. Data centers house a network's most critical systems and are vital to the continuity of daily operations (paloaltonetworks.com). Major Functional Components Compute (Servers) Storage Network 39 / 51

Slide 40

Slide 40 text

Data Center Example A Look into a Google Data Center  40 / 51

Slide 41

Slide 41 text

  Components, Models & Interactions 41 / 51

Slide 42

Slide 42 text

Legacy Service Provider System Era before CS 42 / 51

Slide 43

Slide 43 text

Connected Service Provider System CS Era 43 / 51

Slide 44

Slide 44 text

Connected Service Provider Part of the Global Cloud 44 / 51

Slide 45

Slide 45 text

Connected Service Provider Simplification 45 / 51

Slide 46

Slide 46 text

Connected Things System CS is not only for Human But also for Arbitrary Things 46 / 51

Slide 47

Slide 47 text

Connected Things Simplification 47 / 51

Slide 48

Slide 48 text

CS Components HW: Devices + Infrastructure SW System: Client App + Backend SW System: UI + Data (Local+Remote) + Process (Local+Remote) 48 / 51

Slide 49

Slide 49 text

  Refs 49 / 51

Slide 50

Slide 50 text

Refs 1. http://www.google.com/about/datacenters 2. http://www.google.com/green/storyofsend (N/A) 3. Urs Hoelzle, OpenFlow @ Google, ONS 50 / 51

Slide 51

Slide 51 text

  END Eueung Mulyana http://eueung.github.io/ET3010 ET-3010 | Connected Services and Cloud Computing | Attribution-ShareAlike CC BY-SA 51 / 51