This is a presentation shared from Fast Retailing Co., Ltd. in one of Breakout sessions in AWS Summit Tokyo 2015, talking about how we use AWS, what's the best way to design system on Cloud comparing the best practices on-premises. In addition to the topic about global network design to distribute all of our system to our global customers as well as employees/store staffs.

1. Global Large Scale Cloud Design
Cloud Native Enterprise Infrastructure
Fast Retailing Co., Ltd.

2. Keito Fukuda
Lead Technical Architect
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
As of Aug. 2014
*Including Full-Time Employees, Contract Workers, Part-Timers

5. 4,500
9,000
13,500
18,000
1992 1995 1998 2001 2004 2007 2010 2013 2015
(JPY 100M)
Est.
Group Revenue

6. 1. AWS at FR
2. Cloud Design Strategy
3. Global Network Design
4. Enterprise Cloud Strategy
Agenda

7. 1. AWS at FR
2. Cloud Design Strategy
3. Global Network Design
4. Enterprise Cloud Strategy
Agenda

8. UNIQLO Recipe Wakeup Clock Calendar Looks
UTme Bicqlo Kids Camera

9. EC Site UNIQLO APP UTme APP

10. 20,000,000,000
req/month
100,000 45G
req/sec bps
As of May. 2015

11. 100+ 1,300+
systems instances
As of May. 2015

12. # of instances on 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 at FR
2. Cloud Design Strategy
3. Global Network Design
4. Enterprise Cloud Strategy

14. Independency Maintainability
Availability
Recoverability Replicability
Scalability Visibility
Cloud Design Best Practices

15. Independency
Make System Loosely Decoupled(Micro-Service)

16. 1300+ Instances
100+ Systems
30+ Vendors
Independency
Many Instances Co-Existing in Cloud

17. Each System Sharing Recourses and Assets
Independency
A B C D E

18. Each System Sharing Recourses and Assets
Independency
A B C D E
Infra Cost/Procurement No Longer Problem

19. Independency
Make Respective System Independent to Minimize Dependency
A B C D E

20. Independency
Use Security Group per System to Satisfy Security
A B C D E

21. Maintainability
Take Full Advantage of Full-Managed Services(PaaS)

22. Maintainability
System Getting More Complicated
Mail
Queue
RDBMS
Cache
Search
NoSQL
BigData
Push DNS

23. Maintainability
System Getting More Complicated
Mail
Queue
RDBMS
Cache
Search
NoSQL
BigData
Push DNSDo Not Reinvent Wheels and Babysit

24. Maintainability
Minimize Worrying about Infrastructure

25. Scalability
ELB + AS Ready Instance with Auto-Scaling
ELB AS Ready EC2 Auto Scale

26. Scalability
Probably Scalability Not Required at the Beginning

27. Scalability
Probably Scalability Not Required at the Beginning
System Requirements Always Change

28. “AS Ready”
Stateless + AutoStart
Scalability
Make System Scalable from the Beginning

29. Scalability
Scale System When Necessary

30. Availability
Multi-AZ/Region with DNS Failover
Availability Zone
region
Route53 Region Availability ZoneELB

31. Availability
Availability Zone A
Probably Availability Not Required at the Beginning

32. Availability Zone A
Availability
Probably Availability Not Required at the Beginning
System Requirements Always Change

33. Availability Zone A
Availability
System Designed Assuming Infra Never Goes Down

34. Availability Zone A
Availability
System Designed Assuming Infra Never Goes Down
Do Not Assume Instance will Never Go Down

35. Availability Zone A Availability Zone C
Availability
Do Not Retain Availability in Single Instance, Make It Overall

36. Recoverability
Easy to Recover from Troubles
AS Ready EC2

37. Recoverability
System Happens to Go Down

38. Monitoring
TroubleShoot
Recoverability
Developer Begins to Troubleshoot

