{'fraction_non_alphanumeric': 0.012444444444444444, 'fraction_numerical': 0.0, 'mean_word_length': 5.662721893491124, '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}}
Understanding legacy architecture patterns

While often being the not very well liked stepchild of IT departments, legacy information systems are valuable assets for companies. After many years of development and maintenance, these systems often contain valuable business logic and implement business processes that are nowadays unknown even to the owner of the system. However, maintenance and further development is often costly and requires an increased effort compared to modern applications. Hence, developing sound strategies for gradually modernizing these applications and lowering the associated costs is of paramount importance. For carrying out such strategies, it is useful to understand why and how certain aspects of these systems are implemented. At itestra, we have collected architectural patterns in legacy information systems and use these to understand legacy information systems better and avoid mistakes in the analysis of behavior of such legacy systems. We present these patterns here in order to facilitate the decision-making process in modernization projects and increase their success probability.