-
Notifications
You must be signed in to change notification settings - Fork 85
feat: add docs about source of truth #1002
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR introduces documentation about the "Source of Truth" by updating the sidebar configuration in the docs. The changes close the previous sidebar entry and add a new entry for the "Source of Truth" document.
- Added a new sidebar entry for "Source of Truth" in the best practices section.
- Adjusted the object boundaries to incorporate the new entry.
Files not reviewed (1)
- docs/content/best-practices/source-of-truth.mdx: Language not supported
|
|
||
- User data: The source of truth for user profile data is typically an identity provider like Azure, Okta or Auth0. | ||
- Entity hierarchies: Structures like project/tickets or folder/documents already live in application's databases. Repeatedly querying <ProductName format={ProductNameFormat.ShortForm}/> just to navigate that hierarchy would be inefficient. | ||
- Data relevant for search and filtering: When performing searches, you need to combine data that's on your database and data that's in <ProductName format={ProductNameFormat.ShortForm}/>. Your application's database is the right place to do filtering/sorting/joins. The data required for performing those operations should live in application's databases. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might be worth giving an example for clarity? Such as storing document.content in the app's database, but store document.owner in FGA.
Co-authored-by: Raghd Hamzeh <raghd.hamzeh@openfga.dev>
Description
References
Review Checklist
main