4 ms·
Also, caching layers. Presumably a service uses SQLite to simplify their ops. So long as the caching layer is equally simple to maintain, then SQLite continues
by pfraze 6y ago
Also, caching layers.
Presumably a service uses SQLite to simplify their ops. So long as the caching layer is equally simple to maintain, then SQLite continues to make sense to me
- tyingq 6y agoTheir repo shows the "DummyCache" (no caching) as the default for the Python/Django setup: https://github.com/cmu-db/dbdb.io/blob/master/dbdb/settings.py#L103 https://github.com/cmu-db/dbdb.io/blob/master/dbdb/settings.... I wonder if that's how it is in production.
- kevincox 6y agoFor a mostly static site you would want to cache "over" Django, probably in a caching proxy or CDN. Of course there are a lot of details, such as many CDNs will always go to the origin on a edge miss instead of locating another copy in the CDN. Of course running a caching nginx on the same box as the Django is probably way more performant than caching "under" Django
- tyingq 6y agoIt's intermittently working now. Shows the server as Apache 2.4.18 / Ubuntu. Apache can page cache, but I assume they aren't using it. I don't see any typical CDN headers either. Also, somewhat odd, they are bounding the browser-side cache to 10 minutes: Date: Wed, 16 Sep 2020 18:19:13 GMT Expires: Wed, 16 Sep 2020 18:29:14 GMT
- tbran 6y agoFor this kind of content site, I'd convert the Django site to a static site with django-bakery [1] and stick it on Netlify. I suppose there would be a bunch of rewriting to do searching (lunr.js maybe) and filtering client side. Buuuuuut, at this point, just turning on caching would be easier. [1]: https://github.com/datadesk/django-bakery https://github.com/datadesk/django-bakery