{'fraction_non_alphanumeric': 0.01710261569416499, 'fraction_numerical': 0.0, 'mean_word_length': 5.633333333333334, '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}}
Comparison of consistency approaches for cloud databases

In the last few years, cloud computing has emerged as an exciting and successful paradigm for large-scale computing. Data sizes are increasing exponentially everyday, which makes data management applications potential candidates for deployment in a cloud. The maintenance of ACID properties is the primary obstacle to the implementation of transactional data management systems in a cloud. In particular, the distributed nature of a cloud platform is one of the main challenges of consistency maintenance. In this paper, we study three different techniques for maintaining consistency: the classic approach, the quorum approach and our tree-based consistency (TBC) approach. We identify the key controlling parameters of consistency maintenance in cloud databases and study the behaviour of the different techniques with respect to those parameters. Results demonstrate the advantages and weaknesses of the three consistency techniques.