Or even go further and separate frontend and backend.
Quote from 21551 (dsicussion should maybe be continued here):
We might want to take the data-processing modules out of the Tor Metrics website code base and start a new service for them that produces .csv files as output.
The advantage would be that we can have a real release process for that service whereas we can push Metrics website updates whenever we need to make them. And of course it would become easier for others to run their own instances of this service without also having to set up their own Metrics website.
This idea has been on my mind for a while now, and in the old naming scheme I would have called this service AggregaTor; but I'm more than happy to use a better name.
If we do this, we should consider doing something similar with data specifications as suggested above for Onionoo and CollecTor: the new service would have its own page on the Tor Metrics website, which would be pretty close to the current page with pre-aggregated statistics files.
The Metrics website code base would then consist of the website contents and the graphing engine that consumes .csv files from the new service.