[RakutenTechConf2013] [A-2] Ichiba Architecture
Download as PPTX, PDF1 like2,063 views
Rakuten Ichiba has experienced tremendous growth with over 83 million users and 800 million purchase records, but faces challenges to its legacy architecture. It aims to simplify its architecture by reducing dependencies between applications and the single database. A new approach is being implemented to integrate connections through APIs instead of direct links. This will allow faster and more flexible development while maintaining high performance for merchants and customers on Rakuten Ichiba's online marketplace.
![1. Growth
- Annual GMS [2012]
(GMS=Growth Merchandise Sales)
[billion]
¥14,000
¥12,000
¥10,000
¥8,000
¥6,000
¥4,000
¥2,000
¥0
Rakuten
A
Y
Rakuten Ichiba is No.1 EC Site ! But…
11](https://image.slidesharecdn.com/techconf2013a2-131119011231-phpapp01/85/RakutenTechConf2013-A-2-Ichiba-Architecture-12-320.jpg)
[RakutenTechConf2013] [A-2] Ichiba Architecture
- 2. Growth 1
- 3. Growth • 83,570,000+ users • 800,000,000+ purchase info • 100,000,000+ reviews • 41,000+ merchants • Tremendous amount of search queries • Hundreds GB access log per day etc. 2
- 4. Expand Head Office E-Commerce eBook Travel Other services & businesses Rakuten Institute of Technology Development center Head Office / Regional Headquarters 3
- 5. Unique 『Amazon.comやeBayは、商品を中心に構築されている。 しかし楽天は出店者を中心としたインターネット商店街であり、商品街ではない』 at Ruby World Conference 2010 4
- 6. Synergy 5
- 8. Aside 7
- 9. Rakuten Ichiba’s Challenge Oct/26/2013 Kazuya Sakamoto Group Manager EC Core Platform Group EC Technology Section Rakuten Ichiba Development Department
- 12. 1. Growth - Annual GMS [2012] (GMS=Growth Merchandise Sales) [billion] ¥14,000 ¥12,000 ¥10,000 ¥8,000 ¥6,000 ¥4,000 ¥2,000 ¥0 Rakuten A Y Rakuten Ichiba is No.1 EC Site ! But… 11
- 13. 1. Growth Regular maintenance : 7hour/month 12
- 15. 1. Growth Item ( Get ) Order ( put ) Regular maintenance × × Item Information Order Information Ichiba system was dependent on DB! 14
- 16. 1. Growth Item ( Get ) Basket ( put ) ○ ○ item data cache 180,000,000 item basket data cache 3,000,000 order Item Information Order Information × × 15:00- adopt a Ichiba’s Technology” 5F Ichiba “Rakuten redundant architecture! 15
- 18. 2. Expand Orders are shipped to over 140 countries (2013/07 – 2013/09) 17
- 19. 2. Expand Do you know Micronesia ? 18
- 20. 2. Expand Development Key Issue 1. Shipping - International Destinations 2. Japan Ichiba Item data - Legacy Issue ? 19
- 21. 2. Expand 1. International Destinations → System Association (2012/08) 20
- 22. 2. Expand 2. Japan Ichiba Item Data Legacy Issue EUC DB Size : 3.4 TB Table : 100 Record : 4 Billion 21
- 23. 2. Expand 2. Japan Ichiba Item Data Legacy Issue → Fixed (2013/09) DB EUC New DB UTF We changed character encoding in 2013/09! 22
- 25. 3. Unique Rakuten consist over 40,000 merchants! 24
- 26. 3. Unique + Connect our system to Rakuten system! - payment - item registration + Improve own operation - Own system is nothing - There is no money for make own system + Several requirement - reduce many inquiry - How to input a correct genre? 25
- 27. 3. Unique Add function in RMS 26
- 28. 3. Unique API 3rd party Add function in RMS 27
- 29. 3. Unique Rakuten Summit Rakuten Ichiba Development members joined! 28
- 30. 3. Unique We support merchants with 79 vendors (3rd-party) ! 29
- 31. 3. Unique Rakuten EXPO/Conference Rakuten Ichiba Development members joined! 30
- 33. 4. Synergy 32
- 34. 4. Synergy Ichiba Policy - Keep Service - Speed!! Speed!! Speed!! - Make More Function/Relation 33
- 35. 4. Synergy ( 2013/09 ) I think we prioritized “Speed!!” excessively. 34
- 36. 4. Synergy Ichiba Policy - Keep Service → Be Difficult to Maintain - Speed!! Speed!! Speed!! → Slow!! - Make Many Function/Relation → Make A Few Function/Relation 35
- 37. 4. Synergy Technical Issue - A large number of dependent ( Node=755, Edge=1,233 ) - Anything connect DB ( 1DB ⇔ 66 Application ) - Diverse version ( OS, MW, programing language, script ) etc. 36
- 38. 4. Synergy Case 1 Merchant / Consumer Front App A API Data App B App C App D API α DB If we need to change our database… 37
- 39. 4. Synergy Case 1 Merchant / Consumer Front App A API Data App B App C App D API α DB We have to modify & test many applications. 38
- 40. 4. Synergy Case 1 Merchant / Consumer Front App A API Data App B App C App D API α DB We will integrate many connection by making API. 39
- 43. 0. Extra Load to 2020 “Legacy Architecture” → “Next Architecture” Yasutake※1 Tanaka※2 Kurozumi※2 ※1 Senior Executive Officer ※2 Executive Officer 42
- 44. 0. Extra Let’s make Rakuten’s history together !! http://corp.rakuten.co.jp/careers/engineer/ 43