twobraids/socorro — comment on commit aa6467146b2548e038d1b13acf71c695296906f5
File:  line 0
By Lonnen:

I don't care much for the `socorro/[type of database]_algorithms/` folders. RDBMs systems may be similar, but I don't think we can abstract NoSQL techs usefully. It looks like an added layer of complexity to me. Could we fold what you have there into the individual `socorro/externals/*` folders?

I also don't see a way to specify dependencies on other cron jobs here. We currently use the dailyMatviews job to establish dependencies between stored procedures, and its working out well enough that we'll probably introduce an hourlyMatviews job. It may be more useful to think about how dailyMatviews (https://github.com/mozilla/socorro/blob/master/socorro/cron/dailyMatviews.py) translates to configman.

Since data derivation is so dependent on what tech is being used, I think it would be good to setup a cron app in the external, such that each external could decide what needed to be done and what was dependent on which. Alternatively, we could maintain hourly and daily cron apps in socorro, using configuration pointing to particular external apps to be run to populate the data. Some convention would have to be established for a `run()` method, how to report failure, and dependencies.