[rakutentechconf2013] [a-4] the approach of event in japan ichiba

87
The approach of Big Event In Japan Ichiba Vol.01 Oct/26/2013 Yusuke Kobayashi Group Manager Mall Group, Japan Ichiba Section Rakuten Ichiba Development Department, Rakuten, Inc. http://www.rakuten.co.jp/

Upload: rakuten-inc

Post on 23-Jan-2015

632 views

Category:

Technology


0 download

DESCRIPTION

Rakuten Technology Conference 2013 "The approach of Big Event in Japan Ichiba" Yusuke Kobayashi, Osamu Iwasaki, Makito Hashiyama (Rakuten)

TRANSCRIPT

Page 1: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

The approach of Big EventIn Japan Ichiba

Vol.01   Oct/26/2013Yusuke Kobayashi

Group ManagerMall Group, Japan Ichiba SectionRakuten Ichiba Development Department, Rakuten, Inc.http://www.rakuten.co.jp/

Page 2: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

2

Index

Big Sale in Ichiba

Page 3: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

3

Introduce Me

Yusuke Kobayashi

Group ManagerJapan Ichiba Section Japan Mall Group

Rakuten Ichiba Development Department• Joined in 2005.• Fist career in Rakuten was Infoseek.• Transferred to Ichiba from 2009.

MALL RMS IBS IBE

Japan Ichiba Section

Page 4: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

4

Index

1.Scale of Big Sales - Huge Traffic Scale, Amazing Sales.

2.History of success - Share how we could improve our services.

3.Case study - Show trouble case and explain the countermeasure. -- Checkout System -- Infrastructure(Cloud Environment/Network)

Page 5: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

5

Shopping Marathon

Shop around points

Page 6: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

6

Super Sale

Half Price Items, Point, Topic Items

Page 7: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

7

Victory Sale

77%Off, Half Price,1001 yen items

Page 8: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

8

1.Scale of Big Sales - Huge Traffic Scale, Amazing Sales.

2.History of success - Share how we could improve our services.

3.Case study - Show trouble case and explain the countermeasure. -- Checkout System -- Infrastructure(Cloud Environment/Network)

Page 9: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

9

1.Scale of Big Sale

15 Billion Sales per day

Page 10: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

10

1.Scale of Big Sale

Victory Sale5% traffic of entire Japan!!

Page 11: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

11

Usual

1.Scale of Big Sale

Comparison of order numbers between big sale and usual.

Sale

0 2 4 6 8 10 12 14 16 18 20 22 24 26 28 30 32 34 36 38 40 42 44 46 48 50 52 54 56 58

Time(1hour)

Order Number

Page 12: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

12

1.Scale of Big Sales - Huge Traffic Scale, Amazing Sales.

2.History of success - Share how we could improve our services.

3.Case study - Show trouble case and explain the countermeasure. -- Checkout System -- Infrastructure(Cloud Environment/Network)

Page 13: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

13

Monitoring by 100 DU members

Page 14: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

14

Our Energy!

Page 15: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

15

2. History

2012/03/04 00:00 – 2012/03/04 23:59

2012/06/03 00:00 – 2012/03/06 01:59

2012/12/02 00:00 – 2012/12/04 01:59

2013/03/03 00:00 – 2013/03/05 01:59

2013/06/02 00:00 – 2013/06/05 01:59

2013/09/01 00:00 – 2013/09/04 01:59

2013/09/27 00:00 – 2013/09/30 01:59

Page 16: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

16

2012/03 – Super Sale

24h LimitedHalf Price

Special Items

TV CommercialTrain AD

Page 17: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

17

Top PageEvent Page

Search

IDAD

Entry

ItemPage

BookmarkPurchaseHistory

Review

Checkout

Search Engine

2012/03 – Super Sale

Point Coupon

Page 18: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

18

2012/03 – Super Sale

Page 19: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

19

2012/03 – Super Sale

Page 20: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

20

2012/03 – Super Sale

