Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Infrastructure in LINE / LINE Campus Talk in Ho...
Search
LINE Developers
March 25, 2019
Technology
1
230
Infrastructure in LINE / LINE Campus Talk in Hong Kong by Yoshihiro Saegusa
25.03.2019 Campus Talk in HKUST, CUHK
26.03.2019 Campus Talk in HKU
Presented by Yoshihiro Saegusa
LINE Developers
March 25, 2019
Tweet
Share
More Decks by LINE Developers
See All by LINE Developers
LINEスタンプのSREing事例集:大きなスパイクアクセスを捌くためのSREing
line_developers
3
2.3k
Java 21 Overview
line_developers
6
1.2k
Code Review Challenge: An example of a solution
line_developers
1
1.4k
KARTEのAPIサーバ化
line_developers
1
550
著作権とは何か?〜初歩的概念から権利利用法、侵害要件まで
line_developers
5
2.2k
生成AIと著作権 〜生成AIによって生じる著作権関連の課題と対処
line_developers
3
2.2k
マイクロサービスにおけるBFFアーキテクチャでのモジュラモノリスの導入
line_developers
9
3.6k
A/B Testing at LINE NEWS
line_developers
3
1k
LINEのサポートバージョンの考え方
line_developers
2
1.3k
Other Decks in Technology
See All in Technology
JTCにおける内製×スクラム開発への挑戦〜内製化率95%達成の舞台裏/JTC's challenge of in-house development with Scrum
aeonpeople
0
210
今!ソフトウェアエンジニアがハードウェアに手を出すには
mackee
12
4.7k
「どこから読む?」コードとカルチャーに最速で馴染むための実践ガイド
zozotech
PRO
0
290
実践!カスタムインストラクション&スラッシュコマンド
puku0x
0
370
20250910_障害注入から効率的復旧へ_カオスエンジニアリング_生成AIで考えるAWS障害対応.pdf
sh_fk2
3
240
COVESA VSSによる車両データモデルの標準化とAWS IoT FleetWiseの活用
osawa
1
270
人工衛星のファームウェアをRustで書く理由
koba789
14
7.7k
自作JSエンジンに推しプロポーザルを実装したい!
sajikix
1
170
なぜテストマネージャの視点が 必要なのか? 〜 一歩先へ進むために 〜
moritamasami
0
220
「Linux」という言葉が指すもの
sat
PRO
4
120
Function Body Macros で、SwiftUI の View に Accessibility Identifier を自動付与する/Function Body Macros: Autogenerate accessibility identifiers for SwiftUI Views
miichan
2
180
「何となくテストする」を卒業するためにプロダクトが動く仕組みを理解しよう
kawabeaver
0
390
Featured
See All Featured
[RailsConf 2023] Rails as a piece of cake
palkan
57
5.8k
Cheating the UX When There Is Nothing More to Optimize - PixelPioneers
stephaniewalter
285
13k
個人開発の失敗を避けるイケてる考え方 / tips for indie hackers
panda_program
112
20k
Scaling GitHub
holman
463
140k
Designing for humans not robots
tammielis
253
25k
The Art of Delivering Value - GDevCon NA Keynote
reverentgeek
15
1.6k
Fantastic passwords and where to find them - at NoRuKo
philnash
52
3.4k
Responsive Adventures: Dirty Tricks From The Dark Corners of Front-End
smashingmag
252
21k
The MySQL Ecosystem @ GitHub 2015
samlambert
251
13k
Visualizing Your Data: Incorporating Mongo into Loggly Infrastructure
mongodb
48
9.7k
YesSQL, Process and Tooling at Scale
rocio
173
14k
Automating Front-end Workflow
addyosmani
1370
200k
Transcript
Infrastructure in LINE LINE Corporation Yoshihiro Saegusa
• Now responsible for infrastructure platform (private cloud) • Joined
NHN Japan in April 2005 as a network engineer • Was responsible for networks and data centers until June 2017 ABOUT ME Yoshihiro Saegusa
LINE Service Architecture Redis HBase Talkserver Object Storage Image,
File, Video VoIP BOT East Asia Users Southeast Asia Users North America Users Gateway(Legy) JP SG US TCP TCP TCP Gateway(Legy) Gateway(Legy)
Physical Infrastructure Internet Datacenter Datacenter Physical Machine Datacenter Interconnect Rack
Load Balancer Router Switch Datacenter Network
Infrastructure Overview Physical Infrastructure Infrastructure Platform Application Application Application Application
Application Application Application Application API CLI WebUI Infrastructure Private Cloud
LINE Infrastructure Scale • 1Tbps+ User Traffic • 40,000+ Physical
Machines • Multiple datacenters in 5+ countries
CHALLENGES ɾɾɾ • 3,200 physical machines (10Gbps NIC) • 16,000
Gbps of capacity • 2N redundancy Network POD Server ToR Distribution switch POD Scale • Network bottleneck • Inefficient architecture
SOLUTIONS No bottleneck with CLOS network architecture ɾɾɾ ɾɾɾ Non-blocking
large-scale network POD 7,200 physical machines Server Top of Rack (ToR) Leaf Spine 72,000Gbps capacity
CLOS NETWORK EXAMPLE 2 Network PODs with 948 Switches 180
server racks (7,200 servers) 180 server racks (7,200 servers)
• applications running on private cloud • scale is a
root of problems • keep improving physical infrastructure SUMMARY