[EN] Mercari Tech Conf 2017 Keynote

Transcript

1. Mercari Tech Conf 2017 Head of Engineering, Souzoh Tatsuya Tsuruoka Keynote
2. 4 years since the app release 7.5m downloads (Japan/US) Monthly GMV over 10b yen 3 regions Over 100 software engineers
3. How Mercari was Created
5. Have too many things ↓ How to use them? ↓ Sell to someone else Smartphone usage rising worldwide A new era: anyone can use a smartphone app to sell things to other people Mercari’s Business Concept
6. To realize this concept, we must keep in mind… Move faster than the competition Make use of our late start 2 How to list items: Anyone should be able to list an item easily 1
7. App DB Master DB Slave App Backend read/write replication read App App LB LB Cache NDB NDB NDB NDB MySQL NDB Cluster Infrastructure? For example, a common structure
8. Issue: Infrastructure ★Final Decision Everything on 1 high-end server From the regular minutes on April 6th, 2013
9. Architecture and Technology Stack Server Client ・HTTPS + JSON API ・MVC ・Linux + Apache + MySQL5.6 + PHP5.3 ・Dedicated server: 6core * 2CPU, RAM64GB, SSD200GB ・Provides 95 types of API ・iOS/Android native + WebView DB Master App
11. Feature #751 Considering a search feature - look at usage by Shintaro Yamada, 2013/06/01 Why No Search Feature? Users No hits = bad experience Developers Building a search system takes time
12. A B
13. A 1200x1200 JPEG Quality 100 ~1MB B 612x612 JPEG Quality 80 48KB
14. HTML5 Native Users Developers ✕ ◯ ◯ △ Make timeline native
15. May 2014 56 tickets involving load issues Dealt with in two months Full-blown load tests Introduced cache TV Commercials
16. ・Single infrastructure ・No search function ・Optimizing images ・Making timeline native ・Load issues for the TV ad ・...And many more... Hurdles Understand the business concept 　↓ Decide which issues to solve 　↓ Make bold decisions The start-up phase
17. Mercari Tech Conf 2017 VP of Engineering Sotaro Karasawa Scalable and Elastic Engineering Team
18. Development Team Structure in Each Region San Francisco London Tokyo
19. US Office
20. UK Office
21. Mercari’s Expansion Strategic expansion into new regions Continued focus on Mercari UX improvements Creation of new platforms
22. Growth of the Dev Team Structure
23. Monthly API Project Insights on 2,500+ Commits 400+ Merged Pull Requests 120+ Active Branches
24. Continuously Evolving with Expansion
25. Continuously Evolving Souzoh • Birth of a new subsidiary to develop and run new enterprises • CtoC in new areas, expanding Mercari to specialize in certain areas • Released new services like Atte, Kauru, Maisonz Small organization, delegation of authority A completely new challenge Making a platform
26. Continuously Evolving US Growth • Continue to evolve on the organization side to grow the business • Help from Japan at first • Currently localizing the organization Help from Japan at first Dealing with local demands Gradually localizing
27. Continuously Evolving Client Source Code Fork • At first, to optimize resources, used multiple binaries with one source • Different cultures of different countries • Developed to meet users’ needs • So small teams can make decisions quickly Merits to sharing at first Delegation of authority Optimizing UI/UX
28. JP US UK
29. Mercari’s Dev Team Structure
30. Mercari’s Project Team JP US UK SRE (Site Reliability Engineer) QA/SET (Software Engineer in Test) Seller UX PJ Manager Designer Server Side iOS Android Frontend ... Growth PJ Manager Designer Server Side Frontend ... ... Search PJ Manager Designer Server Side iOS Android ... ... ... UK Manager Designer Server Side iOS Android ...
31. Cross-Region Engineering Team Supporting the Project Team QA/SET (Software Engineer in Test) Engineering Operations SRE Site Reliability Engineer Provides a sense of reliability (“can always use the product comfortably and safely”) to users. Not just in charge of the infrastructure; responsible for reliability as well. Responsible for the quality of software. In the Project Team, QA does manual tests and SET does automation and provides environments. Responsible for developing the team structure and hiring. Takes the lead for hiring, internships, branding, and presence expansion.
32. Mercari’s Values Go Bold All for One Be Professional
33. Mercari’s Values Hey guys, we changed the WiFi settings on the Souzoh side of the office, but it looks like it’s got a bit unstable. Went ahead and changed the settings back! Really sorry for the inconvenience.
34. Mercari’s Values Go Bold All for One Be Professional
35. Scalable and Elastic
36. Scalable and Elastic Elastic Scalable The number of engineers will grow to 500, 1000, even 2000 people globally Trends change daily • Speed and efficiency of development shouldn’t drop • The product quality shouldn’t drop • Should bring out 100% of each individual’s abilities • Should be able to commit right away even if moved to another team • Should put people on areas that need more power to raise the development speed Both new and experienced engineers should be able to grow naturally
37. Mercari Tech Conf 2017 CTO Suguru Namura Technology Strategy At Mercari
38. Current State of Mercari Engineering
39. Japan ・Introducing new tech (like Mercari Channel) ・Increased complexity from platformization ・Scaling of databases ・Optimization of content distribution ・Better UX through improved search precision
40. US ・Growth and feature improvements ・Architecture reforms and code refactoring ・Adding US-specific features ・Automation of trouble prevention and fraud detection
41. UK ・Still in start-up phase ・Implementing UK-specific features ・Very diverse team
42. Mercari Code of Engineering Conduct
43. -1- Ownership
44. Microservices Architecture
45. Low onboarding costs Ownership Rapid deployment Simple testing Small teams Team discretion Clear areas of influence
46. Ownership Low onboarding costs Rapid deployment Simple testing Small teams Team discretion Clear areas of influence
47. Microservices Monolithic
48. How are you handling the transition to microservices?
49. Our approach to microservices Mercari API MySQL Solr
50. Our approach to microservices Mercari API Database Solr API Gateway
51. Our approach to microservices Mercari API MySQL Solr API Gateway Search Service Offer Service Search SaaS Cloud Spanner
52. Our approach to microservices API Gateway Search Service Offer Service Search SaaS Cloud Spanner
53. -2- Automation, Karakuri
54. Examples of automation in action Go Bold Bot ▪ Bot that handles Mercari’s 400+ deploys each month
55. Examples of automation in action “Tonkotsu” bot Account Bot (↑↑This is a bot that checks the App Store/Google Play to see when our updates have been published)
56. Examples of automation in action e2e Test Platform
57. An environment that encourages Karakuri Problem occurs ↓ Look for the cause ↓ Think of ways the problem could have been prevented ↓ Implement the solution from above ↓ Now the problem won’t happen, even if we mess up Mercari
58. -3- Progressive
59. Always looking for the best solutions Progressive Web Apps
60. New Technology
61. AI & Machine Learning
62. Mercari Machine Learning Use Cases Already implemented Testing and researching ・Price suggestions based on text input ・Improved search results through search intent predictions ・Suggestions based on demographic/interests ・Productivity support for CS team ・Image- and text-based price suggestions ・Replies to tier 1 CS inquiries ・Optimization of onboarding process ・Automated detection of illicit listings ・Image-based automated recognition of category/brand/color
63. Machine Learning Platform
64. Machine Learning Platform Overview (Simplified) Training Manager Training Definition Training Program Model Storage API Serving Cluster Training Cluster
65. Blockchain
66. C2C Marketplace × Blockchain = ?
67. Code of Engineering Conduct Ownership Automation & Karakuri Progressive