Almost all services Delayed. Huge traffic. Application high load. Over band frequency. DB high load. NFS high load.

Mass Media powerwas so huge.

Page 21: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

21

2012/03 – Super Sale

Just only Restart and Reboot. Change Apache Configuration. Restart Apache. Reboot physical servers.

Contents Delete Access Control by Creative Web Design team.

Page 22: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

22

2012/03 – Super Sale

Countermeasure Enhance Web/Apps/NW/DB Servers. Band width limitation Tuning Middleware configuration. Decrease traffic. Contents Control. Web Front Speed UP.

Page 23: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

23

2012/06 – Super Sale

!?

Page 24: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

24

Bookmark

2012/06 – Super Sale

Top PageEvent Page

Search

IDAD

Entry

ItemPage

PurchaseHistory

Review

Checkout

Search Engine

Point Coupon

Page 25: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

25

2012/06 – Super Sale

ID went down and Checkout delayed.

We expanded the period due to big troubles.

Page 26: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

26

ID Service

0

10,000

20,000

30,000

40,000

50,000

60,000

6/222:00

6/30:00

6/32:00

6/34:00

6/36:00

6/38:00

6/310:00

6/312:00

6/314:00

6/316:00

6/318:00

6/320:00

6/322:00

6/40:00

6/42:00

#login 20120603

#login 20120527b

#login 20120304b

0

50000

100000

150000

200000

250000

300000

350000

400000

20

12

/6

/3

0:0

0

20

12

/6

/3

0:3

0

20

12

/6

/3

1:0

0

20

12

/6

/3

1:3

0

20

12

/6

/3

2:0

0

20

12

/6

/3

2:3

0

20

12

/6

/3

3:0

0

20

12

/6

/3

3:3

0

20

12

/6

/3

4:0

0

20

12

/6

/3

4:3

0

20

12

/6

/3

5:0

0

20

12

/6

/3

5:3

0

20

12

/6

/3

6:0

0

20

12

/6

/3

6:3

0

20

12

/6

/3

7:0

0

20

12

/6

/3

7:3

0

20

12

/6

/3

8:0

0

20

12

/6

/3

8:3

0

20

12

/6

/3

9:0

0

20

12

/6

/3

9:3

0

20

12

/6

/3

10

:00

20

12

/6

/3

10

:30

20

12

/6

/3

11

:00

20

12

/6

/3

11

:30

20

12

/6

/3

12

:00

20

12

/6

/3

12

:30

20

12

/6

/3

13

:00

20

12

/6

/3

13

:30

20

12

/6

/3

14

:00

20

12

/6

/3

14

:30

20

12

/6

/3

15

:00

20

12

/6

/3

15

:30

20

12

/6

/3

16

:00

20

12

/6

/3

16

:30

20

12

/6

/3

17

:00

20

12

/6

/3

17

:30

20

12

/6

/3

18

:00

20

12

/6

/3

18

:30

20

12

/6

/3

19

:00

20

12

/6

/3

19

:30

20

12

/6

/3

20

:00

20

12

/6

/3

20

:30

20

12

/6

/3

21

:00

20

12

/6

/3

21

:30

20

12

/6

/3

22

:00

20

12

/6

/3

22

:30

20

12

/6

/3

23

:00

20

12

/6

/3

23

:30

20

12

/6

/4

0:0

0

20

12

/6

/4

0:3

0

20

12

/6

/4

1:0

0

20

12

/6

/4

1:3

0

20

12

/6

/4

2:0

0

20

12

/6

/4

2:3

0

ID3 2/3

ID3 1/4

0:00AMSun 6/3

2:00AMMon 6/4

Fig.1: # of Login Successes

Fig.2: # of DB Connection Errors

[0:00-1:09]Just after the launch of Super Sales, DB Connection Errors occurred because of the users' massive accesses. Some of the users experienced connection errors. Errors automatically solved with users’ access decrease.

[20:20 - 0:34]Serious DB Connection Errors occurred because of the users' massive accesses. Critical user login failures by reboots of the ID services, limitation of Login, etc.

