So, the number of objects to be stored would be around: 300 M * 2 yrs * 12 months = 7.2 B. ![]() Let's assume, we store URL requests for a period of 2 years. So, there would be around 50 X 300M = 15B redirections per month which is around 300 M / (30 days * 24 hrs * 3600 sec ) * 50 = 5K URL redirections in a second. Let's take the request ratio to be 50:1 between redirection and shortening. It is safe to assume that our service would have more requests for redirection as compared to shortening. Let us assume 300M fresh URL shortening requests coming up each month. The service should maintain the analytics.Shorter links should not be able to guess and redirect should happen with minimum latency (delay).There should be an option for the user to be able to pick a custom name.The service should be available throughout the day.That short link should be able to redirect the page of the original link.The system should be able to generate a short link that is easy to copy. ![]() Moreover, it could be used if someone wishes not to use the original URL. Secondly, they surely save a lot of space when used or printed. A very basic advantage could be that users tend to make very few mistakes while copying the URL if it is shortened. Why do we need to shorten the URL? Is it something necessary? Well, there are many advantages that shortening of URL provides. ![]() Even wondered why and how these kinds of applications work? In this article, we'll be discussing the system design of a URL shortener and compare it with some applications currently in use.īefore reading this article, it is suggested if you could go and try out so that you could understand this article better. You might have seen URL shortener services such as TinyURL or Bit.ly which are used for using a short alias instead of long URLs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |