Deployment method, device and equipment of enterprise-level IT architecture, medium and program product

Abstract

The invention provides an enterprise-level IT architecture deployment method and device, equipment, a medium and a program product, and relates to the technical field of computers.The method comprises the steps that according to a preset partition rule, multiple architecture areas are divided, and each architecture area comprises at least one of a channel and external connection area, an online product and service area and a data and management analysis area; for each architecture area, a boundary and an interaction rule are configured for the architecture area, and the boundary comprises a first boundary used for inter-area access and / or a second boundary used for inter-area access of all functional modules in the architecture area, the interaction rules comprise a first interaction rule used for inter-region access and / or a second interaction rule used for access among functional modules in the same architecture region; and deploying to obtain the enterprise-level IT architecture according to the configuration results of the plurality of architecture regions. According to the application, an enterprise-level IT architecture meeting the requirements of credential industry development and host downward movement can be provided for a financial institution, so that financial services can be safely and efficiently processed.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a deployment method, device, equipment, medium and program product for an enterprise-level IT architecture. Background Art

[0002] Enterprise-level IT architecture refers to computer systems and network structures designed and implemented to meet the business needs of large enterprises. For financial enterprises, due to the complexity and security of their business, it is necessary to deploy a suitable enterprise-level IT architecture.

[0003] The current enterprise-level IT architecture mainly adopts a centralized product service layer design and a centralized application integration layer service registration mechanism, and is based on host deployment isolation. However, with the advancement of the information technology application innovation industry (hereinafter referred to as the information innovation industry) and the downward migration of host services, the strong isolation between services originally achieved through physical deployment no longer exists, and the application deployment method based on a single application integration layer and a single product service layer will lead to overly complex service call relationships and difficult management. Summary of the invention

[0004] The present application provides a deployment method, device, equipment, medium and program product for an enterprise-level IT architecture to solve at least one of the above problems.

[0005] In a first aspect, the present application provides a method for deploying an enterprise-level IT architecture, comprising:

[0006] According to the preset partitioning rules, multiple architecture areas are divided, each architecture area includes corresponding functional modules; wherein the architecture area includes at least one of the following: channel and external connection area, online product and service area, data and management analysis area, and the functional modules are used to build an enterprise-level IT architecture;

[0007] For each architecture area, a boundary and an interaction rule are configured for the architecture area, wherein the boundary includes a first boundary for inter-area access and / or a second boundary for access between functional modules in the architecture area, and the interaction rule includes a first interaction rule for inter-area access and / or a second interaction rule for access between functional modules in the same architecture area, to obtain configuration results of the multiple architecture areas;

[0008] According to the configuration results of the multiple architecture areas, an enterprise-level IT architecture is deployed.

[0009] In one embodiment, the method further comprises:

[0010] According to the business information of the enterprise, the online product and service area is divided into a plurality of business isolation areas, and the business isolation areas include a core area for processing key businesses and a peripheral area for processing auxiliary businesses.

[0011] In one implementation, configuring boundaries and interaction rules for each architecture region includes:

[0012] For the online product and service area, configuring a first boundary and a first interaction rule for other architecture areas to access the online product and service area for the online product and service area;

[0013] For each business isolation zone, a third boundary and a third interaction rule are configured for other business isolation zones to access the business isolation zone, so that the functional modules in each business isolation zone interact with the functional modules in other architecture areas based on the first boundary and the first interaction rule, and interact with the functional modules in other business isolation zones in the online product and service area based on the third boundary and the third interaction rule.

[0014] In one implementation, configuring, for each service isolation zone, a third boundary and a third interaction rule for other service isolation zones to access the service isolation zone includes:

[0015] For each business isolation zone, obtain the security access level of the business security isolation zone to obtain the security access level of each business isolation zone;

[0016] According to the security access level of each business isolation zone, a third boundary and a third interaction rule for other business isolation zones to access the business isolation zone are configured for each business isolation zone respectively.

[0017] In one embodiment, the configuring boundaries and interaction rules for the architecture regions;

[0018] configuring boundaries for the architecture area based on at least one of a predefined service registry, service discovery, and service proxy; and / or,

[0019] Interaction rules are configured for the architecture area according to at least one of predefined online transactions, event responses, and data synchronization.

[0020] In one embodiment, the partitioning rule is determined based on service information of the functional module, and the service information includes at least one of the following: channel-oriented service, product and application-oriented service, and data-oriented service;

[0021] The dividing of the plurality of architecture areas according to the preset partitioning rules includes at least one of the following:

[0022] According to the channel services oriented to the functional modules, the channels and external contact areas are divided; the channels include customer channels, employee channels and external contact channels;

[0023] The online product and service area is divided according to the functional modules for product and application services; among them, products and applications provide business processing services for channels;

[0024] According to the data services oriented to the functional modules, the data and management analysis areas are divided.

[0025] In one embodiment, configuring boundaries and interaction rules for the architecture area includes:

[0026] For the channel and the external zone, a first boundary and a first interaction rule for access by other regional architectures are configured for the channel and the external zone, and a fourth boundary and a fourth interaction rule for access by external terminals are configured for the channel and the external zone;

[0027] Wherein, business isolation is performed between the channel and the channels in the external connection area.

[0028] In one embodiment, the method further comprises:

[0029] A synchronization mapping relationship based on a data table is configured for the online product and service area and the data and management analysis area, and the data synchronization mapping relationship is used to synchronize the data generated by the online product and service area with the data stored in the data and management analysis area.

[0030] In a second aspect, the present application provides a deployment device for an enterprise-level IT architecture, including:

[0031] A partitioning module, used to divide a plurality of architecture areas according to preset partitioning rules, each architecture area including a corresponding functional module; wherein the architecture area includes at least one of the following: a channel and external connection area, an online product and service area, and a data and management analysis area, and the functional module is used to build an enterprise-level IT architecture;

[0032] an access configuration module, configured to configure, for each architecture region, a boundary and an interaction rule for the architecture region, wherein the boundary includes a first boundary for inter-region access and / or a second boundary for access between functional modules in the architecture region, and the interaction rule includes a first interaction rule for inter-region access and / or a second interaction rule for access between functional modules in the same architecture region, to obtain configuration results of the multiple architecture regions;