[22:37 - 0:42]Ichiba stopped using ID service. Purchases were only processed by non-members.

[23:15 - 23:40]ID service stopped because of server reboot and server down.

[Sun 6/3] Super Sale (2nd) this time[Sun 5/27] Ordinary Sunday[Sun, 3/4] Super Sale (1st) last time

[0:41]DB Connection Error terminated just after stopping batch program for Fraud Access Management running every 10 min. Users became login smoothly.

LoginSuccess

Page 27: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

27

ID Service

ID Service had serious DB connection errors

during the following time period.(1) 0:00 - 1:09 (Sun, 6/3-2012)

Just after the launch of Super Sales, DB Connection Errors occurred because of the users' massive accesses.Some of the users experienced connection errors.

# of DB Connection Errors = 160,497 (in 10 min) (ref. # of Login Successes = 2,167,126)

(2) 20:20(Sun, 6/3-2012) - 0:34 (Mon, 6/4)Serious DB Connection Errors occurred because of the users' massive accesses. Critical user login failures by reboots of the ID services, limitationof Login, etc.

22:37-0:42, Ichiba stopped using ID service. Purchases were only processed by non-members.# of DB Connection Errors = 4,063,667 (in 4 hours 15 min)

Impacted to entire Rakuten Group.

Page 28: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

28

Checkout

Web

Web

Web

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

Web

Web

Web

Web

Web

Web

APP

APP

APP

APP

APP

APP

APP

API

Enhance the instances

Enhance the instances

Change the configuration of thread

Change the threshold

Page 29: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

29

Have no time!!!!

Page 30: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

30

2012/06 – Super Sale

Countermeasure for next Super Sale. Migration of DB servers.(ID) Enhancement Applications Servers.

-> Transfer to Cloud environment not using Physical servers.

Load Test on Production environment.

-> We did on staging environment, but it was not enough.• User Numbers• Item Numbers• Transaction• Server Spec

Different between staging and production

environment.

Page 31: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

31

2012/12 – Super Sale

Page 32: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

32

2012/12 – Super Sale

Bookmark

Top PageEvent Page

Search

IDAD

Entry

ItemPage

PurchaseHistory

Review

Cart

Search Engine

Point Coupon

Page 33: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

33

2012/12 – Super Sale

The first peak time -> DownThis was the most high traffic in this year.

Search, Item Page and Checkout were down.

Page 34: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

34

Search

Web

Web

Web

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

Application load was high

The beginning of the first peak time, search applications was high load because the huge traffic came from event contents.-> We enhanced 65ins by using Cloud environment within 4 hours.

The LB which we enhanced was high load.

Search EngineAPP

APP

APP

APP

APP

APP

APP

LB was highEnhance

Page 35: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

35

Item Page

12/02 9:00 pm to 24:00

Disk Util was 100%

Page 36: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

36

Item Page

The connection delayed between App and NFS.

Page 37: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

37

Item Page

We switched to Akamai during peak time. Cache 25min.(by Mikitani-san suggestion.) Inventory data was not updated in real time. The countermeasure of emergency.

Page 38: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

38

Item Page

Page 39: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

39

Checkout

Web

Web

Web

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

APP

Web

Web

Web

Web

Web

Web

APP

APP

APP

APP

APP

APP

APP

API

High Load

Page 40: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

40

2012/12 – Super Sale

Countermeasures for next Continuously doing the load test of checkout system. Need to decrease NFS call numbers in Item Page

system. Transfer to Cloud environment gradually.

Page 41: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

41

Item Page

AppServer Decreasing Unnecessary File Call

Memcached Server Cache more kinds of files.

- Shop data, Layout data. Re-cache anytime whether file is update or not

when cache is expired

Page 42: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

42

Item PageBefore After

30% Down

Page 43: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

43

Checkout

APP

Jmeter

Web

WEB serverAPP

APP server

Cache DataBase

APP

API α APP

API βAPP

API γ APP

API δ

Load Test about 50 times in midnight…

