Models and Architecture - Connected Services and Cloud Computing
0 likes478 views
The document discusses the architecture and models of connected services, particularly focusing on cloud computing, data centers, and the Gmail service workflow. It explains the components and interactions within cloud environments, emphasizing the role of data centers in storing and processing data. Additionally, it highlights the evolution from traditional service providers to connected service providers in the context of global cloud services.
Models and Architecture - Connected Services and Cloud Computing
- 1. 1 / 51 Connected Services Models & Architecture Dr.-Ing. Eueung Mulyana https://eueung.github.io/ET3010 ET-3010 | Attribution-ShareAlike CC BY-SA
- 2. Outline Basic Model Start Small - GMail Model Mapping Inside the Cloud Data Center Components, Models & Interactions 2 / 51
- 4. 4 / 51 Connected Services & Cloud Model
- 5. 5 / 51 System-Boxes inside Cloud Nested Clouds Zoom In
- 6. 6 / 51 Historically, before the rise of CC, the term Cloud was very common to be used to refer to Networks or Interconnected- Systems. Depending on context, Cloud in this lecture may refer to both of them. In CC concept, Network is a part of CC, but Network is not used only for CC. Cloud (without "Computing") is sometimes used interchangebly with Networks or the Internet Cloud vs. Network
- 7. GMail Service Start Small 7 / 51
- 8. 8 / 51 GMail Service The Story of Send
- 9. 9 / 51 GMail Service The Story of Send 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
- 10. Model Mapping 10 / 51
- 11. (1) Sender e.g. Customer of an ISP (TLKM) 11 / 51
- 12. (2) Sender's ISP e.g. TLKM 12 / 51
- 13. 13 / 51 (1) and (2)
- 14. (3) Outgoing Backbone - e.g. TLKM Peering / Upstream Channels 14 / 51
- 15. (4) Google DC - Front Server 15 / 51
- 16. (4) Google DC - Front Server 16 / 51
- 17. (4) Google DC - Front Server 17 / 51
- 18. (5) Google DC - GMail Backend 18 / 51
- 19. (5) Google DC - GMail Backend 19 / 51
- 20. 20 / 51 (3), (4) and (5)
- 21. (6) Backbone - e.g. Google's Peering / Upstream Channels21 / 51
- 22. (7) Receipient's ISP e.g. XL 22 / 51
- 23. (8) Recipient e.g. Customer of an ISP (XL) 23 / 51
- 24. 24 / 51 (6), (7) and (8)
- 25. Inside the Cloud 25 / 51
- 26. 26 / 51 Providers' Cloud
- 27. An Example of Providers' Network (SPIRENT) 27 / 51
- 28. 28 / 51 Google's Cloud
- 29. Mayes County, Oklahoma - Sunset & Landscape 29 / 51
- 30. Council Blu s, Iowa - Inside Google's Campus Network Room 30 / 51
- 31. Mayes County, Oklahoma - Rack, 4 Switches, Colorful Cables 31 / 51
- 32. Douglas County, Georgia - Colorful Pipes & G-Bike 32 / 51
- 33. 33 / 51 Google DC 2004 From Jupiter Rising:... (Arjun Singh et.al.) SIGCOMM 2015
- 34. 34 / 51 Transport & Interconnection Backbone
- 35. Sumarine Cables Map 35 / 51
- 36. 36 / 51 Google's Cloud Notes
- 37. Backbone in the Cloud - Google's Global DC Facility 37 / 51
- 38. Data Center 38 / 51
- 39. 39 / 51 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
- 40. 40 / 51 Data Center Example A Look into a Google Data Center
- 42. Legacy Service Provider Prior to CS Era 42 / 51
- 43. Connected Service Provider CS Era 43 / 51
- 44. Connected Service Provider Part of the Global Cloud 44 / 51
- 45. Connected Service Provider Simpli cation 45 / 51
- 46. Connected Things CS is not only for Human, But also for Arbitrary Things 46 / 51
- 47. Connected Things Simpli cation 47 / 51
- 48. 48 / 51 Connected Services Components Hardware Devices + Infrastructure Software System Client App + Backend Software System UI + Data (Local+Remote) + Process (Local+Remote)
- 49. Refs 49 / 51
- 50. References 1. http://www.google.com/about/datacenters 2. http://www.google.com/green/storyofsend (N/A) 3. Urs Hoelzle, OpenFlow @ Google, ONS 50 / 51
- 51. 51 / 51 ENDDr.-Ing. Eueung Mulyana https://eueung.github.io/ET3010 ET-3010 | Attribution-ShareAlike CC BY-SA