4 ms·
> a fixed schema/format that will never change When would this happen for any non-trivial multi-tenant service? The difficultly of performing migrations sound
by digisign 4y ago
> a fixed schema/format that will never change
When would this happen for any non-trivial multi-tenant service? The difficultly of performing migrations sounds like it would pretty quickly negate any simplicity gained.
- Mertax 4y agoDefinitely use case specific, as it wouldn't work generally, especially for domain driven data models. The schema I'm thinking of specifically represents a data model that is flexible enough where migrations are extremely rare[1]. Even if there are migrations, it's treated similar to a file conversion (like upgrading an older excel file format to a new format on demand when the file is accessed). [1] Maybe something similar to https://www.notion.so/blog/data-model-behind-notion https://www.notion.so/blog/data-model-behind-notion or an EAV model imbedded in a JSON1 column.