Re: Caching Blogger API Responses - Memcache or Database?
"'Brett Morgan' via Blogger Developer Group" <[email protected]>
| Newsgroups | gmane.comp.web.blogger.api |
|---|---|
| Message-ID | <CAAFdGSdz2oCu-uFE3NRuwUzU4vo2j+xLOsAWV0mjzN4TCJ5qCg@mail.gmail.com> |
Hi Femi, Traditionally memcache is used for this style of caching because replacing lost content is a simple matter of making another request to the Blogger API. Silly question, how many requests per day are you currently dealing with? brett On Thu Oct 09 2014 at 9:32:38 AM Femi TAIWO <[email protected]> wrote: > Hello, > > Summary: Cache or not to cache? > > I am displaying posts and comments from another Blogger site on my > platform. > Each time a user visits the page or article, I make a call to the API to > get article information and another one to get its comments. But I'm > convinced that this is a bad design. > > I'm thinking of caching the results maybe for a couple of hours or a day > since the article content rarely changes once published. > > Please do you think Memcache would be the best fit for this or should I be > saving to a database and replacing it after a refresh? > > > Regards, > > *Femi TAIWO* > http://plus.google.com/+FemiTAIWO > > -- > You received this message because you are subscribed to the Google Groups > "Blogger Developer Group" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/bloggerdev. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Blogger Developer Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/bloggerdev. For more options, visit https://groups.google.com/d/optout.