About two years ago I did some work for PBS that might be related to this. The objective was to turn their catalog into a static feed that could be consumed by

About two years ago I did some work for PBS that might be related to this. The objective was to turn their catalog into a static feed that could be consumed by table top boxes. An interesting aspect of the project was that their catalog was fairly well normalized. I was expecting the usual mess of data structures. It was built with vanilla Django. No rest framework because the feed was rendered to static files served by S3. During our discussions I brought using Go for its performance and resilience. That was (correctly) decided against and we went with Django. Why Django? It's easy to wrap up periodic jobs as commands and runnning them with django celery.