> There are no schemaless databases, just the ones with an explicit schema and the ones with their schema defined in a couple hundred places in code This is a

> There are no schemaless databases, just the ones with an explicit schema and the ones with their schema defined in a couple hundred places in code This is a false dichotomy - there are better ways of self-managing the schema than "couple hundred places in code." There are valid usecases where a schemaless db is the better option (e.g. when you're recording self-describing data. Or when there is an implicit, consistent structure to the data - but the engineers won't know it at development time. Or when you want to do a full-take of structured data including unknown fields without losing data that's not in your DDL without resorting to file blobs, requiring additional data management)