Squid or Varnish for Django?

[Trupti W]

Hi all,

I have a django application that needs to be built to scale in the future. I am considering http caching & ESI for the solution. Has any of you any experience with either Squid or Varnish? What works better with Django? I just want the caching & ESI functionality. We are using NGINX as the reverse proxy.

Thanks!

[Avraham Serour]

what do you mean by ESI? wikipedia has 7 definitions onlyon computer science

In any case you can build you django application normally and scale in the future as needed.

squid and varnish have different purposes and work on opposites sides of the pipe, varnish sits on the server side serving the html, squid sits on the client side reading, and both of them work with http, doesn't matter if you have django

before you complicate your architecture I suggest you start using the django part of caching, set the http headers for caching

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/fb7e1649-0a3e-4d30-9a3d-ebc582650675%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Collin Anderson]

ESI = Edge Side Includes, where some rendering can happen on a CDN.

I personally try to serve the exact same html to every user, and squeeze things like "hello so-and-so" (and csrftokens) into a cookie and display that using javascript. That way most of my webpages don't have a Vary header, and I can take full advantage of http caching.