Service Orchestration, Old Fashioned Way

Container를 사용하지 않는 Service Orchestration에 대해 소개하고 구현된 결과를 공유합니다.

Transcript

1. Service Orchestration Without Kubernetes Orchestration in Old Fashioned Way 이승(mark) @ LINE 1
2. What We Are Up To reduce development cost reduce operation cost improve service reliability 2
3. Reduce Development Cost make faster, reliable CI tool provide development environment per developer 3
4. Reduce Operation Cost adapt microservice architecture make infra-services as a platform telemetry scaling storage etc 4
5. Improve Service Reliability make services Highly Available by Availability Zones by Federated Remote Regions help developing managed backends redis, centraldogma, etc 5
6. Current Status most of LINE Talk services are using JVM JVM is container without runtime also, there's plenty of platforms which works on non- containerized environment K8S uses container runtime can use VMs by kata containers or firecracker but not native processes actually, they are container-compatible VM runtimes 6
7. Problems on Container: Debug lack of JVM Debuggability inspect processes with jps/jstack take heap dump attach debugger, profiler K8S Debugging is far from complete Debugging with an ephemeral debug container / Kubernetes v1.18 [alpha] 7
8. What We Need Is non-containerized workload orchestration With Kubernetes Integration With Federation To Modernize Legacy Applications without Rewrite 8
9. Containerized Orchestration 9
10. Non Containerized Orchestration .GZ 10
11. DEMO 11