Platform Engineering at Mercari (Platform Engineering Kaigi 2024)

https://www.cnia.io/pek2024/sessions/768e0788-00cc-4055-88d2-27e32730b035/

Transcript

1. Platform Engineering at Mercari Platform Engineering Kaigi 2024
2. Taichi Nakashima @deeeet / @tcnksm VP of Platform Engineering
3. Agenda
 • Overview Of Mercari Developer Platform • How did we evolve Platform Engineering? • Future of Platform Engineering at Mercari
4. Overview of Mercari Developer Platform
5. Mission of Platform Engineering at Mercari
 Providing core infrastructure, toolings and workflows for Mercari Group developers so that they can deliver new value and experience to Mercari customers quickly and reliably.
6. Mission of Platform Engineering at Mercari
 Providing core infrastructure, toolings and workflows for Mercari Group developers so that they can deliver new value and experience to Mercari customers quickly and reliably.
7. Platform
8. Mission of Platform Engineering at Mercari
 Providing core infrastructure, toolings and workflows for Mercari Group developers so that they can deliver new value and experience to Mercari customers quickly and reliably.
9. Build Test Deploy Operate Infrastructure Network Interface Documentation On-support Production readiness check Service catalog Template project Language package/library Protobuf management CI platform QA environment & automation Cloud administration Kubernetes administration Terraform & Kubernetes monorepo CDN administration Cloud & physical network Service mesh Delivery platform Experimentation platform Supply Chain Security protection Delivery configuration management Observability platform Production access managements
10. Service C Service D Service B Service E Service A Mercari, Merpay, Hallo services Google Kubernetes Engine 200+ Microservices 4000+Kubernetes Pods 3 main business
11. How did we evolve Platform Engineering?
12. How we evolve Platform Engineering?
 • Startup phase (2017-2020) • Expansion phase (2020-2024)
13. Startup Phase 2017-2020
14. Why Platform Engineering?
15. Microservices architecture migration
16. QA team SRE team Test Deploy Operate Build Monolith Backend Team
17. QA team SRE team Test Deploy Operate Build Monolith Backend A Team Backend B Team Backend C Team
18. Product A Team QA team SRE team Build Service A Product B Team Build Service B Product C Team Build Service C Test Deploy Operate
19. QA team SRE team Test Deploy Operate Product A Team Product B Team Product C Team Build Service A Build Service B Build Service C
20. Test Deploy Operate Test Deploy Operate Test Deploy Operate Product A Team Product B Team Product C Team Build Service A Build Service B Build Service C
21. Test Deploy Operate Test Deploy Operate Test Deploy Operate Platform Platform Team Product A Team Product B Team Product C Team Build Service A Build Service B Build Service C
22. How did we approached initial development?
23. Start from “Collaboration”
24. Collaboration X-as-Service / Self-service Product Teams Platform Team
25. Old Infrastructure Monolith System
26. API Gateway New Platform Old Infrastructure Monolith System Service A
27. API Gateway Listing New Platform Old Infrastructure Monolith System
28. API Gateway Listing Merpay API New Platform Old Infrastructure Monolith System
29. Start from “Collaboration”
 • Easy Discovery: Platform team can actually facing the issue as Stream-aligned team and understand it clearly • Easy Validation: Platform team can get feedback directly from the team and iterate quickly • Business contribution: Platform team can produce some business value when collaboration is completed
30. How we evolve Platform Engineering?
 • Startup phase (2017-2020) • Expansion phase (2020-2024)
31. Expansion Phase 2020-2024
32. Expansion Phase
 • Updating Platform Engineering Organization • Moving toward Single Platform
33. Updating Platform Engineering Organization
34. Problems raised by the platform team at the team off-site
35. Strategies
 • Teams for Software Development Lifecycle (SDLC) • Platform teams for platform teams • Team for Platform interface
36. Build Test Deploy Operate
37. Build Test Deploy Operate Platform DX Observability CI/CD
38. Platform Infra Network Infrastructure Network Build Test Deploy Operate Platform DX Observability CI/CD
39. Team Team Team Team Team Team
40. Component Component Component Component Component Component
41. Component Component Component Component Component Component Product B Team Product C Team Product A Team
42. Team Team Team Team Team Team Platform Product B Team Product C Team Product A Team
43. Team Team Team Team Team Team Platform Platform DX • Documentation system • Support ticket system • Abstraction system Product B Team Product C Team Product A Team Interface
45. https://www.flickr.com/photos/docsearls/5500714140/
46. Expansion Phase
 • Updating Platform Engineering Organization • Moving toward Single Platform
47. Moving toward Single Platform
48. Platform
49. MK Platform FT Platform Hallo Platform MK Platform Team FT Platform Team H Platform Team
50. Moving toward Single Platform
 • Migrating legacy systems • Enabling new business
51. Migrating legacy systems
52. API Gateway New Platform Old Infrastructure Monolith System
53. API Gateway New Platform Monolith System
54. Migrating legacy system
 • Removing additional operation cost • Assigning the members to the new areas • Using the same tooling for legacy system development
55. Moving toward Single Platform
 • Migrating legacy systems • Enabling new business
56. Enabling new business
57. New business = New technologies?
58. Isolation?
59. 💪
60. https://www.flickr.com/photos/alasdairjmckenzie/8154861542/
61. How we evolve Platform Engineering?
 • Startup phase (2017-2020) • Expansion phase (2020-2024)
62. Future of Platform Engineering at Mercari
63. Two Dimensions of Platform evolution
 • Horizontal ◦ Expanding our capability for new opportunities ◦ e.g., Enabling new business, migrating legacy system • Vertical ◦ Improving & enhancing existing capabilities ◦ e.g., Migrating self hosted CI system
65. Moving toward “Global” Single Platform
66. How did we evolve Platform Engineering?
67. Thank you