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, we are populating all the schemas for a Post, Fact Check, etc during retrieval on dega-api. This is an expensive query and is more performant to populate it as a new field during creation/updation of a post.
PRO:
Performance of the read queries in dega-api improves significantly, especially the ones which are more involved like the fact-checks
CONS:
Increased complexity when creating/updating a post. This should still be manageable as long as the read queries which are more frequent are performant.
When updates are made to fields like organization, user, etc, we have to repopulate all the related schemas for posts. A workaround for this would be to provide the ability to manually retrigger generation of all the schemas for posts in a particular space. This way, administrators for a particular space could trigger updating the schemas manually whenever there is a change that automatically doesn't generate the schemas.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Currently, we are populating all the schemas for a Post, Fact Check, etc during retrieval on
dega-api
. This is an expensive query and is more performant to populate it as a new field during creation/updation of a post.PRO:
dega-api
improves significantly, especially the ones which are more involved like thefact-checks
CONS:
Beta Was this translation helpful? Give feedback.
All reactions