{'fraction_non_alphanumeric': 0.009280742459396751, 'fraction_numerical': 0.0, 'mean_word_length': 5.392592592592592, '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}}
Electronic invoice system database architecture issues and the possible solutions

This paper elucidates electronic invoice system’s database architecture requirements and its building issues that one may encounter. Enumerated requirements and issues were taken into consideration and it is suggested to use three types of DB in the system. NoSQL model of database for its numbers of advantages is recommended for the information reused by users to store and querying them. The database is able to split database loadequally with the help of horizontal sharding. Making partition numbers equal to the number which has common divisors as much as possible will let splitting load amount equally among possible additional infrastructure. A special approach is required to each element of system to perfectly create architecture of the information system's database.