You are reading a single comment by @arrowplum and its replies.
Click here to read the full conversation.
-
Ok, but by site specific you mean lfgss specific, yeah? So microcosm (the product) queries the db to access microcosms's (the sites [like lfgss, is that right?]) resources even if they seem static? So lfgss specific things are expensive (relatively) even if they don't seem like it.
That must be why long caching is so important. You are using cloudflare for some things, right?
arrowplum-
You should read our code if you're interested. On github, called microweb.
One API, drives all sites, one Django codebase delivers all frontends, all shared files are just dumb static files, everything else is determined from what the API tells Django.
We use CloudFlare for DNS and SSL as much as the edge cache.
We're not yet using Railgun, but we may.
Velocio
Erm, no. But if it's a site-specific resource, then it will need to find out about the site it's on, and what the resource is.
Shared site resources are just your standard static files.