Think of it more abstractly, memcached isn't a "web tool". If you're fetching the same thing over and over from the DB without it changing inbetween, you can cache it. If you're applying complex templates or sorting data, etc. Anywhere where blobs of data are reusable you can get a win.
...but if your backend is fast enough and traffic low enough, it's easier to skip caching altogether. On Wed, 26 Sep 2018, testingformy...@gmail.com wrote: > Hi there- > I'm hoping somebody here can help me out with something? I was told to look > into whether memcached would be appropriate for a new tool we'll be > developing, and it's a little difficult to tell. What we'll be working on is > a tool that's meant exclusively for managing data. Creating / Modifying / > Deleting products, orders, accounts, etc. Said tool is going to be in use by > hundreds of people at any given time. > > Based on what I've read so far, it sounds like memcached is great for > supporting a website, but there isn't much out there talking about supporting > a tool > like the one described above. Does anyone here know one way or the other? > If it helps, we're hoping to be running the tool on a LAMP setup. > > Thanks very much! > > -- > > --- > You received this message because you are subscribed to the Google Groups > "memcached" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to memcached+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > > -- --- You received this message because you are subscribed to the Google Groups "memcached" group. To unsubscribe from this group and stop receiving emails from it, send an email to memcached+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
