I have done some preliminary reading.

[Config files vs database tables](https://stackoverflow.com/questions/3190710/config-files-vs-database-tables)  

[Type to use for "Status" columns in a sql table](https://stackoverflow.com/questions/7205391/type-to-use-for-status-columns-in-a-sql-table)

Tables:

```
[video]
    id
    title
    format_id (foreign key)
    language_id (foreign key)
    aspect_ratio_id (foreign key)

[formats]
    id
    name

[languages]
    id
    name

[aspect_ratios]
    id
    name

```

The last 3 tables (formats, languages, aspect\_ratios) aren't going to change much (if at all). i.e. I might add a new language when we have support for it.

So is it a good practice to extract those types of tables (references only, hardly any updates/inserts) into a standalone yaml file and have the application logic to deal with the views? Or should I keep everything in the DB to maintain the data & relational integrity at the (small) cost of table joins?