{'fraction_non_alphanumeric': 0.01171875, 'fraction_numerical': 0.0, 'mean_word_length': 5.6869565217391305, '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}}
Handling mutual exclusion in a distributed application through Zookeeper

Zookeeper a powerful, feasible approach to build distributed applications implementing open APIs that enables developers to apply their own powerful co-ordination primitives. The aim of this study is twofold i) To study the anatomy and life cycle of zookeeper and make use of as a role of high-performance coordination service for distributed applications ii) a case study was presented about Zookeeper implementations in the payment process where synchronization and coordination is not meet due to dual server implementation, where orders are placed through an estore application. Finally the potentiality of Zookeeper replications is considered to address reliability and performance issues.