Note that a 2-level cache was also just merged into doctrine/cache (not yet tagged): https://github.com/doctrine/cache/pull/52
Marco Pivetta http://twitter.com/Ocramius http://ocramius.github.com/ On 11 December 2014 at 17:04, Menno Holtkamp <[email protected]> wrote: > Since we are going beyond the subject of this mailing-list, my last > contribution to this thread. > > No, you mis-understood the idea of a two-level cache. The ResultCache, can > also be 'done' using a two-level cache. The results will be saved at the 2 > levels, the fast one (APC, in-memory) and a slower one, which might be > file-system, but I would prefer a server independent approach: a shared > datastore like MongoDB. That way you have the advantages of both > mechanisms. You can reboot your server (clearing the fast, in-memory > cache), but still have a fallback on the slow cache. > > Anyhow, please read this: > http://framework.zend.com/manual/1.12/en/zend.cache.backends.html#zend.cache.backends.twolevels > and DO experiment before responding ;). > > And MongoDB can be used as a quite powerful caching layer (for example > with support of tagging and automatic expiryDates), separate from the > concepts of ORM / ODM. > > About caching the REST API Response, yeah I would cache the responses. The > API might be down / slow response, etc. Only when the API is in the same > network / cluster, caching might be skipped, but still in that cache I > would apply caching. > > Cheers > > On 11 December 2014 at 16:20, Nima Sadjadi <[email protected]> wrote: > >> Hi Menno, >> I know the FileCache has no excellent performance but in general: >> Assuming if a user can only use FileCache with orm only (no MongoDb), do >> you mean using ResultCache as second level cache? And Metadata/Query as >> first level? >> Or you were refering to my second post to set the RESTApi response as >> second level? >> >> -- >> You received this message because you are subscribed to the Google Groups >> "doctrine-user" 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/doctrine-user. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to the Google Groups > "doctrine-user" 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/doctrine-user. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "doctrine-user" 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/doctrine-user. For more options, visit https://groups.google.com/d/optout.
