Optimized organization enrichment #2187
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes proposed ✍️
Optimize organization enrichment by enriching
organizationCaches
table instead oforganizations
table.Explanation:
organizations
table belongs to a tenant and is a copy oforganizationCaches
table which is a global table and is deduplicated. So we can have oneorganizationCaches
entry that belongs to multiple tenants inorganizations
table.So the optimization is that we will spend less enrichment credits because we will first enrich
organizationCaches
entry and then update all instances inorganizations
table with those enriched data.How
Before we had one temporal schedule that triggered enrichment of
organizations
table entries and updatedorganizationCaches
.Now we have two temporal schedules: one triggers enrichment of
organizationCaches
tables and the other updatesorganizations
table entries where needed.Checklist ✅
Feature
,Improvement
, orBug
.Add screenshots to the PR description for relevant FE changesNew backend functionality has been unit-tested.API documentation has been updated (if necessary) (see docs on API documentation).