You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently is the creation of an entity fails, then there are often partial entities left over - causing both orphaned data and instability in the server.
Goal
Creation of entities should be done in memory, with only a single save at the end.
Hypothesis
Having atomic creation of entities will
improve production server stability
reduce data without the proper relations set
improve developer effectiveness (less resetting of the database)
techsmyth
changed the title
Atomic creation of entities + authorization policies
Stability: Atomic creation of entities + authorization policies
Jun 14, 2024
Description
Currently is the creation of an entity fails, then there are often partial entities left over - causing both orphaned data and instability in the server.
Goal
Creation of entities should be done in memory, with only a single save at the end.
Hypothesis
Having atomic creation of entities will
Must have scope
Stakeholders
Development
QA
Design
To be build up from lower level entities.
Spike can go last to derisk the rest of the work.
The text was updated successfully, but these errors were encountered: