Micro Service Architect in K8S in ZaloPay Merchant Platform | Châu Nguyễn Nhật Thanh

1. Micro-services in k8s
in ZaloPay Merchant Platform
Châu Nguyễn Nhật Thanh
Head of Merchant Platform
VNG Corp.

2. Content
• About me
• eSale
• Why micro services?
• Why K8s?
• Lesson learned

3. About
- M.Sc Uni Duisburg, Germany
- Tech Lead in VNG (10 years)
- ZingMe
- CSMBoot, CSMPlay, CSM
- GBC
- IoT Lab
- ZaloPay Merchant Platform
(MEP)
- K8S newbie

4. eSale

5. Why Micro-services?

6. Before

7. Before

8. Before
• One big system
• Back Office and Front Office
• BO: Accounting, Report, Card Inventory …
• FO: UserProfile, Sales, Wallet …
• Business logic stays on Store Procedure
• DB using MS SQL

9. Before
• Problems
• Cannot plug more biz
• Hard to scale
• Very hard to maintain
• Totally depends on System Operator

10. After

11. After
https://enternews.vn/media/uploaded/395/2017/07/22/20170517091803-buyt-nhanh-brt.jpg

12. After
• Split into small components
• Frontend: API middle ware
• Backend: Core components such as Wallet, User
Profile, Authentication
• Back office: Accounting, Report, Card Inventory

13. After
• Divide and Conquer
• Easy to scale
• Easy to add more business logic
• Problems
• Communication between components very
complicated
• Very hard to maintain and deploy the services

14. After

15. Why k8s?

16. What is k8s ?
https://d33wubrfki0l68.cloudfront.net/26a177ede4d7b032362289c6fccd448fc4a91174/eb693/images/docs/container_evolution.svg

17. What is k8s ?

18. Why k8s?
• Fix the gap between scaling and maintenance
• Container engine packages your code into images
• k8s deploys your images into the infrastructure
• Convert tasks from Ops to dev
• Automation your deployment through CI/CD scripts
• Everything based on configuration

19. eSale v2

20. eSale v2

21. Lesson learned

22. Multi instances
• Stateful vs stateless
• Internal cache
• Load balancing
• Auto scaling

23. Monitor k8s
• Scaling node
• Kubespray version issue (R&D vs Production)
• Detect node and service problems