[0033] A deployment module is configured to deploy an enterprise-level IT architecture based on the configuration results of the multiple architecture areas.

[0034] In a third aspect, the present application provides an electronic device, comprising: a processor, and a memory communicatively connected to the processor;

[0035] The memory stores computer-executable instructions;

[0036] The processor executes the computer-executable instructions stored in the memory to implement the enterprise-level IT architecture deployment method provided in the first aspect above.

[0037] In a fourth aspect, the present application provides a computer-readable storage medium, in which computer execution instructions are stored. When the computer execution instructions are executed by a processor, they are used to implement the deployment method of the enterprise-level IT architecture provided in the first aspect above.

[0038] In a fifth aspect, the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the method for deploying the enterprise-level IT architecture provided in the first aspect above.

[0039] The deployment method, device, equipment, medium and program product of the enterprise-level IT architecture provided by the present application are divided into multiple architecture areas according to preset partitioning rules, each architecture area includes a corresponding functional module, and the architecture area includes at least one of the following: channel and external connection area, online product and service area, data and management analysis area, and the functional module is used to build an enterprise-level IT architecture; for each architecture area, the architecture area is configured with a boundary and an interaction rule, the boundary includes a first boundary for inter-area access and / or a second boundary for access between functional modules in the architecture area, the interaction rule includes a first interaction rule for inter-area access and / or a second interaction rule for access between functional modules in the same architecture area, and the configuration results of the multiple architecture areas are obtained. According to the configuration results of the multiple architecture areas, the enterprise-level IT architecture is deployed. In this process, by dividing the architecture area and configuring the corresponding boundaries and interaction rules for each architecture area, in the scenario of host business downshifting, there is no need to rely on the physical isolation of the host, and the complexity of the call is simplified. The enterprise-level IT architecture deployed in this way can effectively improve the security and efficiency of business processing, and is clearer and more convenient to manage than the existing 7+1 layer architecture. It can provide financial institutions with an enterprise-level IT architecture that meets the development needs of the information and innovation industry, so as to facilitate the safe and efficient processing of financial business. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0041] Figure 1 A schematic diagram of an enterprise-level IT architecture in the prior art;

[0042] Figure 2 A flowchart of a method for deploying an enterprise-level IT architecture provided in an embodiment of the present application;

[0043] Figure 3 A flowchart of another method for deploying an enterprise-level IT architecture provided in an embodiment of the present application;

[0044] Figure 4 for Figure 3 Schematic diagram of the process of step S201;

[0045] Figure 5 A flowchart of another method for deploying an enterprise-level IT architecture provided in an embodiment of the present application;

[0046] Figure 6 A schematic diagram of a possible enterprise-level IT structure provided in an embodiment of the present application;

[0047] Figure 7 A schematic diagram of the structure of a deployment device for an enterprise-level IT architecture provided in an embodiment of the present application;

[0048] Figure 8 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application.

[0049] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0050] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0051] In the technical solution of this application, the collection, storage, use, processing, transmission, provision and disclosure of financial data or user data and other information involved are in compliance with the provisions of relevant laws and regulations and do not violate public order and good morals. It should be noted that in the embodiments of this application, some existing solutions in the industry such as certain software, components, models, etc. may be mentioned, and they should be considered as exemplary. Their purpose is only to illustrate the feasibility of the implementation of the technical solution of this application, but it does not mean that the applicant has or will necessarily use the solution.

[0052] Enterprise-level IT architecture is a description of the business operations and IT support framework of an enterprise, usually including business architecture and IT architecture. IT architecture includes application architecture, data architecture, technical architecture and security architecture. Financial institutions usually have different IT architectures from ordinary enterprises due to the complexity and security of their business.

[0053] The enterprise-level IT architecture currently used by financial enterprises mainly adopts a (7+1) layer 12T architecture, such as Figure 1 As shown, including:

[0054] Channel integration layer 1 (P1, P2), this architecture layer is used to integrate channel access, accept business requests from different channels, process and encapsulate request data, call background services and return results; User service integration layer 2 (P3), this architecture layer is used to be customer-centric, integrate end-to-end customer service processes, and provide integrated services for internal and external users. It is based on an enterprise-level workflow engine that spans time, roles, and users, and calls the service logic of the product service layer to complete business processing; Application Integration Layer 3 (P4), the components of the product service layer publish services in the service directory of the application integration layer, and the service requester searches for services through the service directory; External Integration Layer 4 (P5), responsible for the interaction between external institutions and internal systems, such as insurance companies and credit reporting systems, mainly completes functions such as protocol conversion and message forwarding, and shields technical complexity for internal systems; Product Service Layer 5 (P6~P8), mainly for key banking business applications, such as deposits, loans, etc., published in the application integration layer P4 of the application integration layer; Data Integration Layer 6 (P9), integrates various types of data within the enterprise and provides consistent data calculation and access services; Management Analysis Layer 7 (P10~P12), provides centralized management analysis services and support for internal management and decision-making of the enterprise, including all management analysis components, and obtains the required data services from the data integration layer; Infrastructure and Governance Layer (+1), provides basic setting capabilities of IT architecture, such as transaction monitoring, application monitoring, etc.

[0055] It can be understood that the 12Ps from P1 to P12 refer to the different partitions in each of the seven system architecture levels for different business or system concerns, namely Figure 1 The block combination in each architecture layer. For example, P1 in the channel integration layer represents the customer channel, and P2 represents the employee channel. The P1 channel can be further divided into the Internet channel and the independent banking channel. The above channels can be further divided into mobile banking channels, ATM channels, etc.

