Downloaded 39 times
Uploaded byLINE Corporation
B 2 line game cloud - our personal ec2
The document discusses improvements made to a game cloud platform between 2014 and the present. It summarizes key points as follows: 1. In 2014, the platform faced issues serving games globally from a single data center. This motivated the start of the Game Cloud project. 2. Significant improvements were made including using HAProxy for load balancing instead of hardware, establishing points of presence around the world, and improving network architecture to reduce latency. 3. The platform now uses Docker Swarm and keeps its architecture simple and reliable. It also implemented an auto-scaling system called Gearbox to provide high availability at low cost.
More Related Content
Similar to B 2 line game cloud - our personal ec2
![Coded Agents – with UiPath SDK + LangGraph [Virtual Hands-on Workshop]](https://cdn.slidesharecdn.com/ss_thumbnails/codedagentsdeck-251215155422-5497c599-thumbnail.jpg?width=640&height=640&fit=bounds)
B 2 line game cloud - our personal ec2
- 2. Currently on theCloud
- 3. 1 Our situationin 2014 2 How we improved 3 Sweet things 4 More sweet things 5 Future
- 4. 1 Our situationin 2014 2 How we improved 3 Sweet things 4 More sweet things 5 Future
- 5. Our situation in2014 1st gen “HSP” – (2014) from cybercafe/漫画木さ/PC방 platform 2nd gen ECDH-based key exchange Platform Billing/AAA/Monitoring, etc. & Game servers “LGC” – (cloud release) 3rd gen: “Trident” – (current)
- 6.
- 7. Process Dev/QA/Sandbox/REAL… Get VM Get L4binding ACLs/storage, etc. From hours to days…
- 8. Thus, the Game Cloudproject began…
- 9. 1 Our situationin 2014 2 How we improved 3 Sweet things 4 More sweet things 5 Future
- 10. Global In our case GSLB(Global Server Load Balancing) HAProxy instead of hardware L4 Multi-team effort client, server, cloud We get more flexibility less latency
- 11. LINE Global POP NewYork Tokyo Seoul HK Singapole Beijing Frankfurt a a
- 12. Network layer control Highlatency Fit for cloud Global Testing in Thailand TH KR GSLB TH SG KR HAProxy 500 1000 1500 2 12 206 16
- 13. Process Dev Ops Government The structure ofyour organization affects the structure of your software. And vice-versa! DevOps Small StartupCHOOSE
- 14. Process Progressive / Easy,simple Requirements for our new platform : We have many third parties and technology stacks involved... Etc.
- 15. Process For ourselves simple reliablefuture proof
- 16. Process Why not… Docker Swarm orCoreOS Mesos Kubernetes
- 18. Process KEEP THINGS SIMPLEAND RELIABLE! For distributed systems, minimize coordination A good paper: https://blog.acolyer.org/2016/01/19/dcft/ • Polling • 1way dataflow • Idempotency • Commutativity • limited trust
- 19. LGC Story Games plannedfor release were suddenly canceled but we needed to show results! Strong “sales” efforts to release other games on the LGC platform
- 21. Putting Out Fires Therelease was a success,followed by a quick scaling-up, and then our first fires… TECHNICAL Riak fire : the system works with Riak down OE fire: the system works with OE down Hardware and conf fires (TDI! Soon to come!) Full container reboot improved our design through limited trust
- 23. 1 Our situationin 2014 2 How we improved 3 Sweet things 4 More sweet things 5 Future
- 25.
- 26.
- 27. 1 Our situationin 2014 2 How we improved 3 Sweet things 4 More sweet things 5 Future
- 29.
- 30. High availability Low cost Why DoWe Need It?
- 32. How Does ItWork?
- 33. How Did WeBuild it? Data Collector Monitoring API Predicator Metrics Raw Metrics Scaler States Game Cloud API Excute Scaling Gearbox
- 34. Challenges Complex query Plenty ofmetrics records millions of records per day Scalability of the auto-scaling system itself
- 35. Solutions Data Collector Monitoring API Predicator Metrics Metrics Scaler States GameCloud API Excute Scaling Gearbox Module Storage ElasticSearchAdmin Site Strategy Scaler Log Metrics 1.Strategy 2.Metrics { } Predicator Log 1.Strategy 2.Scaler Log
- 36.
- 37.
- 38.
- 39.
- 40. Back to Jojo What’scoming next!
- 41. 1 Our situationin 2014 2 How we improved 3 Sweet things 4 More sweet things 5 Future
- 42. Future QUIC SDN ACL, IP bycontainer, VLAN etc. Cloud storage TDI Distributed GC – link paper DCTCP Image GC
- 43.
- 44.
- 45.
- 46. SDN- Software-Defined Networking Container specificIP ACLs VLANs
- 47. TDI- Test-Driven Infrastructure hardwareOS configuration images backup/ restore Automated testing for Etc. firmware, version, etc.
- 48. Distributed GC Max Avg.GC pause http://arxiv.org/pdf/1504.02578.pdf Median Std.Dev. Mean 7.847 0.0 2.296 0.579 2.312 GCoff 7.743 12.243 2.294 0.582 2.311 Blade 164.206 12.339 2.297 3.395 2.403 GC on
- 49. Added in Linux3.18 https://kernelnewbies.org/ Linux_3.18 http://simula.stanford.edu/ ~alizade/Site/DCTCP.html DCTCP- Data Center TCP - high burst tolerance - low latency - high throughput http://simula.stanford.edu/~alizade/Site/DCTCP.html
- 50. Distributed GC Because wegenerate tons of Docker images
- 51. And more andmore…
- 54. • AP • OptionalCP • Index/search • CRDT • Multiple backends • User ACL support RIAK/Choose a Safe and Simple Friend Make a deliberate choice of consistency model SQL NoSQL But actually… With the authorization of Kingsbury Kyle (Aphyr)
- 55.