I would certainly be happier using a schemaless database with a strongly typed language. I guess it comes down to where you want your dynamism: in the app code

I would certainly be happier using a schemaless database with a strongly typed language. I guess it comes down to where you want your dynamism: in the app code, or in the persistence layer. Using a highly dynamic language with a schemaless database feels very unsafe to me. Similarly, using a strongly typed language with a relational DB is sometimes a pain. I wonder, when one makes a large change to one's app code in the "strongly typed language + schemaless db" scenario, what happens to the existing data that was persisted before the change, which is now in a format that is incompatible with the new model code? I'm used to writing migrations that change the schema and update the existing data if needed, all inside a transaction.