Handling TV Ad Traffic Influx with Microservices

https://wantedly.connpass.com/event/135968/ での登壇資料です。

Transcript

1. FiNC Technologies Ryo Kubota )BOEMJOH
   57
   "E
   5SBGGJD
   *OGMVY
   XJUI
   .JDSPTFSWJDFT
2. • Ryo Kubota • FiNC Technologies • SRE • New graduate 8IP
   BN
   *
3. • What is Microservices? • About our TV Ad • Discussion on Microservices after TV Ad "HFOEB
4. What is Microservices?
5. An architecture that structures a big system as a collection of small services 8IBU
   JT
   .JDSPTFSWJDFT
6. • Technical heterogeneity • Resiliency • Scalability • etc #FOFGJUT
   PG
   .JDSPTFSWJDFT
7. 8IZ
   'J/$
   BEPQU
   .JDSPTFSWJDFT
8. l0OF
   "QQ
   GPS
   &WFSZ#PEZz The concept goes well with Microservices New functions have been quickly released UP$
   BQQ
   "VUIFOUJDBUJPO &DPNNFSDF
   "* $PVQPO
   8FBSBCMF 3FDP
   FOHJOF
   -JGFMPH 4/4
   $IBU UP#
   TJUF 1PJOU
   4VQQMFNFOU
9. About our TV Ad
10. 57
    "E
    5SBGGJD
    *OGMVY
11. • .VMUJQMF
    /FX
    'VODUJPOT
    3JHIU
    #FGPSF
    UIF
    57
    "E • https://note.mu/mizoguchiyuji/n/n1267b01a3756
12. • Traffic influx • Parallel development right before the TV ad • But NO DOWNTIME 8F
    IBOEMFE
    57
    "E
13. Discussion on Microservices after TV Ad
14. 8IBU
    EJE
    XPSL 
    
    4DBMJOH
15. • You can scale out each function separately 8JUI
    .JDSPTFSWJDFTʜ
16. "
    NJDSPTFSWJDF
    GPS
    VTFS
    POCPBSEJOH Transition in the number of workers → TV ad started
17. • Quicker than scaling a single big monolith • Cost saving 4DBMJOH
    .JDSPTFSWJDFT
18. 8IBU
    EJE
    XPSL 
    
    'VODUJPO
    #BTFE
    1BSUJUJPOJOH
19. • .VMUJQMF
    /FX
    'VODUJPOT
    VOEFS
    %FWFMPQNFOU
    JO
    1BSBMMFM • https://note.mu/mizoguchiyuji/n/n1267b01a3756
20. • You just need to focus on a single function • This can only be done with Microservices 1BSBMMFM
    %FWFMPQNFOU
21. 'VUVSF
    JNQSPWFNFOU
    -FHBDZ
    .POPMJUI
    
22. "
    -FHBDZ
    .POPMJUI
    4UJMM
    3FNBJOT Legacy monolith can often be a bottleneck
23. &YBNQMF
    BU
    'J/$ .POPMJUI 4FSWJDF
    " 4FSWJDF
    # 4FSWJDF
    $ 4FSWJDF
    % : Synchronize user info • This monolith has a knowledge about to which services it has to synchronize its information => Tight coupling (Anti-pattern)
24. • Anti-pattern emerged as a problem under increased traffic • The queues for synchronization got stuck *ODJEFOU
    %VSJOH
    57
    "E
25. -PPTF
    $PVQMJOH • Each microservice should not have knowledge about other services • Use pub/sub model instead • Microservice just publishes some event • Other microservices subscribe it if needed
26. .JHSBUJPO
    GSPN
    .POPMJUI • When you adopt Microservices, you often need to migrate from monolithic architecture • Legacy monolith is likely to be tightly coupled to other services • Complete migration not to fall into anti-patterns • Otherwise you might end up increasing complexity
27. $PODMVTJPO
28. $PODMVTJPO • We ran TV ad • We handled the traffic influx and parallel development with Microservices • Explained about a legacy monolith as future improvement