Download as PDF, PPTX
More Related Content
Similar to AWS Summit 2015 Tokyo Breakout: Global Large Scale Cloud Design and Cloud Native Enterprise Infrastructure at Fast Retailing
![[AWS에서의 미디어 및 엔터테인먼트] AWS 개요, 클라우드 스토리지 및 Amazon CloudFront, Elastic Transcod...](https://cdn.slidesharecdn.com/ss_thumbnails/awsoverview-140219201920-phpapp02-thumbnail.jpg?width=640&height=640&fit=bounds)
![[BDD 2025 - Full-Stack Development] Agentic AI Architecture: Redefining Syste...](https://cdn.slidesharecdn.com/ss_thumbnails/fs-agenticaiarchitectureredefiningsystemcommunication-251124030838-e6c70cc2-thumbnail.jpg?width=640&height=640&fit=bounds)
![[BDD 2025 - Mobile Development] Exploring Apple’s On-Device FoundationModels](https://cdn.slidesharecdn.com/ss_thumbnails/md-exploringappleson-devicefoundationmodels-251124030840-d690542c-thumbnail.jpg?width=640&height=640&fit=bounds)
![[BDD 2025 - Full-Stack Development] PHP in AI Age: The Laravel Way. (Rizqy Hi...](https://cdn.slidesharecdn.com/ss_thumbnails/fs-phpinaiagethelaravelway-251125012602-ef9d330e-thumbnail.jpg?width=640&height=640&fit=bounds)
![[DevFest Strasbourg 2025] - NodeJs Can do that !!](https://cdn.slidesharecdn.com/ss_thumbnails/devfeststrasbourg2025-nodejscandothat-251127142731-da65b6fd-thumbnail.jpg?width=640&height=640&fit=bounds)
AWS Summit 2015 Tokyo Breakout: Global Large Scale Cloud Design and Cloud Native Enterprise Infrastructure at Fast Retailing
- 1. Global Large ScaleCloud Design Cloud Native Enterprise Infrastructure Fast Retailing Co., Ltd.
- 2. Keito Fukuda Lead TechnicalArchitect Fast Retailing Co., Ltd. Responsibilities: • Digital Services • Mobile Services • O2O • Backend Platforms • Infrastructure/Architecture Kenichiro Ara Infrastructure & Communication Lead Fast Retailing Co., Ltd. Responsibilities: • Enterprise infrastructure/architecture • Global WAN • Office/Store infrastructure • Corporate infrastructure • ICT technologies
- 4. JPY1,380,000,000,000 2,75389,580 20+ Revenue StoresEmployees* Countries Asof Aug. 2014 *Including Full-Time Employees, Contract Workers, Part-Timers
- 5. 4,500 9,000 13,500 18,000 1992 1995 19982001 2004 2007 2010 2013 2015 (JPY 100M) Est. Group Revenue
- 6. 1. AWS atFR 2. Cloud Design Strategy 3. Global Network Design 4. Enterprise Cloud Strategy Agenda
- 7. 1. AWS atFR 2. Cloud Design Strategy 3. Global Network Design 4. Enterprise Cloud Strategy Agenda
- 8. UNIQLO Recipe WakeupClock Calendar Looks UTme Bicqlo Kids Camera
- 9. EC Site UNIQLOAPP UTme APP
- 10.
- 11. 100+ 1,300+ systems instances Asof May. 2015
- 12. # of instanceson AWS 500 1,000 1,500 2,000 2010 2011 2012 2013 2014 2015 0 10 50 300 1,000 2,000
- 13. Agenda 1. AWS atFR 2. Cloud Design Strategy 3. Global Network Design 4. Enterprise Cloud Strategy
- 14. Independency Maintainability Availability Recoverability Replicability ScalabilityVisibility Cloud Design Best Practices
- 15. Independency Make System LooselyDecoupled(Micro-Service)
- 16. 1300+ Instances 100+ Systems 30+Vendors Independency Many Instances Co-Existing in Cloud
- 17. Each System SharingRecourses and Assets Independency A B C D E
- 18. Each System SharingRecourses and Assets Independency A B C D E Infra Cost/Procurement No Longer Problem
- 19. Independency Make Respective SystemIndependent to Minimize Dependency A B C D E
- 20. Independency Use Security Groupper System to Satisfy Security A B C D E
- 21. Maintainability Take Full Advantageof Full-Managed Services(PaaS)
- 22. Maintainability System Getting MoreComplicated Mail Queue RDBMS Cache Search NoSQL BigData Push DNS
- 23. Maintainability System Getting MoreComplicated Mail Queue RDBMS Cache Search NoSQL BigData Push DNSDo Not Reinvent Wheels and Babysit
- 24. Maintainability Minimize Worrying aboutInfrastructure
- 25. Scalability ELB + ASReady Instance with Auto-Scaling ELB AS Ready EC2 Auto Scale
- 26. Scalability Probably Scalability NotRequired at the Beginning
- 27. Scalability Probably Scalability NotRequired at the Beginning System Requirements Always Change
- 28. “AS Ready” Stateless +AutoStart Scalability Make System Scalable from the Beginning
- 29. Scalability Scale System WhenNecessary
- 30. Availability Multi-AZ/Region with DNSFailover Availability Zone region Route53 Region Availability ZoneELB
- 31. Availability Availability Zone A ProbablyAvailability Not Required at the Beginning
- 32. Availability Zone A Availability ProbablyAvailability Not Required at the Beginning System Requirements Always Change
- 33. Availability Zone A Availability SystemDesigned Assuming Infra Never Goes Down
- 34. Availability Zone A Availability SystemDesigned Assuming Infra Never Goes Down Do Not Assume Instance will Never Go Down
- 35. Availability Zone AAvailability Zone C Availability Do Not Retain Availability in Single Instance, Make It Overall
- 36. Recoverability Easy to Recoverfrom Troubles AS Ready EC2
- 37.
- 38.
- 39. TroubleShoot Recoverability Do Not MakeDevelopers TroubleShootMonitoring Do Not Take Long Time to Get it Recovered
- 40. Restart Recoverability Make System RecoveryEasier “AS Ready” Stateless + AutoStart Monitoring
- 41. Replicability Easy to Clonea System CloudFormation Elastic Beanstalk CodeDeploy
- 42. Replicability Production Only Production EnvironmentNecessary at the Beginning
- 43. Production Staging IntegrationStressTest Development Replicability Multi-Environments Required as We Go
- 44. Replicability Production Staging IntegrationStressTest Development Make Cloning System Easy
- 45.
- 46. Portability Users System Needsto Connect with lots of Endpoints
- 47. Portability Users System Needsto Connect with lots of Endpoints Do Not Get All Endpoints Connected thru IPs
- 48. Users org.xxx.uniqlo.com read-db.xxx.uniqlo.comdb.xxx.uniqlo.com cache.xxx.uniqlo.com Portability Assign“Owned”Hostname to Endpointsfor Maximum Flexibility static.xxx.uniqlo.com
- 49. Users org.xxx.uniqlo.com Portability Easy System Updatewith Blue-Green Deployment
- 50. Visibility Collect as MuchData as Possible ConfigCloudWatch CloudTrail
- 51. Visibility Users Modern SystemConsists of Full-Managed Services
- 52. Users Visibility Difficult to Figureout Root Cause
- 53. Users Visibility Difficult to Figureout Root Cause Not Everything under your Control on Cloud
- 54. Monitoring Visibility Collect as MuchData as Possible
- 55. Do NOT CarryOver Enterprise Best Practice to Cloud
- 56. Agenda 1. AWS atFR 2. Cloud Design Strategy 3. Global Network Design 4. Enterprise Cloud Strategy
- 57. Tokyo Sydney Singapore Ireland Sao Paulo California Oregon Frankfurt Beijing Virginia Multi-Regions forGlobal Service Distribution
- 58. Production Staging Development Management 4 VPCs inEach Region Region
- 59. Production Staging Development Management B2C/B System ResidingTogether, Each VPC Completely Isolated Region
- 60. Production Staging Development Management Management VPC Reachableto All VPCs Region
- 61. Production Staging Development Management 10G x 2 1Gx 2DX for Only System Connection Direct Connect
- 62. Production Staging Development Management 10G x 2 1Gx 2 Customers Employees Developers Access
- 63. Management Production Staging Development Same VPC Designacross Regions Management Production Staging Development Management Production Staging Development Management Production Staging Development Management Production Staging Development Management Production Staging Development Management Production Staging Development Management Production Staging Development
- 64.
- 65. Management Production Staging Development Mesh Topology forHigh Availability Management Production Staging Development Management Production Staging Development Management Production Staging Development Management Production Staging Development Management Production Staging Development Management Production Staging Development Management Production Staging Development
- 66. Management Production Staging Development Management Production Staging Development Management Production Staging Development Management Production Staging Development Management Production Staging Development Management Production Staging Development Management Production Staging Development Management Production Staging Development Cross Region Connectionwith VyOS VyOS VyOS VyOS VyOS VyOS VyOS VyOS VyOS
- 67.
- 68.
- 69.
- 70.
- 71. Public(DMZ) Private Secure 3 Segments inEach VPC VPC
- 72.
- 73.
- 74. Agenda 1. AWS atFR 2. Cloud Design Strategy 3. Global Network Design 4. Enterprise Cloud Strategy
- 75. Quick Decision Makingfor AWS Migration 2014/3: 2014/4-10: Verification & Adaptation 2014/11: Director & CIO Approvals 2014/12: CEO Approval
- 76. Current Enterprise AWSArchitecture Data center 1G x 2 10G x 2 Production Verify & Dev
- 77. Paradigm Shift Required-Mindset Instance Gets Down Hardware Crushes Requirement Changes
- 78. WAN-Based Internet-Based Paradigm ShiftRequired -Network
- 79. Encryption & RightsManagement Real-Time Monitoring & Treatment Paradigm Shift Required -Security
- 80. Fast Retailing ITTeam Direction towards 2020
- 81. 12,500 25,000 37,500 50,000 1992 1994 19961998 2000 2002 2004 2006 2008 2010 2012 2014 2016 2018 2020 (JPY 100M) Group Revenue
- 82.
- 83.
- 84.
- 85.