Case Studies Archives - Shared Hosting | VPS Hosting | Dedicated Hosting
 

Yelp Case Study

System Specifications Bandwidth (Why Medium?): Yelp stores a huge amount of information that is added to daily. The website receives over 120 million users each month and is ranked the 30th most popular website in the United States by Alexa – this all amounts to a large amount of traffic looking for ever-changing information. However, the […]

Read More

SnapChat Case Study

System Specifications Bandwidth (Why Medium?): Although over 400 million Snaps are sent each day and they are entirely images or videos, they are small and low-quality. This means that not very much data is transferred over each day. However, it is still medium because of how many people use SnapChat on a daily basis. Disk (Why […]

Read More

Vine Case Study

System Specifications Bandwidth (Why Medium?): Vine has an even more limited functionality than Instagram.It does qualify as social media because you can (“like”), comment, and “re-Vine” (share). But it does not allow you to post static images and can only apply minimal images. However, the bandwidth is “medium” because videos require more than text. Disk (Why […]

Read More

Instagram Case Study

System Specifications Bandwidth (Why Medium?): Instagram has very limited functionality. Although it is a social media platform, not very much information is shared. However, pictures and videos need more bandwidth than text, and Instagram is entirely composed of both of these. Disk (Why Medium?): Instagram stores all of the pictures and videos uploaded by users. The photo-sharing […]

Read More

Expedia Case Study

System Specifications Bandwidth (Why medium?): Expedia’s database includes information regarding flights, airlines, hotels, rental cars, and more. With over 40 million visitors a month, this site has a fair amount of traffic. Because the type of data stored is small (information as opposed to videos), the bandwidth is medium. Disk (Why low?): Storage for Expedia includes information […]

Read More

Polyvore Case Study

System Specifications Bandwidth (Why medium?): Because Polyvore only deals with pictures of clothing and text-based information, it does not need a high bandwidth. The amount of traffic garnered makes it medium. Disk (Why medium?): Polyvore stores lots of information, including social networking and the database of clothing that gets shared between users. However, the information […]

Read More

IMDb Case Study

System Specifications Bandwidth (Why Medium?): Although IMDb doesn’t stream a ton of full moves like Netflix does, it does stream movie trailers and some TV shows: high bandwidth is necessary to ensure that all viewers can access materials. IMDb hosts with Amazon’s CloudFront, which provides a reliable service that accounts for traffic spikes and lulls. […]

Read More

LivingSocial Case Study

System Specifications Bandwidth (Why Low?): Although LivingSocial has a lot of users, it only needs to provide enough bandwidth for simple browsing, and sending daily deal emails to customers does not require too much bandwidth. CPU (Why Low?): The LivingSocial website displays a lot of images and text describing its deals, and the main functions […]

Read More

Goodreads Case Study

System Specifications Bandwidth (Why Low?): Goodreads doesn’t display large amounts of data on their site. In fact, most images aren’t anything more than a book cover, and they don’t stream videos (except occasionally on their blog). CPU (Why Medium?): They definitely need some computing power to run all the features they provide as well as […]

Read More

Woot Case Study

System Specifications Bandwidth (Why Medium?): At certain times, Woot receives a ton of traffic. During a sale, they once had 3.1 million buy requests and sold out in 8 seconds. These occasions require high bandwidth, but normally they use much less. CPU (Why Low?): Since Woot’s business model offers one main product per day, customers […]

Read More