News for hackers. Stuff that matters.
Re:How Facebookipodayclosingprice.com Scaled with MemCachier by nacs on Tuesday May 29, 2012 @06:45PM (#4040382)
Not to be cynical but this post has virtually no content -- it's simply "We used memcache as a caching layer and not hit the DB. The End"

Didn't we know this a decade ago?

[ Parent | on HN ]
Re:How Facebookipodayclosingprice.com Scaled with MemCachier by hodgesmr on Tuesday May 29, 2012 @07:18PM (#4040499)
While some people look at this as "so what?" I did find the post valuable. I've never used memcache before, and this was a good illustration of its use.
[ Parent | on HN ]
Re:How Facebookipodayclosingprice.com Scaled with MemCachier by joejohnson on Tuesday May 29, 2012 @06:58PM (#4040431)
How many hits were they really getting? It appears that only 2261 people made predictions.
[ Parent | on HN ]
Re:How Facebookipodayclosingprice.com Scaled with MemCachier by alex_lod on Tuesday May 29, 2012 @07:37PM (#4040563)
It was covered in TechCrunch, Bloomberg, and other big journals, too -- it definitely got a lot of views.

The difference between the small number of updates (2261) and the presumed large number of views is precisely why this was a great use case for memcache/MemCachier. High-read/low-update content is the perfect caching use case.

[ Parent | on HN ]
Re:How Facebookipodayclosingprice.com Scaled with MemCachier by getsat on Tuesday May 29, 2012 @07:56PM (#4040629)
Website uses basic caching to survive traffic spike, news at 11.
[ Parent | on HN ]
Re:How Facebookipodayclosingprice.com Scaled with MemCachier by adventureful on Tuesday May 29, 2012 @07:33PM (#4040546)
Had not seen the site before. Amusing how far off nearly everybody was on the pricing.
[ Parent | on HN ]