Page 44: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

44

Checkout

We always have so many load tests for checkout systems before Super

Sale.Explain later…by Hashiyama.

Page 45: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

45

2013/03 – Super Sale

Page 46: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

46

2013/03 – Super Sale

Bookmark

Top PageEvent Page

Search

IDAD

Entry

ItemPage

PurchaseHistory

Review

STEP

Cart

Search Engine

BasketAPI Point Coupon

Page 47: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

47

No Trouble!!

Success!!

Page 48: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

48

2013/06 & 2013/09 – Super Sale

No Big Trouble!

Page 49: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

49

From this year…

Page 50: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

50

Victory Sale

Just only 3 weeks for this event preparation..

Page 51: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

51

Victory Sale

1st Spike. From Yahoo!

2nd Spike. Event Started.

3rd Spike. New Paper AD

Page 52: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

52

Victory Sale

Bookmark

Top PageEvent Page

Search

IDAD

Entry

ItemPage

PurchaseHistory

Review

STEP

Cart

Search Engine

BasketAPI Point Coupon

Page 53: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

53

Top & Search

Top Page

Search

The traffic was higher more than we expected.Around 6 or 7 times!!!!

The countermeasure for this was just enhancement.

Page 54: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

54

1.Scale of Big Sales - Huge Traffic Scale, Amazing Sales.

2.History of success - Share how we could improve our services.

3.Case study - Show trouble case and explain the countermeasure. -- Checkout System -- Infrastructure(Cloud Environment/Network)

Page 55: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

55

About Me

Name Makito Hashiyama(@capyogu)

Role Team manager of APIs for Rakuten Ichiba

Recent activity GlassFish Community Feedback @ JavaOne 2013

Contact [email protected]

Page 56: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

56

Overview of Rakuten Ichiba Checkout

Architecture Behaves like a service bus based on SOA Calls more than 15 external APIs and mashes up

them, then provides

Scale More than 100 application servers

Checkout

APIKVS

External APIs

Client side

SOAP/REST

Page 57: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

57

Provides over 50 services to client side Get/Set shopper information Get/Set merchant information Validation Update inventory Register order data into DB etc..

Checkout

API

Item API Cart API

Merchant API

Client side

SOAP/REST

Overview of Rakuten Ichiba Checkout

Page 58: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

58

Overview of Rakuten Ichiba Checkout

Stateful API Manage session information instead of client side Creates unique key and manage it with KVS Client side only have to call API with the key

KVSCheckout

API

SOAP/REST

Client side

key value

Key1 Session1

Key2 Session2

Page 59: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

59

Overview of Rakuten Ichiba Checkout

Rakuten Super Sale Biggest online sales in Japan It causes a huge amount of traffic

Performance bottleneck External APIs called by our API were slow down We needed to improve the system at the peak time

delay

Checkout

API

External APISOAP/REST

Slow downDelay

Page 60: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

60

How to execute load test

delay

Checkout

API

External APISOAP/REST

JMeter

Environment On production at midnight Execute over 50 times with JMeter

Test case 100,000 dummy shoppers 1,000,000 dummy items / 6,500 dummy merchant Reproduce sale’s load as much as possible

Page 61: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

61

How to execute load test

APP

Jmeter

Web

WEB serverAPP

APP server

Cache DataBase

APP

API α APP

API βAPP

API γ APP

API δ

As a result, bottleneck moved to APP server

Page 62: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

62

Improvement to handle a huge traffic

Task Queue

Worker Thread

Worker Thread

Worker Thread

Checkout API

Worker Thread

Worker Thread

External APIs

delay

delay

delay

delay

delay

CPU load was high

Client side

Request

Page 63: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

63

Improvement to handle a huge traffic

Task Queue

Worker Thread

Worker Thread

Worker Thread

Checkout API

External APIs

Client side

Request

(1)According to vmstat, ‘run queue’ was very high(2)Decrease worker threads to keep ‘run queue’ low(3)As a result, latency increased but throughput was improved

Page 64: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

64