[0056] The characteristics of the above-mentioned enterprise-level IT architecture are that it logically adopts a unified product service layer design, a centralized application integration layer service registration mechanism, and based on the principle that the host does not make outbound calls and the actual situation of the core business host concentration, the core business layer in the product service layer is mainly deployed in the host field, and the non-core business layer and the outbound call business related to the host business are deployed on an open platform, and the IT architecture is governed based on physical isolation. In other words, the current enterprise-level IT architecture adopts a centralized design strategy, which is specifically manifested in that all business services are concentrated in a unified product service layer, all services are registered and managed through a unified service registration center, and the isolation of business systems mainly depends on the physical deployment strategy of the host, and physical isolation is achieved by deploying different business systems on different hosts or host partitions or open platforms.

[0057] With the development of the information industry and the migration of business systems from traditional hosts to open platforms (such as cloud computing platforms, distributed computing platforms, etc.), the business hierarchical division originally achieved through physical deployment areas has become blurred, and the strong isolation between businesses achieved through physical deployment no longer exists. The application deployment method based on a single application integration layer and a single open platform product service layer will lead to overly complex service call relationships. If the above-mentioned enterprise-level IT architecture is still used, it will be difficult to ensure the security and efficiency of business processing, and the architecture will be difficult to govern due to the large number of architecture layers and complex call relationships. Therefore, it is necessary to adopt a new deployment method to deploy enterprise-level IT architecture, no longer relying on physical separation, and at the same time clarify the enterprise-level IT architecture to facilitate governance.

[0058] In view of this, the deployment method, apparatus, equipment, medium and program product of the enterprise-level IT architecture provided in the embodiments of the present application divides multiple architecture areas according to preset partitioning rules, each architecture area contains corresponding functional modules, and the architecture area includes at least one of the following: channel and external connection area, online product and service area, data and management analysis area, and the functional module is used to build an enterprise-level IT architecture; for each architecture area, a boundary and interaction rules are configured for the architecture area, and the boundary includes a first boundary for access between areas and / or a second boundary for access between functional modules in the architecture area, and the interaction rule includes a first interaction rule for access between areas and / or a second interaction rule for access between functional modules in the same architecture area, and obtains the configuration results of the multiple architecture areas, and deploys the enterprise-level IT architecture according to the configuration results of the multiple architecture areas. In this process, by dividing the architecture area and configuring corresponding boundaries and interaction rules for each architecture area, there is no need to rely on the physical isolation of the host in the scenario of host business moving downward, and the complexity of calling is simplified. The enterprise-level IT architecture deployed in this way can effectively improve the security and efficiency of business processing, and is clearer and easier to manage than the existing 7+1 layer architecture.

[0059] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0060] Figure 2 The following is a flow chart of a method for deploying an enterprise-level IT architecture provided in an embodiment of the present application. Figure 2 As shown, the method includes steps S201-S203.

[0061] Step S201, according to the preset partitioning rules, divide a plurality of architecture areas, each architecture area contains corresponding functional modules; wherein the architecture area includes at least one of the following: channel and external connection area, online product and service area, data and management analysis area, and the functional modules are used to build an enterprise-level IT architecture.

[0062] Exemplarily, those skilled in the art may adaptively determine partitioning rules in combination with enterprise architecture or business objectives, and divide the partitions into multiple architecture areas, which are also top-level areas, including channels and external relations areas, online products and services areas, and data and management analysis areas.

