InterviewBit Problems   Design URL Shortener

About the Design URL Shortener category (1)
How would you handle machine dying in the case of SQL DB? (3)
Is NoSQL more consistent that RDBMS like SQL Server? (3)
What is the minimum length of shortened url to represent 6 Billion URLs? (9)
URL Shortener How would a typical write query look like? (4)
How many queries per second should the system handle?(Assuming 100 Million new URLs added each month) (16)
X^62 > 610^9 should be 62^x > 610^9 (3)
Why 1 billion queries month? (1)
Should I return the same tiny URL for two users who try to shorten the same long URL? (3)
Shouldn't ShorteningAPI have a custom short url parameter? (1)
Gotcha: How should we handle the case where two separate URL gets shortened to the same URL? (9)
Doubt with the formula (2)
Should we choose Consistency or Availability for our service? (6)
What does "salt" mean in URL shortener? (2)
Should we choose RDBMS or NOSQL? (7)
URL Shortener How does our client know which application servers to talk to. How does it know which application servers have gone down and which ones are still working? (4)
Try to list down other design goals? (3)
URL Shortener Is Latency a very important metric for us? (4)
URL Shortener How would you take care of application layer fault tolerance? (3)
How many URLs will we need to handle in the next 5 years? (3)
How would you shard the data if you were working with SQL DB? (5)
How should we compute the hash of a URL? (7)
Why store hash as the key instead of the encoded(first 6 characters) value as the key? (1)
How much data will we need to store so that we don't have to restructure our architecture for the next 5 years considering constant growth rate? (9)
What all data should we store? (3)
Not Understand how they come up with 3 TeraBytes for URLs and 36 GigaBytes (2)
URL Shortener How do we handle the case where our application server dies? (3)
How does the database handle expired URLs? e.g. just replace the key's value with TinyUrl's 404 page? (2)
Data read/written each second? (3)
Do the figures matter from interview perspective? (1)