This is a continuation of the earlier posts starting with this one: http://ravinote.blogspot.com/2020/09/best-practice-from-networking.html
If the listing is common to several consumers, a key may be used for each consumer for their specific needs. If this approach does not scale, then the listing may be retrieved in ranges and the filtering may be taken over on the compute side.
The keys will need to have backward compatibility otherwise they break existing scenarios.
When a new key is added, it may not impact existing keys, but it does affect the overall space consumption of the listing depending on the size and number.
The keys can have as many fields as necessary. If this becomes slow, the lookups can be faster when there are only a few keys to compare.
Key comparison can be partial or full. Partial keys are useful to match duplicates. The number of keys that share the same subkeys can be many. This form of comparison is very helpful to group entries.
Grouping of entries also helps with entries that span groups based on subkeys. These work across groups
No comments:
Post a Comment