[0063] Among them, the channel and external connection area is used to support the customer-centric user interaction and business integration of the bank, which may include the channel integration layer, external connection integration layer, and user service integration layer. The functional modules of the channel and external connection area may include customer channels (such as mobile banking, ATM machines, etc.), employee channels, such as (counter systems, employee mobile client, etc.), external connection channels (such as bank-to-bank docking applications, and online transaction-related applications of the People's Bank of China), etc.; the online product and service area is used to divide the business areas and applications of the enterprise from an enterprise-level perspective, for example, it can be the implementation and interconnection interaction layer of the banking business by field, integrating the application integration layer and product service layer in the original IT architecture, and the functional modules in the online product and service area such as core (business) applications, peripheral (business) applications, etc.; the data and management analysis area is used to realize enterprise-level data aggregation and data analysis and data mining, analyze business and management functions, which can interact with the channel and external connection area and the online product and service area to realize data storage and analysis, integrating the business scope of the data integration layer and management analysis layer in the original IT architecture, and the functional modules in the data and management analysis area such as data applications or data analysis tools, etc.

[0064] Optionally, the partitioning rules of this embodiment can be determined based on the service information of the functional module, and the service information includes at least one of the following: channel service-oriented, product and application service-oriented, and data service-oriented; the above step S201 divides multiple architectural areas according to preset partitioning rules, including at least one of the following: dividing channel and external liaison areas according to the channel service-oriented functional module; wherein the channel includes customer channels, employee channels, and external liaison channels; dividing online product and service areas according to the product and application service-oriented functional module; wherein the products and applications provide business processing services for the channel; dividing data and management analysis areas according to the data service-oriented functional module.

[0065] The channel in this embodiment is the main way and interface for interacting with different groups of the enterprise (such as customers, employees within the enterprise, and external organizations). In financial institutions, it includes customer-oriented, employee-oriented, and external organizations. For example, mobile banking and ATM machines are customer-oriented and are divided into corresponding channels in the channel and external connection areas; business systems (such as transfer business, deposit and loan business, deposit and loan derivative business, etc.) are divided into the online product and service area. Specifically, the online product and service area can be divided into multiple autonomous areas (that is, business isolation areas, such as core areas and peripheral areas). Transfer business and deposit and loan business are divided into the core area as core businesses, and deposit and loan derivative business is divided into the peripheral area as auxiliary business. These business systems can provide business processing services for channels (such as mobile banking); data management tools, databases, etc. are divided into the data and management service area to provide data analysis, storage and other services for the entire IT architecture.

[0066] Compared with the IT architecture division in the prior art, this embodiment performs partitioning based on the service information of the functional modules, and its division and deployment efficiency is higher, and the architecture hierarchy (there is a clear responsibility classification between architecture areas) is clearer.

[0067] Step S202: for each architecture area, configure boundaries and interaction rules for the architecture area, wherein the boundaries include a first boundary for inter-area access and / or a second boundary for access between functional modules in the architecture area, and the interaction rules include a first interaction rule for inter-area access and / or a second interaction rule for access between functional modules in the same architecture area, to obtain configuration results of the multiple architecture areas.

[0068] In this embodiment, considering the host migration scenario, corresponding boundaries and interaction rules are configured for each architecture area, thereby improving the security and clarity of the entire IT architecture. Among them, the first boundary of inter-area access is also the boundary of each architecture area itself. In other words, each architecture area includes a regional boundary. When other architecture areas need to access this architecture area, they must comply with the boundary rules of this architecture area (such as boundary entrances and entrance criteria). The second boundary of access between functional modules in the architecture area, that is, the boundary of each functional module in the architecture area, for example, the channels in the channel and external connection area are isolated from each other, and the core applications and peripheral applications in the online product and service area may have some core applications and peripheral applications that need to interact with data (such as deposit and loan business and deposit and loan derivative business), and data intercommunication or isolation is achieved according to the access control of the boundary.

[0069] For example, the configuration of the boundaries and interaction rules of channels and outreach areas may be as follows:

[0070] For the channel and the external zone, a first boundary and a first interaction rule for access by other regional architectures are configured for the channel and the external zone, and a fourth boundary and a fourth interaction rule for access by external terminals are configured for the channel and the external zone; wherein business isolation is performed between the channels in the channel and the external zone.

[0071] In this example, for channels and external areas, enterprise boundaries and channel internal access boundaries are configured according to business needs. Enterprise boundaries refer to the boundary rules that need to be met when external parties (such as customers, external organizations or employees) access channels. Channel internal access boundaries refer to the access boundaries between channels. In this embodiment, in view of the business characteristics of financial institutions, the boundaries between channels are isolated and not connected to each other. Each channel interacts with other architecture areas (such as initiating requests to online product and service areas to perform corresponding business processing). It can be understood that within the top-level area of ​​this layer, based on the terminal characteristics of the three channels, user permissions and interaction methods are different. Therefore, based on the channel isolation principle between the three channels, each channel should independently interact with the product business layer boundary entrance, and no interaction occurs between the top-level channels.

[0072] In actual applications, in channels and external areas, such as customer channels, interaction rules can be configured for different segmented channels, such as (mobile banking, online banking), etc., and services can be integrated according to their business types or business similarities (for example, through the user service integration layer), and then interact with the boundary entrances of other architectural areas (such as online products and service areas).

[0073] It should be noted that, in this embodiment, the first boundaries of each architectural area can adopt the same boundary or different boundaries. In order to improve the security of the architecture, the first boundaries of different architectural areas adopt different boundaries, and the same applies to the second boundary, third boundary, fourth boundary, etc.

[0074] In an optional implementation manner, configuring the boundary and interaction rules for the architecture area in the above steps may include the following steps:

[0075] Boundaries are configured for the architecture region based on at least one of a predefined service registry, service discovery, and service proxy.

[0076] In this embodiment, through the service registration, discovery and proxy mechanism, it is possible to isolate the services of each architectural area (or multiple partitions of the same architectural area such as the core area and the peripheral area) at the logical level, so that the services of different architectural areas (or the core area and the peripheral area) are logically independent and do not interfere with each other.

[0077] For example, taking the boundary configuration of the core area and the peripheral area as an example, the boundary of the core area and the peripheral area is configured by using service registration. Service registration refers to registering the service information (such as service name, address, port, etc.) to a centrally managed service registration center. This registration center can be a database or a special service registration tool (such as Eureka, Consul, etc.). For the service registration of the core area, the services in the core area are registered to the service registration center dedicated to the core area, and this registration center only contains the service information of the core area. For the service registration of the peripheral area, the services in the peripheral area will be registered to the service registration center dedicated to the peripheral area, and this registration center only contains the service information of the peripheral area; service discovery, service consumers (such as applications or other services) find and obtain the information of the required services through the service registration center. For example, service consumers in the core area will only visit the service registration center of the core area to discover and call the services in the core area. For service discovery of the peripheral area, service consumers in the peripheral area will only visit the service registration center of the peripheral area to discover and call the services in the peripheral area; service proxy, that is, in the process of service calling, the service request is transferred and controlled through the proxy mechanism. The proxy can be an intermediate layer responsible for processing the routing, load balancing, security verification, etc. of the service request. Core area service proxy: service requests in the core area will be processed by the service proxy in the core area, ensuring that the request only flows within the core area. Peripheral area service proxy: service requests in the peripheral area will be processed by the service proxy in the peripheral area, ensuring that the request only flows within the peripheral area. In this way, even in the same physical network, the services between different areas are completely isolated logically, ensuring their independence and security.

[0078] In some embodiments, the design and implementation of the relevant boundaries can be implemented by improved service registration, service discovery, and service proxy architecture, or by other means. In actual applications, multi-level boundaries can be configured for the enterprise-level IT architecture (i.e., multiple areas are divided and configured and edited within the top-level area). When implementing the specific physical layer, taking into account IT practices, a unified physical architecture and the principle of logical isolation can be adopted to implement access control based on the logical boundaries of services and applications based on access rights. It is also possible to deploy the access boundaries of the physical layer at multiple logical levels based on the actual IT situation of the enterprise. Similarly, it is also possible to implement multi-level access control boundaries with logical control and physical independent deployment based on actual system traffic. Based on the principle of regional and service boundary division, when designing and publishing services, enterprises can establish a service management system to design and publish the access control configuration of each service based on different responsibility boundaries before the service is officially released.

[0079] In addition, the above steps of configuring boundaries and interaction rules for the architecture area may also include the following steps: configuring interaction rules for the architecture area according to at least one of predefined online transactions, event responses, and data synchronization.

[0080] Among them, online transaction refers to transaction activities conducted through the network. It usually involves multiple steps, such as user authentication, data transmission, payment processing, etc. The online transaction system needs to ensure the security and integrity of the data; event response refers to the actions taken by the system when a specific event (such as user operation, system alarm, etc.) is detected, which can include triggering specific functions, sending notifications, recording logs, etc.; data synchronization refers to the process of maintaining data consistency between multiple systems or devices. In practical applications, data conflicts, delays and other problems need to be resolved to ensure that all participants can access the latest data. In this embodiment, the online and product service area and the data and management analysis area adopt data line transactions (ETL, DB-level data synchronization).

[0081] For example, configure the interactive rules of event response for the channel and external connection area, configure the interactive rules of online transaction for the core area in the online product and service area, and configure the interactive rules of data synchronization for the data and management analysis area. In addition to the above rules, the interactive rules can also define the corresponding communication protocols, data formats, etc., so as to realize the interaction between areas (or modules).

[0082] It should be noted that those skilled in the art may also determine corresponding boundaries and interaction rules in combination with actual application adaptability.

[0083] Step S203: deploy an enterprise-level IT architecture according to the configuration results of the multiple architecture areas.

[0084] In this embodiment, after completing the boundaries and interaction rules of each architecture area, the enterprise-level IT architecture can be deployed. In some embodiments, the functional modules of each architecture area can be deployed according to the above configuration results to ensure that the functional modules of each area can operate normally and communicate according to the boundaries and interaction rules. For example, for channels and external connections, an application programming interface (API) gateway can be deployed, external interfaces and security policies can be configured, and interfaces with external systems can be deployed and configured to ensure the secure transmission of data and services; for online products and services areas, core business services such as user management, order processing, payment services, etc. can be deployed, and necessary middleware such as message queues, cache services, etc. can be deployed; data and management analysis areas can be deployed, such as deploying databases, data warehouses, databases and other data storage systems, such as deploying data analysis tools, platforms, etc., and configuring data collection and analysis processes.

[0085] In the above technical solution, by dividing the architecture area and configuring corresponding boundaries and interaction rules for each architecture area, there is no need to rely on the physical isolation of the host in the scenario of host business migration, and the complexity of calling is simplified. The enterprise-level IT architecture deployed in this way can effectively improve the security and efficiency of business processing, and is clearer and more convenient to manage than the existing 7+1 layer architecture.

[0086] Figure 3 This is a flow chart of another enterprise IT architecture deployment method provided by an embodiment of the present application. Based on the above embodiment, this embodiment improves security and simplifies the complexity of calling by dividing the online product and service area into multiple business isolation areas. Specifically, in addition to the above steps S201-S203, the method provided by this embodiment may also include step S301:

[0087] Step S301: Divide the online product and service area into a plurality of business isolation areas according to the business information of the enterprise, wherein the business isolation areas include a core area for processing key businesses and a peripheral area for processing auxiliary businesses.

[0088] In this embodiment, the online product and service area takes the bank's capabilities as the core, defines the business capabilities that the bank can provide from the overall IT system and application level, and is an application deployment and governance area from an enterprise-level perspective. This architecture area abandons the two-level concept of the application integration layer and the product service layer in the original IT architecture. On the basis of the top-level area of ​​the online product and service area, it divides multiple autonomous business areas (i.e., business isolation areas) according to the bank's business needs. Each area can contain its autonomous regional boundaries, and the business area contains multiple applications. The application is a logical application, which contains a logical application service boundary, and the boundary contains a service set published by the logical application. Specifically, the architecture area can be divided into a core (product service) area and a peripheral (product service) area, wherein each business isolation area can be further divided into multiple independent areas, such as the peripheral area is divided into a deposit and loan derivative business area, an inclusive business area, etc. Each area establishes its own business and service boundaries, as well as external and internal interaction rules.

[0089] In the prior art, through a centralized service registration mechanism, all service calls and integrations are managed and coordinated in the same architecture layer, which will lead to overly complex call relationships when making service calls. This embodiment further partitions online products and servers based on the partitions of the top-level area. In actual applications, service calls can be made according to corresponding partitions, which greatly simplifies the problem of call complexity.

[0090] In some embodiments, in combination Figure 4As shown, in the above step S201, for each architecture area, configuring boundaries and interaction rules for the architecture area may include the following steps:

[0091] Step S201a: for the online product and service area, configure a first boundary and a first interaction rule for other architecture areas to access the online product and service area.

[0092] It should be noted that the configuration method of the first boundary and the first interaction rule can be found in the above description and will not be repeated here.

[0093] In this embodiment, the core area itself is defined as a service application and an external application. The interaction rules can be exemplified as follows: the core area provides direct external online transaction access, and does not provide direct request services for core external services. Specifically, the core area's external requests are provided by the core area's outbound call service. This type of service is based on the principle that core services do not make outbound calls. When the core area receives an online transaction that requires an outbound call, such as (inter-bank real-time payment), it acts as a peripheral proxy application for the core service, receives the request of the requesting party, and interacts with the core and external applications when necessary. The interaction with the core adopts a non-suspended mode, that is, a real-time direct service request or a subsequent request based on events and event responses. When the core service is designing a business, if it encounters a business that requires an outbound call, the business should be split into two sub-businesses, and the response processing should be based on independent events.

[0094] Optionally, the services published by the core area can be managed at three levels, including the application layer, the core area layer, and the enterprise layer. Among them, the application layer service is published at the logical application boundary and is only requested within the logical application scope of the published service. Its design and management authority lies in the project or application-level application architecture management department. The core area layer service is an application that is published by a specific application, published within the core area boundary, and visible within the core area layer. Its design, release, and management belong to the core area application architecture management department. The enterprise layer service belongs to the service or event mechanism and data line mechanism that the core area application publishes to the enterprise top-level area boundary and is accessed by the product business layer application or other top-level area application outside the core area. The design, release, and management of this type of interaction need to be globally controlled by the enterprise-level architect; the peripheral product service area can establish an independent application and service area similar to the core area. According to the specific characteristics of the product service area, a three-layer service governance (application layer, regional layer, and enterprise layer) can be established or reduced to two layers (enterprise layer and regional layer) and one layer (non-layered) service governance according to the actual situation. The application architect and architecture department of the business area are responsible for the application division and service governance work within this layer.

[0095] Step S201b: For each business isolation zone, configure a third boundary and a third interaction rule for other business isolation zones to access the business isolation zone, so that the functional modules in each business isolation zone interact with the functional modules in other architecture areas based on the first boundary and the first interaction rule, and interact with the functional modules in other business isolation zones in the online product and service area based on the third boundary and the third interaction rule.

[0096] In this embodiment, the third boundary, in addition to being the access boundary between business isolation zones, also includes the access boundary of other architecture areas to the business isolation zone. In other words, if the functional modules in the channel and external connection zone need to initiate a request to the application in the core business zone, the request needs to pass through the first boundary and the second boundary before it can reach the core business isolation zone. For other partitions in the online product and service area except the core area and the peripheral area, if the corresponding third boundary is not configured, the request can reach the other partitions after passing through the first boundary of the online product and service area, and interact according to the corresponding interaction rules.

[0097] In some embodiments, the above-mentioned channels and external connection areas, data and analysis areas can also be divided into multiple sub-areas according to actual needs. The principle is similar to that of the above-mentioned online product and service areas, and will not be elaborated here.

[0098] Furthermore, in order to facilitate the governance of each area, the corresponding boundaries and interaction rules can be configured in combination with the security access level of each business isolation zone. Specifically, the above step S201b configures the third boundary and third interaction rules for other business isolation zones to access the business isolation zone for each business isolation zone, which can be configured in the following manner:

[0099] For each business isolation zone, obtain the security access level of the business security isolation zone to obtain the security access level of each business isolation zone;

[0100] According to the security access level of each business isolation zone, a third boundary and a third interaction rule for other business isolation zones to access the business isolation zone are configured for each business isolation zone respectively.

[0101] In this embodiment, the security access level can be predetermined by the user in the early stage of deployment, and the security access level can be divided in combination with the actual application. For example, the security access level of the core area is higher than that of the peripheral area, and the corresponding boundaries and interaction rules are configured for each business isolation area according to different security access levels. Based on this approach, the deployment security and flexibility of the enterprise-level IT architecture can be effectively improved.

[0102] Figure 5This is a flow chart of another method for deploying an enterprise-level IT architecture provided by an embodiment of the present application. Based on the above embodiment, this embodiment can ensure the consistency of data in the enterprise-level IT architecture by configuring a synchronization mapping relationship based on a data table for the relevant architecture area. Specifically, in addition to the above steps S201-S203, the method may also include:

[0103] Step S501: configure a synchronization mapping relationship based on a data table for the online product and service area and the data and management analysis area, the data synchronization mapping relationship is used to synchronize the data generated by the online product and service area with the data stored in the data and management analysis area. The configuration results of multiple architecture areas include a synchronization mapping relationship based on a data table.

[0104] In this embodiment, based on the synchronization mapping relationship of the data table, that is, based on the table-level peer mapping synchronization, the table level refers to data synchronization in units of database tables, rather than in smaller (such as rows, columns) or larger (such as the entire database) units. Synchronous mapping refers to a one-to-one correspondence between the tables in the two areas. For example, a user table UserTable in the online product and service area also has a corresponding user table UserTable in the data management and analysis area. The data in the two areas can be copied or updated to another area to ensure that the data in the two areas are consistent. Specifically, the data in a database table in the online product and service area can be synchronized to the corresponding table in the data management and analysis area. This synchronization is based on the table level, that is, each table has a corresponding synchronization relationship, and the synchronization process ensures that the table data in the two areas are consistent. For example, the online product and service area has a user table UserTable, which contains basic information of users, and the data management and analysis area also has a user table UserTable, which is used to store and analyze user data. The synchronization mapping relationship based on the table level will ensure that the data changes in the UserTable in the online product and service area (such as adding new users, updating user information) will be synchronized to the UserTable in the data management and analysis area in a timely manner. Exemplarily, for the online product and service area and the data and management area, a synchronization mapping relationship based on a data table is configured, which can be implemented by associating data tables (information), that is, the association and binding between UserTables in the above example.

[0105] In some embodiments, the application isolation principle of the data source (the boundaries and interaction rules of the above-mentioned different partitions) can also be combined to realize the synchronization mapping relationship based on the data table, so as to jointly realize the governance of the IT architecture. Exemplarily, under the above-mentioned data synchronization rules, the data receiving function module of the data and management analysis area can be configured with rules for consistency of the structure and data content of the original data and the data source and isolation of each level, as well as rules for the processing of the derived data and data reorganization of data analysis in other data storage areas of the data and management analysis area, so as to ensure the consistency and isolation of the data.

[0106] In summary, the technical solution provided in this embodiment can effectively solve the problems and challenges faced by enterprise-level IT architecture governance based on the development of the information and innovation industry and the implementation of the mainframe migration of large banks. On the basis of the existing IT architecture design, it combines the architectural hierarchy division, boundary and interaction rule configuration, etc., to provide financial institutions with an enterprise-level IT architecture that meets the development needs of the information and innovation industry, so as to facilitate the safe and efficient processing of financial business. Figure 6 As shown, Figure 6 A possible schematic diagram of an enterprise-level IT architecture deployed based on the above-mentioned enterprise-level IT architecture deployment method is shown. It can be seen that compared with the existing enterprise-level IT architecture, the architecture is clearer and more reasonable.

[0107] Figure 7 It is a structural diagram of a deployment device of an enterprise-level IT architecture provided by this application, such as Figure 7 As shown, the device 700 includes a partition module 701, an access configuration module 702 and a deployment module 703, wherein:

[0108] Partitioning module 701, used to divide multiple architecture areas according to preset partitioning rules, each architecture area includes corresponding functional modules; wherein the architecture area includes at least one of the following: channel and external connection area, online product and service area, data and management analysis area, and the functional modules are used to build an enterprise-level IT architecture;

[0109] An access configuration module 702 is used to configure a boundary and an interaction rule for each architecture area, wherein the boundary includes a first boundary for inter-area access and / or a second boundary for access between functional modules in the architecture area, and the interaction rule includes a first interaction rule for inter-area access and / or a second interaction rule for access between functional modules in the same architecture area, to obtain configuration results of the multiple architecture areas;

[0110] The deployment module 703 is configured to deploy an enterprise-level IT architecture according to the configuration results of the multiple architecture areas.

[0111] In one embodiment, the partitioning module 701 is further configured to divide the online product and service area into multiple business isolation areas according to the business information of the enterprise, and the business isolation areas include a core area for processing key businesses and a peripheral area for processing auxiliary businesses.

[0112] In one implementation, the access configuration module 702 includes:

[0113] A first configuration unit, configured to configure, for the online product and service area, a first boundary and a first interaction rule for other architecture areas to access the online product and service area;

[0114] The second configuration unit is configured to configure, for each business isolation zone, a third boundary and a third interaction rule for other business isolation zones to access the business isolation zone, so that the functional modules in each business isolation zone interact with the functional modules in other architecture areas based on the first boundary and the first interaction rule, and interact with the functional modules in other business isolation zones in the online product and service area based on the third boundary and the third interaction rule.

[0115] In one embodiment, the second configuration unit is specifically configured to obtain the security access level of the business security isolation zone for each business isolation zone, and obtain the security access level of each business isolation zone; according to the security access level of each business isolation zone, a third boundary and a third interaction rule for other business isolation zones to access the business isolation zone are configured for each business isolation zone respectively.

[0116] In one implementation, the access configuration module 702 includes:

[0117] A third configuration unit, configured to configure a boundary for the architecture area according to at least one of predefined service registration, service discovery, and service proxy; and / or,

[0118] A fourth configuration unit is configured to configure interaction rules for the architecture area according to at least one of predefined online transactions, event responses, and data synchronization.

[0119] In one embodiment, the partitioning rule is determined based on service information of the functional module, and the service information includes at least one of the following: channel-oriented service, product and application-oriented service, and data-oriented service;

[0120] The partition module 701 includes at least one of the following: dividing the channel and external liaison areas according to the functional module oriented to channel services; wherein the channels include customer channels, employee channels and external liaison channels; dividing the online product and service areas according to the functional module oriented to product and application services; wherein the products and applications provide business processing services for the channels; dividing the data and management analysis areas according to the functional module oriented to data services.

[0121] In one implementation, the access configuration module 702 includes:

[0122] A fifth configuration unit is configured to configure, for the channel and the external zone, a first boundary and a first interaction rule for access by other regional architectures for the channel and the external zone, and to configure a fourth boundary and a fourth interaction rule for access by external terminals for the channel and the external zone;

[0123] Wherein, business isolation is performed between the channel and the channels in the external connection area.

[0124] In one embodiment, the device further comprises:

[0125] The data configuration module is set to the online product and service area and the data and management analysis area, and configures a synchronization mapping relationship based on a data table. The data synchronization mapping relationship is used to synchronize the data generated by the online product and service area with the data stored in the data and management analysis area.

[0126] The above-mentioned device provided in the embodiment of the present application can be used to execute the technical solution of the deployment method of the enterprise-level IT architecture in the above-mentioned embodiment. Its implementation principle and technical effect are similar and will not be repeated here.

[0127] It should be noted that it should be understood that the division of the various modules of the above device is only a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated. And these modules can all be implemented in the form of software called by processing elements; they can also be all implemented in the form of hardware; some modules can also be implemented in the form of software called by processing elements, and some modules can be implemented in the form of hardware. For example, the partition module 701 can be a separately established processing element, or it can be integrated in a chip of the above device. In addition, it can also be stored in the memory of the above device in the form of program code, and called and executed by a processing element of the above device. The function of the partition module 701. The implementation of other modules is similar. In addition, all or part of these modules can be integrated together, or they can be implemented independently. The processing element here can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each module above can be completed by an integrated logic circuit of hardware in the processor element or instructions in the form of software.

[0128] Figure 8 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. Figure 8 As shown, the electronic device may include: a transceiver 81 , a processor 82 , and a memory 83 .

[0129] The processor 82 executes the computer execution instructions stored in the memory, so that the processor 82 executes the scheme in the above embodiment. The processor 82 can be a general-purpose processor, including a central processing unit CPU, a network processor (NP), etc.; it can also be a digital signal processor DSP, an application-specific integrated circuit ASIC, a field programmable gate array FPGA or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.

[0130] The memory 83 is connected to the processor 82 via a system bus and completes communication between them. The memory 83 is used to store computer program instructions.

[0131] The transceiver 81 can be used to exchange data with .

[0132] The system bus can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The system bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus. The transceiver is used to realize the communication between the database access device and other computers (such as clients, read-write libraries, and read-only libraries). The memory may include random access memory (RAM) and may also include non-volatile memory.

[0133] The above-mentioned electronic device provided in the embodiment of the present application can be used to execute the technical solution of the deployment method of the enterprise-level IT architecture in the above-mentioned embodiment. Its implementation principle and technical effect are similar and will not be repeated here.

[0134] The embodiment of the present application also provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement the deployment method of the enterprise-level IT architecture provided in the above embodiment.

[0135] The above-mentioned medium provided in the embodiment of the present application can be used to execute the technical solution of the deployment method of the enterprise-level IT architecture in the above-mentioned embodiment. Its implementation principle and technical effect are similar and will not be repeated here.

[0136] The embodiments of the present application also provide a computer program product, including a computer program, which, when executed by a processor, implements the deployment method of the enterprise-level IT architecture provided in the above embodiments.

[0137] The above-mentioned program product provided in the embodiment of the present application can be used to execute the technical solution of the deployment method of the enterprise-level IT architecture in the above-mentioned embodiment. Its implementation principle and technical effect are similar and will not be repeated here.

[0138] The embodiment of the present application also provides a chip for executing instructions, which is used to execute the deployment method of the enterprise-level IT architecture in the above embodiment. The implementation principle and technical effect are similar and will not be repeated here.

[0139] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of modules is only a logical function division, and there may be other division methods in actual implementation, such as multiple modules can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or modules, which can be electrical, mechanical or other forms.

[0140] The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to implement the solution of this embodiment.

[0141] In addition, each functional module in each embodiment of the present application can be integrated into one processing unit, or each module can exist physically separately, or two or more modules can be integrated into one unit. The above-mentioned module-composed unit can be implemented in the form of hardware or in the form of hardware plus software functional units.

[0142] The above-mentioned integrated module implemented in the form of a software function module can be stored in a computer-readable storage medium. The above-mentioned software function module is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to perform some steps of the methods of various embodiments of the present application.

[0143] It should be understood that the processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), etc. A general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in the invention may be directly implemented as being executed by a hardware processor, or may be implemented by a combination of hardware and software modules in the processor.

