This is a continuation of the earlier posts starting with this one: http://ravinote.blogspot.com/2020/09/best-practice-from-networking.html
The results from the background tasks mentioned above might also take a long time to accumulate. They can be made available as they appear or batched.
The load balancer works very well to enable background tasks to catch up by not overloading a single task and distributing the online activities to ensure that the background task has light load
The number of background tasks or their type should not affect online activities. However, systems have known to be impacted when the tasks are consuming memory or delay garbage collection
If one or more background tasks takes plenty of shared resources, they can be canceled and they are written to be fault tolerant so that they can pick up from where they left off.
The use of lookup keys is common to find entries in listings. The key generally comprises of a prefix and one or more values pertaining to related entities.
The type and number of keys can change even in the same listing. They can also be used as markers
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, the listing may be retrieved in ranges and the filtering may be taken over on the compute side.
No comments:
Post a Comment