Look into if modeling data differently in the DB has benefits

[Cryptophobia]

From @helgi on September 15, 2016 23:13

Instead of JSONField consider doing a parent/child model to handle proc type information. (and other nested information). Autoscales model with Autoscale for web and worker records. This will only work in some cases. Might not map to health checks very well given it is a very nested structure.

There are two reasons why I want to see some exploration on this

1. Do validations outside of the JSON Schema hack and rather utilise built-in validations from Django / DRF or at least function based validations
2. If swagger (Specify the API using swagger deis/controller#811) happens (or any auto-generated schema format) then having data concretely described it going to help a lot

This may not be viable at all, or is only viable when dealing with very simple structures, at best when we know it needs to only map down to the level of process type

Copied from original issue: deis/controller#1075