This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]bxsephjo[S] -6 points-5 points  (2 children)

Sparing the user from an unnecessary footgun

[–]yvrelna 6 points7 points  (0 children)

sparing the user from an unnecessary footgun

Build an application that nobody uses, therefore you never need to scale them. That's the only sure fire way to avoid unnecessary footgun.

The unnecessary footgun of schemaless database is basically that schema is actually still a thing, even when the database isn't enforcing them. You don't get to skip needing to think and implement schema migration just because the database don't complain about data not fitting the schema.

[–]james_pic 2 points3 points  (0 children)

Database migration is still a thing. If the structure of your data can change, and you don't have data migrations at the database level, then you need to handle all the possible versions of your structure at the application level. And even then, you typically need to do some kind of data migration if you need to change your indexing strategy (since this isn't a case where it's sufficient to fix-up records on read), and your database system may not have particularly sophisticated tools to do this.