Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Global platform

15,825 views

Published on

Global coverage system design. Data

Published in: Technology

Global platform

  1. 1. Global Platform Design Terry.Cho (bwcho75@gmail.com)
  2. 2. What is Global Platform?  Global Platform Is deployed another country or across region Have to consider Regulation Time to market Culture Data Replication Operation
  3. 3. Global Platform Layers  Layers Let’s talk about Global Platform Characteristics from Infrastructure to Software Layer (Full Stack) !! Software Layer Infrastructure Layer
  4. 4. PART I.INFRASTRUCTURE LAYER
  5. 5. Infrastructure Stack [I. Infrastructure Layer]  Stack Cloud OS Server Storage Data Center
  6. 6. Data Center [I. Infrastructure Layer]  Location • Regulation • Bandwidth • Climate (Cooling) • Recruitment • Operation (24x7, Follow The Sun)  PUE  Global Center vs Regional Center  Zone 컨테이너 기반 4세대 데이타 센터
  7. 7. Server [I. Infrastructure Layer]  Commodity Server • Cost • Density  POD • Standard Design Google Server Design • Scale Out Unit [Procurement]  Network • Management Line • Service Line • VM Movement Line Microsoft Server Design • SAN (iSCSI)  Resiliency vs Redundancy Facebook Server Design
  8. 8. Storage [I. Infrastructure Layer]  IO Segregation
  9. 9. Cloud OS [I. Infrastructure Layer]  Open Source vs Commercial • Open Source is not so cheap [ Development Cost , Server H/W Cost, SW License Cost, Maintenance Fee] ※ Open Source : Open Stack Nova Level Approach  And DevOps
  10. 10. Use or Build? [I. Infrastructure Layer]  Use first for Time to Market !!  Build later after learning
  11. 11. PART II.SOFTWARE LAYER
  12. 12. Software Stack [ II. Software Layer ]  Common Server Software Layer Proxy Identity Management Business Logic Data Storage
  13. 13. IDM and PROXY [ II. Software Layer ]  Identity Management • Authentication & Authorization and Profile Management • IM (Master Data), AM (Authentication Only/LDAP),PM (Provisioning) • Integrate with Legacy System (Telco) • Global Replication across Data Center • Regulation  Proxy • Similar to SOA Enterprise Service Bus • Routing • Message Transformation (※ HTTP Header change) • Throttling • Logging + External or Internal Interface (like Enterprise Application Integration)  Protocol • REST, Thrift, Protocol Buffer
  14. 14. Business Logic [ II. Software Layer ]  Biz Logic • No shared data, Stateless  Prevent Trouble Propagation, Provides Scalability • Think about productivity  Python, Erlang
  15. 15. Data Storage [ II. Software Layer ]  Data - Storage • File Storage – COST and Consistency, Availibility • Simple Data Storage - NoSQL Combination • Relational Data Storage – RDBMS with Sharding , Query Off Loading • Small & High Performance Data Storage – In Memory Data Grid  Data Implementation Technology • Big Data Processing - Map & Reduce • Data Replication (across data center) – ETL, CDC and Filtering
  16. 16. Q&A

×