[0144] The memory may include a high-speed RAM memory, and may also include a non-volatile storage NVM, such as at least one disk memory, and may also be a USB flash drive, a mobile hard disk, a read-only memory, a magnetic disk or an optical disk, etc.

[0145] The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, the bus in the drawings of the present application is not limited to only one bus or one type of bus.

[0146] The above storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. The storage medium can be any available medium that can be accessed by a general or special purpose computer.

[0147] An exemplary storage medium is coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and the storage medium can be located in an application specific integrated circuit (ASIC). Of course, the processor and the storage medium can also exist as discrete components in an electronic control unit or a main control device.

[0148] Those skilled in the art can understand that all or part of the steps of implementing the above-mentioned method embodiments can be completed by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the steps of the above-mentioned method embodiments are executed; and the aforementioned storage medium includes: ROM, RAM, disk or optical disk and other media that can store program codes.

[0149] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit it. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A method for deploying an enterprise-level IT architecture, characterized in that: include: According to the preset partitioning rules, multiple architecture areas are divided, each architecture area includes corresponding functional modules; wherein the architecture area includes at least one of the following: channel and external connection area, online product and service area, data and management analysis area, and the functional modules are used to build an enterprise-level IT architecture; For each architecture area, a boundary and an interaction rule are configured for the architecture area, wherein the boundary includes a first boundary for inter-area access and / or a second boundary for access between functional modules in the architecture area, and the interaction rule includes a first interaction rule for inter-area access and / or a second interaction rule for access between functional modules in the same architecture area, to obtain configuration results of the multiple architecture areas; According to the configuration results of the multiple architecture areas, an enterprise-level IT architecture is deployed.

