This is a continuation of the earlier posts starting with this one: http://ravinote.blogspot.com/2020/09/best-practice-from-networking.html
Listings are great to use when they are in a single location. They are often scoped to a parent container. If the parent containers are distributed, the listings tend to be multiple. In such cases, the effort is repeated.
When the listings are separated by locations, the results from the search may be fewer than the expected total if only one of the locations is searched. This has often been encountered in deployments.
The listings do not need to be aggregated across locations in all cases. Sometimes, only the location is relevant, and the listing and the search can be scoped to it.
Iterating the listings has proved banal in most cases both for the system and for the user. Consequently, either an identifier is used to go directly to the entry in the listing, or a listing is reserved so that only that listing is accessed.
The listing can be cleaned up as well. There is no need to keep it growing with outdated entries and then archived by age. The cleaning can happen in the background so that list iterations skip over entries or do not see the entries that appear as removed.
Listing entry values are particularly interesting. In addition to the type of attributes in an entry, we can take advantage of the range of values that these attributes can take. For example, we can reserve boundary values and extremely tiny values that will not be encountered in the real world at least for most cases.
No comments:
Post a Comment