Moving From Legacy
Infrastructure to Kubernetes
Luka.Huang@mopcon 2020
Slide 2
Slide 2 text
Self Intro
• Luka Huang
• Senior Backend Developer
works for Splashtop
Slide 3
Slide 3 text
Self Intro
• Luka Huang
• Senior Backend Developer
works for Splashtop
• Medium - Luka Huang
Slide 4
Slide 4 text
Self Intro
• Luka Huang
• Senior Backend Developer
works for Splashtop
• Medium - Luka Huang
• A Curator of StarBugs Weekly
Slide 5
Slide 5 text
Self Intro
• Luka Huang
• Senior Backend Developer
works for Splashtop
• Medium - Luka Huang
• A Curator of StarBugs Weekly
• Creator of CodeShiba
https://www.facebook.com/CodeShiba
Slide 6
Slide 6 text
Career
1. Web Developer
( Ruby on Rails + Vue.js)
2. Backend Developer
3. Interested in DevOps
( Terraform / Docker / Kubernetes … etc)
Slide 7
Slide 7 text
Involve in Large-scale System
1. It’s exciting
2. Knowledge is important
3. Can earn more money
Outline
• Why we move to Kubernetes ?
• Introduction to Kubernetes & IAC
• Move legacy infrastructure to K8s
• Legacy infrastructure vs Legacy Code
• Talking about 10x Engineer
• Conclustion
Slide 12
Slide 12 text
Why we move to Kubernetes ?
為什麼要使⽤ Kubernetes ?
Slide 13
Slide 13 text
過得好好的,為什什麼要⽤用 K8S ?
Slide 14
Slide 14 text
契機
Slide 15
Slide 15 text
啟動歐洲區
Slide 16
Slide 16 text
如果要擴展歐洲業務,
要建立⼀一個獨立的系統
Slide 17
Slide 17 text
GDPR
Slide 18
Slide 18 text
GDPR
Slide 19
Slide 19 text
好嚴格阿!
Slide 20
Slide 20 text
⽤用原來來的架構再搭⼀一套不好嘛?
Slide 21
Slide 21 text
Single system
Infrastructure Layer (EC2、VPC、RDS … etc)
Application Layer(API, Web, Worker, … etc )
Testing by QA
Slide 22
Slide 22 text
Clone the entire system
2 * Infrastructure Layer (EC2、VPC、RDS … etc)
2 * Application Layer(API, Web, Worker, … etc )
2 * Testing by QA
The new system is 90% the same as original system.
Slide 23
Slide 23 text
in the code and
in the infrastructure
Don’t Repeat Yourself