2. The method according to claim 1, characterized in that Also includes: According to the business information of the enterprise, the online product and service area is divided into a plurality of business isolation areas, and the business isolation areas include a core area for processing key businesses and a peripheral area for processing auxiliary businesses.

3. The method according to claim 2, characterized in that The configuring of boundaries and interaction rules for each architecture area includes: For the online product and service area, configuring a first boundary and a first interaction rule for other architecture areas to access the online product and service area for the online product and service area; For each business isolation zone, a third boundary and a third interaction rule are configured for other business isolation zones to access the business isolation zone, so that the functional modules in each business isolation zone interact with the functional modules in other architecture areas based on the first boundary and the first interaction rule, and interact with the functional modules in other business isolation zones in the online product and service area based on the third boundary and the third interaction rule.

4. The method according to claim 3, characterized in that The configuration of the third boundary and the third interaction rule for other service isolation zones to access the service isolation zone for each service isolation zone includes: For each business isolation zone, obtain the security access level of the business security isolation zone to obtain the security access level of each business isolation zone; According to the security access level of each business isolation zone, a third boundary and a third interaction rule for other business isolation zones to access the business isolation zone are configured for each business isolation zone respectively.

5. The method according to any one of claims 1 to 4, characterized in that: said configuring boundaries and interaction rules for said architecture regions; configuring boundaries for the architecture area based on at least one of a predefined service registry, service discovery, and service proxy; and / or, Interaction rules are configured for the architecture area according to at least one of predefined online transactions, event responses, and data synchronization.