39. TroubleShoot
Recoverability
Do Not Make Developers TroubleShootMonitoring
Do Not Take Long Time to Get it Recovered

40. Restart
Recoverability
Make System Recovery Easier
“AS Ready”
Stateless + AutoStart
Monitoring

41. Replicability
Easy to Clone a System
CloudFormation Elastic Beanstalk CodeDeploy

42. Replicability
Production
Only Production Environment Necessary at the Beginning

43. Production Staging Integration StressTest Development
Replicability
Multi-Environments Required as We Go

44. Replicability
Production Staging Integration StressTest Development
Make Cloning System Easy

45. Portability
From IP-based to“Owned”Name-based
Route53

46. Portability Users
System Needs to Connect with lots of Endpoints

47. Portability Users
System Needs to 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 Endpoints for Maximum Flexibility
static.xxx.uniqlo.com

49. Users
org.xxx.uniqlo.com
Portability
Easy System Update with Blue-Green Deployment

50. Visibility
Collect as Much Data as Possible
ConfigCloudWatch CloudTrail

51. Visibility Users
Modern System Consists of Full-Managed Services

52. Users
Visibility
Difficult to Figure out Root Cause

53. Users
Visibility
Difficult to Figure out Root Cause
Not Everything under your Control on Cloud

54. Monitoring
Visibility
Collect as Much Data as Possible

55. Do NOT Carry Over
Enterprise Best Practice to Cloud

56. Agenda
1. AWS at FR
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 for Global Service Distribution

58. Production
Staging
Development
Management
4 VPCs in Each Region
Region

59. Production
Staging
Development
Management
B2C/B System Residing Together, Each VPC Completely Isolated
Region

60. Production
Staging
Development
Management
Management VPC Reachable to All VPCs
Region

61. Production
Staging
Development
Management
10G x 2
1G x 2DX for Only System Connection
Direct Connect

62. Production
Staging
Development
Management
10G x 2
1G x 2
Customers
Employees
Developers
Access

63. Management
Production
Staging
Development
Same VPC Design across 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. 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 VPC Peering

65. Management
Production
Staging
Development
Mesh Topology for High 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 Connection with VyOS
VyOS
VyOS
VyOS
VyOS
VyOS
VyOS
VyOS
VyOS

67. 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
VyOS
VyOS
VyOS
VyOS
VyOS
VyOS
VyOS
VyOS
Difficult to Maintain Configuration

68. 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
VyOS
VyOS
VyOS
VyOS
VyOS
VyOS
VyOS
VyOS
Orchestration for Auto Configuration with Serf

69. Management
Production
Staging
Development
Access from Consumers
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
Users Users
Users

70. Management
Production
Staging
Development
Access from Developers
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
Developers Developers
Developers

71. Public(DMZ)
Private
Secure
3 Segments in Each VPC
VPC

72. Public(DMZ)
Private
Secure
Access Control by NACL
VPC

73. Public(DMZ)
Private
Secure
Hosting in Appropriate Segment
VPC

74. Agenda
1. AWS at FR
2. Cloud Design Strategy
3. Global Network Design
4. Enterprise Cloud Strategy

75. Quick Decision Making for AWS Migration
2014/3:
2014/4-10: Verification & Adaptation
2014/11: Director & CIO Approvals
2014/12: CEO Approval

76. Current Enterprise AWS Architecture
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 Shift Required -Network

79. Encryption & Rights Management
Real-Time Monitoring & Treatment
Paradigm Shift Required -Security

80. Fast Retailing IT Team
Direction towards 2020

81. 12,500
25,000
37,500
50,000
1992 1994 1996 1998 2000 2002 2004 2006 2008 2010 2012 2014 2016 2018 2020
(JPY 100M) Group Revenue

82. Disrupt Traditional Enterprise Systems

83. In-House Development

84. Open Source

85. Now Hiring!
http://www.fastretailing.com/employment/career/jp/fr/it/