The National Transport University Bulletin

Abstract

Research in the field of design is considered, previously the problems of complexity were solved by developers through the correct choice of data structures and the development of algorithms, partly by separation of powers. Architectural styles are analyzed, a set of types of system components and a set of patterns of data transfer or control interactions are defined. EAI (Enterprise Application Integration) systems, sometimes called A2A (Application-to-Application Integration), are used to solve the first type of tasks, and B2B (Business-to-Business Integration) systems are used to solve the second type of tasks. In some situations, it is very difficult to determine the difference between A2A and B2B integration, since the complexity of some solutions within information systems may exceed the complexity of solutions for their joint functioning. A comparison is made of the use of different architectural styles, which are suitable for solving different tasks in terms of ensuring non-functional requirements, although the same functionality can be implemented using different styles. A practical model of combination, which creates a full-fledged system, is proposed. The immediate short-term advantage of the ESB approach is that it achieves the same overall effect as the EAI (hub-and-spoke) approach, but at a significantly lower total cost of ownership. These savings are realized not only through reduced hardware and software costs, but also through labor savings realized through the use of a distributed and flexible structure. A set of integration principles is defined and middleware is provided, which can consist of a combination of technologies and services that enable the integration of multiple systems. Software development architecture plays one of the key roles during development

Keywords: