> > A layer of filesystem caching can then be added to prevent accessing > > from the database each time, but you can also scale out to multiple > > servers without a shared filesystem (such as NFS). > > Hi guys, I am a real beginner in caching, and even don't know where > exactly to start my study. Needing some suggestion and/or references. > My application is of a CMS kind, where users can store text and images. > I think to store images in database (SQLAlchamy + PostgreSQL), and > cache them in the webservers.
*** I'm in a similar situation, creating a similar system. This is the best caching solution I've found: http://www.danga.com/memcached/ That doesn't help you in deciding how to store your content, however. Mine is stored in the filesystem, using names that map to unique DB keys in my relational DB. But my content isn't as dynamic as yours, so YMMV. Stuart --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to turbogears@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears -~----------~----~----~----~------~----~------~--~---
