"Schemaless databases" are cool. I would rather maintain as little schema as possible in the database and instead keep it in my code. Schema must exist somewher

"Schemaless databases" are cool. I would rather maintain as little schema as possible in the database and instead keep it in my code. Schema must exist somewhere because my data model exists. Since the data model and my program are tightly coupled (since the entire point of the program is to manipulate internal data state due to external and internal stimulus and produce output), keeping them together makes the overall system manageable versus the headache of effectively having code in two places. This is similar for complicated routing configurations pushed to proxies and other external config. They are really part of your code.