Improvement to handle a huge traffic

As a result… Checkout API could process over 12,000

transactions / minute We also achieved 30,000 TPM in load test

(Just yesterday we did!!!)

Page 65: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

65

Overview of Rakuten Ichiba Checkout

In the future

Set SLA for each external APIResolve performance issues

Synchronous vs. Asynchronous Upgrade library / middleware / JDK Deep copy(copy constructor vs. serialize)

Page 66: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

66

Self introduction

Vice Group ManagerServer Platform Group / Network administration Group

Global Infrastructure Development Department

And Committee member of JANOG(JApan Network Operators’ Group)

Name : Osamu Iwasaki

Role : Network / Cloud Eng & Mgr

Twitter @osamuiwasakiSkype osamu.iwasaki

Page 67: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

67

Our traffics history

0

20000

40000

60000

80000

100000

120000

140000

160000(Gbps)

Peak traffics at Victory Sales, over 140Gbps which was about over 5% of Japan Internet traffics

Page 68: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

68

Our traffics history

0

20000

40000

60000

80000

100000

120000

140000

160000(Gbps)

Peak traffics at Victory Sales, over 140Gbps which was about over 5% of Japan Internet traffics

Victory Sale

Super Sales

Page 69: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

69

Network traffic trend from 2012/Jan(SS traffic focus)

SuperSale 2012June

2012Dec

2012Mar

2013June

2013Sep

2013Oct(VS)

CDN 60G 78.9G 69.1G 75.8G 73.7G 127.6G

RakutenDC 12.7G 14.2G 12.8G 12.5G 11.7G 12.9G

Total 72.7G 93.1G 81.9G 88.3G 85.4G 140.5G

0

20000

40000

60000

80000

100000

120000

140000

160000(Gbps)

Page 70: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

70

PC/FeaturePhone/Smartphone/Table share by Sales

Mobile traffics increase rapidly!! Almost 50%

Page 71: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

71

Our private cloud history

About 1years ago, we starts from 300VMs.But now, around 10000VMs running for Rakuten Ichiba services. Compared last year is over 30 times !!!

Page 72: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

72

Victory Sale

Just only 3 weeks for this event preparation..

Page 73: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

73

But !!

Page 74: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

74

Our Load Balancers are downed……

Page 75: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

75

What happened at peak time

LoadBalancer-ACPU utilization

Peak TimePeak Time

LoadBalancer-BCPU utilization

Due to heavy traffics at VictorySale start time, CPU load of LoadBalancer rapidly growth……

Page 76: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

76

After the result of re-allocation operation

LoadBalancer-ACPU utilization

LoadBalancer-BCPU utilization

After the VIP re-allocation, we could separate heavy traffics to other LoadBalancer

Page 77: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

77

Our counter action for next Victory sale

ActiveSLB

(Target CPU under 30%)

StandbySLB

(CPU 0%)

VIP Group A

VIP Group B

Internet

Regular time3times peak capable

ActiveSLB

(Target CPU under 15%)

StandbySLB

(Target CPU under 15%)

VIP Group A

VIP Group B

Internet

BigSale time6times peak capable

VIP Group B

3times is not enough for us, 6times we need for the Super/Victory sales.

Page 78: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

78

Next Victory sale ready?

Page 79: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

79

Next Victory sale ready?

Yes, we are ready !!!

Page 80: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

80

Wrap UP

Page 81: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

81

Wrap Up

• Traffic : 5% of entire Japan.• Sales : Over 15B yen/day• Continuously

Tuning/Improvement• Cloud environment

Page 82: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

82

Global Expansion - Super Sale

Page 83: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

83

Worldwide Rakuten Super Sale

In future

Page 84: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

84

And…

Page 85: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

85

Page 86: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

86

Page 87: [RakutenTechConf2013] [A-4] The approach of Event in Japan Ichiba

87

Thank you for listening.

Yusuke Kobayashi

@okoba23

Makito Hashiyama

@capyogu

Osamu Iwasaki

@osamuiwasaki