Design a URL Shortener (TinyURL, Bit.ly) | Systems Design Questions 3.0 With Ex-Google SWE

She told me that she likes my short URLs, because the big ones hurt too much anyways https://docs.google.com/presentation/... Hey everybody, thanks so much for giving this one a watch. You may notice that these videos aren't going to be hours long, and are pretty succinct. That's on purpose, I want to be straight to the point. If you want me to cover aspects of this problem that I neglected to mention, please let me know. Besides that, I anticipate there being a lot of comments here. Like I said, before, if you want me to respond to yours within a week, please sign up for a channel membership. It's not going to make the video quality any better, but it's going to get me one step closer to finally buying that Lamborghini and flexing on my annoying ex-girlfriend. Here are timestamps this time, aren't I a great guy? 00:39 - FUNCTIONAL REQUIREMENTS 01:27 - SUPPORTED SCALE 02:36 - URL MAPPING TABLE 03:42 - NUMBER OF DATABASE NODES 04:25 - HIGH LEVEL DESIGN 05:16 - KEY GENERATION SERVICE OVERVIEW 05:49 - CREATING A SHORT URL 06:09 - RETRIEVING A SHORT URL 06:35 - DATABASE INDEXING 07:09 - DATABASE REPLICATION 07:53 - CACHING OVERVIEW 08:33 - REDIS 09:37 - DEEP DIVES 10:03 - DATABASE CONTENTION 10:42 - KEY REBALANCING 11:31 - DATABASE MANAGED REQUEST ROUTING 12:36 - CITUS 13:18 - HASHING 14:24 - CHOOSING A DATABASE 14:40 - DATABASE INDEX CHOICE 15:13 - DATABASE REPLICATION CHOICE 16:24 - MULTIPLE REGIONS 16:44 - READ THROUGH CACHING