Document examples of problematic database storage and patterns
We've already discovered some patterns can cause stability and scalability issues. We should document these patterns as a reference for engineers and maintainers who are designing and reviewing new features that leverage the database.
Definition of Done
-
Begin a document in the database with information on problematic patterns -
Include information from the discussion below -
Include information on table size and issues
-
-
Link to the new page in database review in the "preparation when adding tables" and "how to review" sections
Background from Thread
The following discussion from !81179 (merged) should be addressed:
-
@alexives started a discussion: (+4 comments) Can we provide examples of patterns that pose such risks? (Maybe this is it's own document?)
Here is a recent example which inspired this update. https://docs.google.com/document/d/1yYyCuUiIadGJCVaM9spXnHgu1wQiCcjCGuYrVDsyj44/edit#heading=h.uqd2cif1583i
I agree that finding a way to include examples would be useful. Let me know if you have suggestions on how to achieve this.