Please enable JavaScript.

Coggle requires JavaScript to display documents.

System Design, design system - shortening link shortening_url - Coggle…

- - - - Pros:
        
        Easy to implement, fast
      - Cons: It can be duplicate
        To prevent duplicate we can check in the database before we create that URL, this will cause issue low latency
    - - Each time a new URL is created, call KGS to get a key from table new keys, if any issue happen, we can get a new key, this's acceptable, we don't have to check the DB, KGS will make sure the key generated is new and not used.
      - We can store in to two table: new_keys, used_key(to stored all key that already used, or get by created_url service)
      - KGS can be a Single points of failure:
        if the KGS down, it will down the system, we need a replicate of KGS, to backup when the KGS is down
  - - - Let assume we will generate 6 characters and used Base64:
        
        6 characters: 64^6 = 68.7 Billions
        We will need a KGS DB size: 68.7 billions * 6 bytes (6 charaters) ~ 400 GB.