Timeline for Logical separation of database content
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 7, 2018 at 9:41 | comment | added | Danielku15 | The blog example is really a small schema to illustrate the topic. Actually it is a way more complex ERP like system with a partial entity-attribute-value data model. From a DB query perspective it might be achievable to add the neccessary filters everywhere, but also domain level validations and unique constraints need to be extended. The multi-database system doesn't sound too bad for me as we already have a centralized DB update sequence on application startup. | |
| Aug 6, 2018 at 21:02 | comment | added | abydal | I agree with greg-burghardt if the blog example really is the schema being used. But my understanding is that the blog schema is just a small example, and that @Danielku15 really is working with a much larger schema. | |
| Aug 6, 2018 at 20:30 | comment | added | Greg Burghardt | @Danielku15: I really really really would not start with this solution. Misamoto has the right solution. If you think the coding effort is difficult just to add a "blogs" table, the database maintenance effort will be monumental if you must maintain a bunch of similar looking schemas. | |
| Aug 6, 2018 at 12:09 | comment | added | Danielku15 | I also did some further reading as Killian nicely added the correct tag "multitenancy". It really seems to be the fastest and easiest solution to have separate databases. I might need to still clarify with our product management if we really can have a strict separation of all tenants. | |
| Aug 6, 2018 at 12:00 | review | First posts | |||
| Aug 6, 2018 at 14:18 | |||||
| Aug 6, 2018 at 11:55 | history | answered | abydal | CC BY-SA 4.0 |