Design A URL Shortener | System Design Beginner’s Course 2022

[@girdharsinghrathore3857]

keeping doing great work (Y), page number 6, why are you returning short url directly from DB to client, it should be via DB=> APP server=> load balancer=> client

[@0xssff]

brilliant

[@antimuggle_ridhi2565]

shouldn't the redis cache be user specific? If so why is it located in the api server?

[@irtizahafiz]

Depends on how you want to cache the data. Typically server-side caches (such as Redis) will be on the API layer, while client caches can be build on the user's device.

[@melk48111]

Hi irtiza, are you planning to do system design on Web crawler or Uber?

[@irtizahafiz]

Web crawlers, yes.

[@zymasethecatalyst]

Keep Going 🚀🚀

[@irtizahafiz]

More coming 😎

[@firezdog]

How do you deal with persistence? Even in this simple system, it seems like you want to do something to make sure that the data in that MySQL database is recoverable -- especially if a lot of links to your tinyURL are being used all over the web.

[@irtizahafiz]

Most cloud-hosted MySQL systems have some kind of redundancy built for data recovery.

[@raghusrinivasan7309]

A few more extensions to this approach can be studied at kzbin.info/www/bejne/d4fdpYWPbJyrrqM which talks about how many characters you need for coming up with a short URL based on the #requests coming for this service. It also has some info about generating analytics info based on geography, #requests/sec etc

[@thegreatlazydazz]

Why does the web browser need a sever to generate short urls and tranlstae it back to long urls. Why is it so difficult for web browser to store long urls?

[@irtizahafiz]

I am not sure what you mean by the "web browser" storing long URLs?

[@kyakarein]

any reason to skip capacity estimation? how we will handle required scaling?

[@irtizahafiz]

Sorry, I didn't mean to cover every angle. Hopefully what I had was useful to you.

[@석상주]

I think there is some minor flaw with the approach. Even if there exists a mapping between short URL and long URL, you'd still generate a unique hash because you don't want different users to own the same short link.

[@irtizahafiz]

Hi! That’s a good point! In my design here, I didn’t take in account supporting unique shortURLs for individual users. If your app requires it, then yes you can generate the unique hash regardless at the expense of greater space usage.

[@swattertroops-yaaa]

I think it should progressively add entries like /aaaa /aaab /aaac all the way to 0000

[@firezdog]

why not?

[@swattertroops-yaaa]

I'll make a product around this

[@irtizahafiz]

That’s awesome! Good luck!

[@jackfrost8969]

Defining TTL without a user-specific URL is not an optimal approach. One two many flows here.