{'fraction_non_alphanumeric': 0.016408386508659983, 'fraction_numerical': 0.0, 'mean_word_length': 5.134078212290503, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Garbage collection in regions

The concept of regions provides for the ability to group and scope services across a network. Issues arise when entities of a region are no longer part of the region, due to a request to leave the region, an eviction by the region, or even component or network failures. Consequently, the references to these entities must be garbage collected. Depending on the purpose and design constraints of the region at hand, there can be many ways this can be implemented. Therefore, application designers must have the flexibility to implement a region design to incorporate a garbage collection scheme that meets their needs for correct semantics as well as performance and resource requirements. We have formulated a design for the region infrastructure that allows this flexibility and looked at various implementations of region designs built on top of this infrastructure. These proof-of-concept implementations allowed us to investigate some of the issues that arise regarding garbage collection. Thesis Supervisor: Karen R. Sollins Title: Principal Research Scientist