6. The method according to any one of claims 1 to 4, characterized in that: The partitioning rule is determined according to service information of the functional module, wherein the service information includes at least one of the following: channel-oriented service, product and application-oriented service, and data-oriented service; The dividing of the plurality of architecture areas according to the preset partitioning rules includes at least one of the following: According to the channel services oriented to the functional modules, the channels and external contact areas are divided; the channels include customer channels, employee channels and external contact channels; The online product and service area is divided according to the functional modules for product and application services; among them, products and applications provide business processing services for channels; According to the data services oriented to the functional modules, the data and management analysis areas are divided.

7. The method according to any one of claims 1 to 4, characterized in that: The configuring boundaries and interaction rules for the architecture area includes: For the channel and the external zone, a first boundary and a first interaction rule for access by other regional architectures are configured for the channel and the external zone, and a fourth boundary and a fourth interaction rule for access by external terminals are configured for the channel and the external zone; Wherein, business isolation is performed between the channel and the channels in the external connection area.

8. The method according to any one of claims 1 to 4, characterized in that: Also includes: A synchronization mapping relationship based on a data table is configured for the online product and service area and the data and management analysis area, and the data synchronization mapping relationship is used to synchronize the data generated by the online product and service area with the data stored in the data and management analysis area.

9. A deployment device for an enterprise-level IT architecture, characterized in that: include: A partitioning module, used to divide a plurality of architecture areas according to preset partitioning rules, each architecture area including a corresponding functional module; wherein the architecture area includes at least one of the following: a channel and external connection area, an online product and service area, and a data and management analysis area, and the functional module is used to build an enterprise-level IT architecture; an access configuration module, configured to configure, for each architecture region, a boundary and an interaction rule for the architecture region, wherein the boundary includes a first boundary for inter-region access and / or a second boundary for access between functional modules in the architecture region, and the interaction rule includes a first interaction rule for inter-region access and / or a second interaction rule for access between functional modules in the same architecture region, to obtain configuration results of the multiple architecture regions; A deployment module is configured to deploy an enterprise-level IT architecture based on the configuration results of the multiple architecture areas.

10. An electronic device, characterized in that: include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the enterprise-level IT architecture deployment method according to any one of claims 1-8.

11. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, they are used to implement the deployment method of the enterprise-level IT architecture according to any one of claims 1 to 8.

12. A computer program product, characterized in that It comprises a computer program, which, when executed by a processor, implements the method for deploying the enterprise-level IT architecture according to any one of claims 1 to 8.

Images