Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Backend architecture for LINE LP production tool

Backend architecture for LINE LP production tool

Daisuke Matsushita
LINE Growth Technology Development Department Server Side Engineer
https://linedevday.linecorp.com/jp/2019/sessions/S2-16

LINE DevDay 2019

November 21, 2019
Tweet

More Decks by LINE DevDay 2019

Other Decks in Technology

Transcript

  1. 2019 DevDay Backend Architecture for LINE LP Production Tool >

    Daisuke Matsushita > LINE Growth Technology Development Department Server Side Engineer
  2. About me Daisuke MATSUSHITA LINE Growth Technology Co., Ltd. Developer

    Department Development Center Server Side Engineer Self Introduction
  3. What’s LPGen From Backend > Landing Page Generator > developed

    and operated by LINE Growth Technology Co., Ltd. > In-house service in LINE group LPGen Overview
  4. LPGen Backend Architecture > VOS is an object storage server

    in Verda. > In LPGen, VOS is used for image files and the place to deploy LP. > Verda is LINE internal private cloud environment. About Verda Object Storage(VOS)
  5. LPGen Backend Architecture > This server proxies requests to the

    API server. > This server has an authentication module called NSS. > This server returns HTML of LPGen. About Web Server
  6. LPGen Backend Architecture > For LPGen login, users can use

    ID/PW they usually uses.
 → Simple > NSS authenticated a user and add authentication information to requests. > NSS is Single Sign On system for NAVER and its group companies. 
 About NSS
  7. LPGen Backend Architecture > Only API server accesses the database

    and VOS. > When users publish LP, this server receives contents of HTML, makes a HTML file and deploy it to VOS. → Quick Deploy > We designed API as RESTful API. About API Server
  8. LP Build and Deploy Flow LPGen Backend Architecture API Server

    ᶃ Client Calls API With LP HTML Image VOS ᶄ Get Image Used in LP LP VOS ᶅ Deploy LP Html File and Image
  9. LPGen Backend Architecture > It is high cost that a

    proxying route is via internet. > We will use not Verda CDN but an internal cache server. > Verda CDN internally uses AWS Cloud Front and Akamai. Future Task