Enterprise integrated service platform based on cloud native architecture and construction and application method thereof

Abstract

The embodiment of the invention provides an enterprise integration service platform based on a cloud native architecture and a construction and application method thereof, and relates to the technical field of service platforms. The platform comprises a message service integration module used for providing creation, distribution, execution and management of messages and message channels; the application service integration module is used for providing plug-ins and APIs; the service integration full-life-cycle management module is used for realizing classified display and detail display of the capability, and capability-based retrieval and API management; the platform base integrated service monitoring module is used for providing an integrated service quantity, accessing a service source system, analyzing and displaying a service state, and providing data and detailed page development; and the asset visualization module is used for monitoring the operation state and the operation data of the message integration service module and the application service integration service through a visual interface. According to the implementation mode provided by the invention, multiple problems confronted by a traditional enterprise in a digital transformation process are solved.

Description

Technical Field

[0001] The present application relates to the technical field of service platforms, and particularly to an enterprise integration service platform based on a cloud-native architecture, a construction method of an enterprise integration service platform based on a cloud-native architecture, an application method of an enterprise integration service platform based on a cloud-native architecture, and an electronic device. Background Art

[0002] In recent years, with the rapid development of information technology and the booming rise of the digital economy, more and more enterprises have begun to focus on digital transformation to improve business operation efficiency and market competitiveness. As one of the core driving forces for promoting digital transformation, cloud computing technology has played a crucial role.

[0003] Traditional integration platforms are usually built based on local infrastructure, aiming to connect different business systems and applications, solve data exchange and functional collaboration between different systems, and achieve data sharing and circulation. Such platforms rely on predefined integration patterns and fixed architecture designs to achieve interconnection between different systems. However, in practical applications, traditional integration platforms face significant limitations. First, since different departments and subsidiaries have adopted their own technical architectures in the construction of their respective business systems, lacking a unified standard and platform, the complexity of integration and management has increased significantly. Second, the design of traditional platforms often makes business systems operate independently, and it is difficult to achieve a closed loop in internal processes. As a result, information transmission and decision-making processes lag, unable to meet the enterprise's demand for efficient and smooth business collaboration. In addition, the lack of unified standards in aspects such as interconnection, security guarantee, and management efficiency of traditional integration platforms restricts the efficient aggregation of cloud data and the seamless connection of systems, hindering the intensive utilization of enterprise information resources.

[0004] Facing these challenges, cloud-native technology has emerged and gradually become an important means to promote enterprise transformation. The cloud-native architecture provides a more flexible and dynamic management mode through emerging technical means such as containerization, microservices, and service meshes, and can meet the needs of enterprises in a changing market environment. Compared with traditional platforms, the cloud-native architecture not only has higher agility and elasticity, but also supports rapid iteration and deployment of applications, and can significantly improve development efficiency and resource utilization. Therefore, the transformation of the integration service platform to the cloud-native architecture can not only effectively improve application productivity, but also promote the evolution of enterprises from the traditional "local development, offline delivery" mode to the new "cloud development, online deployment" mode, achieving a comprehensive improvement in resource management and application operation and maintenance efficiency. Summary of the Invention

[0005] The purpose of the embodiments of the present application is to provide an enterprise integration service platform based on a cloud-native architecture and its construction and application methods, aiming to provide full-life-cycle application system management support from aspects such as design, development, testing, integration, deployment, and operation through a unified technical architecture and standards, and to provide cloud-native service capabilities for SaaS applications. Improve the interconnection capabilities of enterprises during the digital transformation process, promote data liquidity and information sharing, and help enterprises achieve more efficient operation and decision-making, so as to solve at least some of the problems in the background technology.

[0006] To achieve the above object, the present application provides an enterprise integration service platform based on a cloud-native architecture. The platform includes: a message service integration module for providing creation, allocation, execution, and management of messages and message channels; an application service integration module for providing plugins and APIs; a service integration full-life-cycle management module for realizing classified display and detailed display of capabilities, as well as retrieval based on capabilities and management of APIs; a platform base integration service monitoring module for providing analysis and display of the number of integration services, access service source systems, and service status, and providing data and detailed page development; and an asset visualization module for monitoring the running status and running data of the message integration service module and the application service integration service through a visual interface.

[0007] Optionally, the message service integration module includes: a Topic creation unit for supporting the expansion of millions of Topic quantities through a computing and storage separation architecture; a tenant isolation unit for supporting multi-tenancy through two key concepts of tenant and namespace; a publish-subscribe management unit for consumers to be combined to consume messages, where each consumption group is a subscription, and consumers can have different consumption methods: exclusive, failover, or shared; a message resending unit for re-consuming messages that have failed to be processed by specifying the number of message retries or the delay of message resending; and an online expansion unit for supporting online expansion by adopting a computing and storage separation architecture design.

[0008] Optionally, the application service integration module includes: a traffic control unit for supporting traffic control according to multiple dimensions; an authentication and authorization unit for supporting multiple built-in authentication methods and enabling other authentication methods through custom plugins; a forwarding proxy unit for supporting forwarding proxies of multiple protocols to achieve access and load balancing of multiple backend services; a speed limit policy unit for supporting speed limit policies for different dimensions; a cache acceleration unit for supporting caching of API response results; and a log recording unit for supporting real-time recording of API access logs and providing a visual log query and analysis tool.

[0009] Optionally, the service integration full life cycle management module includes: an API development unit for implementing unified and standardized management of integration interfaces, preparing interface design specifications, and forming a unified, collaborative, and standardized API management tool; an API degradation unit for supporting multiple degradation control strategies; an API online testing unit for supporting test case management and invocation of test cases; a routing management unit for supporting static routing policies based on a configured routing table; a visual and drag-and-drop service orchestration unit for encapsulating the entire process into a data object for saving and restoring the service orchestration diagram; a status management unit for querying the transaction log list and service information of the service; an authentication management unit for supporting the Token authentication method for OpenAPI interfaces; a log statistics and analysis unit for providing multi-dimensional API statistical reports; an API monitoring unit for providing performance monitoring, log collection, and log analysis functions; and an API load balancing unit for supporting configuration of load weights when there are multiple URL addresses for the same service at the backend.

[0010] Optionally, the platform base integration service monitoring module includes: an operation log unit for comprehensively monitoring various operation metrics of the system; an API capability operation unit for supporting monitoring of API capability operations; a capability comprehensive display unit for comprehensively displaying the capabilities of the integrated service platform; a service link tracing unit for providing a topology diagram of the call relationships of each component for the services in the API gateway, and providing the entire data link tracing based on the relationship topology diagram; and a log unified management unit for providing a unified log management function for the services in the API gateway.

[0011] Optionally, the asset visualization module includes: a message integration service display unit for monitoring and displaying the running status of the message service integration module and displaying the statistical data of message production / consumption; a service integration service display unit for monitoring and displaying the running status of the application service integration module; and an asset graph analysis unit for displaying API assets using a knowledge graph.

[0012] Optionally, the platform further includes an authentication and authorization module, and the authentication and authorization module includes an access permission policy control sub-module set based on different service access relationships, and the different service access relationships include: access between internal services, access of internal services to external services, and access of external services to internal services.

[0013] In this application, a method for constructing an enterprise integration service platform based on a cloud-native architecture is also provided. Based on the aforementioned enterprise integration service platform based on a cloud-native architecture, the method includes: adopting a Spring Cloud microservices architecture, with the front-end presentation implemented using Vue, and the system providing services to users in a B / S mode; using Nginx plus lua scripts as the gateway layer; setting a data layer on the gateway layer, with etcd database used for the core data in the data layer; setting an application layer on the data layer, with the application layer developed using the Spring Boot framework and Mybatis as the persistence layer framework; the platform is hosted by a distributed server cluster, distributing traffic to multiple servers in the distributed server cluster through load balancing technology, using an elastic scaling mechanism to schedule server resources, and using a monitoring and alarm mechanism to monitor the system status in real time and predict potential problems.

[0014] In this application, a method for applying an enterprise integration service platform based on a cloud-native architecture is also provided. Based on the aforementioned enterprise integration service platform based on a cloud-native architecture, the method includes: obtaining a user instruction based on the front-end, and starting one of the integration service registration process, integration service usage process, and message service consumption process based on the user instruction; the integration service registration process includes: API design, API development, API testing, submitting a registration request, and approval; the integration service usage process includes: API signing, initiating a signing application, first-level approval, and second-level approval; the message service consumption process includes: applying to use the message service, allocating tenant permissions, allocating namespaces, customizing Topics, customizing consumption policies, and consuming messages.

[0015] In this application, an electronic device is also provided, including: at least one processor; a memory connected to the at least one processor; wherein, the memory stores instructions executable by the at least one processor, and the at least one processor implements the aforementioned enterprise integration service platform based on a cloud-native architecture, the method for constructing an enterprise integration service platform based on a cloud-native architecture, or the method for applying an enterprise integration service platform based on a cloud-native architecture by executing the instructions stored in the memory.

[0016] In this application, a machine-readable storage medium is also provided. Instructions are stored on the machine-readable storage medium, and when the instructions are executed by a processor, the processor is configured to execute and implement the aforementioned enterprise integration service platform based on a cloud-native architecture, or the method for constructing an enterprise integration service platform based on a cloud-native architecture, or the method for applying an enterprise integration service platform based on a cloud-native architecture.

[0017] In this application, a computer program product is also provided, including a computer program which, when executed by a processor, implements the aforementioned enterprise integration service platform based on a cloud-native architecture, the construction method of the enterprise integration service platform based on a cloud-native architecture, or the application method of the enterprise integration service platform based on a cloud-native architecture.

[0018] The above technical solution has the following beneficial effects:

[0019] (1) Unified standards and efficient management. By constructing a unified technical architecture and a standardized API gateway, the present invention significantly reduces the management complexity of enterprises in cloud platform construction. Each business system achieves seamless docking through standard interfaces, avoiding the data island problem caused by system fragmentation in the past. This unified and standardized design enables enterprises to quickly integrate when expanding new applications, improving the overall management efficiency.

[0020] (2) Comprehensive data aggregation and sharing capabilities. By introducing a variety of sensors and data collection devices in the perception layer, the present invention can collect and aggregate data from different business systems in real time. This ability not only improves the data liquidity but also provides a solid foundation for subsequent data analysis and decision-making. Through the powerful computing power of the cloud platform, enterprises can achieve in-depth data mining, improving the accuracy and timeliness of business decisions.

[0021] (3) Full-link performance monitoring and rapid problem location. Combining link tracing technology, the present invention realizes full-link monitoring of interfaces and services. This innovation not only provides in-depth performance visibility, helping enterprises to promptly discover performance bottlenecks, but also can quickly locate the problem source. This full-link monitoring ability significantly improves the operation and maintenance efficiency of enterprises, reduces the fault recovery time, and ensures the continuity and stability of business.

[0022] (4) Reducing operation and maintenance costs and improving resource utilization rate. Through the innovation of cloud-native application development and operation and maintenance management capabilities, enterprises can achieve service-oriented management of resources, reducing the dependence on local hardware resources. Developers can complete coding, debugging, and application deployment in the cloud, maximizing the resource advantages of cloud computing. This method not only reduces the infrastructure investment cost of enterprises but also improves the resource utilization rate, achieving the optimization of cost-effectiveness.

[0023] (5) Improving business flexibility and adaptability. The integration service platform of the present invention can support the efficient collaboration of multi-functional teams, accelerating the digital transformation pace of enterprises. Through flexible data processing and monitoring capabilities, enterprises can quickly respond to market changes and business requirements, improving business flexibility and adaptability. This feature enables enterprises to maintain a continuous competitive advantage in the increasingly competitive market environment.

[0024] (6) Security and self - controllability. In response to security risks in cloud computing, the present invention emphasizes the construction of self - controllable technologies. By strengthening the security protection of self - built data centers and reducing dependence on foreign technologies, the security of the enterprise's core business data is ensured. This improvement in security not only enhances customer trust but also lays a foundation for the sustainable development of the enterprise.

[0025] Other features and advantages of the embodiments of the present application will be described in detail in the subsequent specific implementation section. Brief Description of the Drawings

[0026] The drawings are used to provide a further understanding of the embodiments of the present application and constitute a part of the specification. They are used together with the following specific implementation to explain the embodiments of the present application, but do not limit the embodiments of the present application. In the drawings:

[0027] Figure 1 Schematically shows the architecture diagram of the enterprise integration service platform based on the cloud - native architecture according to the embodiment of the present application;

[0028] Figure 2 Schematically shows the internal structure diagram of the electronic device according to the embodiment of the present application. Specific Implementation Modes

[0029] The following details the specific implementation modes of the embodiments of the present application with reference to the drawings. It should be understood that the specific implementation modes described herein are only used to illustrate and explain the embodiments of the present application and do not limit the embodiments of the present application.

[0030] Figure 1 Schematically shows the architecture diagram of the enterprise integration service platform based on the cloud - native architecture according to the embodiment of the present application. As Figure 1 shown, the enterprise integration service platform based on the cloud - native architecture includes:

[0031] A message service integration module for providing creation, allocation, execution, and management of messages and message channels;

[0032] An application service integration module for providing plugins and APIs;

[0033] A service integration full - life - cycle management module for realizing classification display and detailed display of capabilities, as well as retrieval based on capabilities and management of APIs;

[0034] A platform base integration service monitoring module for providing analysis and display of the number of integration services, access service source systems, and service status, and providing data and detailed page development; and

[0035] An asset visualization module is used to monitor the running status and running data of the message integration service module and the application service integration service through a visual interface. The authentication and authorization module therein is an optional module.

[0036] In the above embodiments, the integration service platform is used to comprehensively manage and govern the integration of various enterprise systems, build an integration monitoring system, precipitate service capabilities, form enterprise integration assets, and manage the integration assets in a visual manner. The core of the integration service construction is to achieve resource serviceification, service assetization, asset visualization, technology standardization, unified service governance, and one-stop operation through global service governance and by referring to models such as the OpenAPI market.

[0037] In some embodiments of the present application, the specific settings and functions of the message service integration module are as follows. The Topic creation unit supports the creation of a large number of Topics: Through an architecture that separates computing and storage, it can support the expansion of the number of Topics in the millions, and at the same time, it can always maintain good performance. This is a huge improvement. In contrast, Kafka does not separate computing and storage, and when there are more Topics, it will affect its sequential I / O, and the performance will decline seriously. It is suitable for IoT scenarios. The tenant isolation unit realizes tenant isolation: It supports multi-tenancy through two key concepts, tenants and namespaces, and the multi-tenancy nature is mainly reflected in the URL of the topic. The publish-subscribe management unit realizes publish-subscribe management: A Topic is a channel for sending messages. Each message in a Topic can be used multiple times according to the subscription needs of consumers. Each subscription corresponds to a consumer group, and each Topic can have different consumer groups. Consumers are grouped together to consume messages, and each consumer group is a subscription. Consumers can have different consumption methods: exclusive, failover, or shared. The message resend unit realizes message resending: Usually, cancellation confirmation can be used to achieve the purpose of reprocessing messages after message processing fails. Failed messages can be re-consumed by specifying the number of message retries and the delay of message resending. The online expansion unit realizes online expansion: It adopts an architecture design that separates computing and storage to support online expansion.

[0038] In some embodiments of the present application, the application service integration module provides important functions such as routing matching, load balancing, service discovery, API management, etc. in its core, as well as basic modules such as configuration management. In addition, the plugin runtime is also included, providing a runtime framework for native Lua plugins, a runtime framework for multi-language plugins, and an experimental Wasm plugin runtime, etc. The multi-language plugin runtime provides support for multiple development languages, such as Golang, Java, Python, JS, etc. Currently, various types of plugins are also built-in, covering various fields of the API gateway, such as authentication and authorization, security, observability, traffic management, multi-protocol access, etc. The currently built-in plugins are implemented using native Lua. For the introduction and usage methods of each plugin, please refer to the relevant plugin documentation. The specific settings and functions of the application service integration module are as follows.

[0039] The traffic control unit implements traffic control: It supports traffic control based on dimensions such as IP, API, and user to avoid system crashes or malicious attacks. The authentication and authorization unit implements authentication and authorization: It supports authentication methods such as OAuth2 and JWT, and other authentication methods can be implemented through custom plugins to ensure the security of the API. The forwarding proxy unit implements forwarding proxy: It supports forwarding proxies for protocols such as HTTP, HTTPS, and WebSocket, and can implement access to multiple backend services and load balancing. The rate limiting policy unit implements rate limiting policies: It supports rate limiting policies for multiple dimensions such as users, APIs, and IPs to avoid excessive consumption of APIs by malicious users or programs. The cache acceleration unit implements cache acceleration: It supports caching API response results to reduce the load on the backend service and improve the response speed of the API. The log recording unit implements log recording: It supports real-time recording of API access logs and provides visual log query and analysis tools to facilitate users' monitoring and problem troubleshooting.

[0040] In some embodiments of the present application, the service integration full life cycle management module realizes the classified display and detailed display of capabilities. It can retrieve capabilities according to the source of capabilities, operation status, capability name, or API ID, facilitating users to view how to enable the capability. It supports the API registration function and realizes functions such as one-point registration of API interfaces, application information management, access permission management, full life cycle management of APIs, API version management, API import, API signing, API approval, capability catalog management, and capability catalog query. It provides API design, API gateway, and monitoring services, covering the full life cycle management of API development, release, invocation, statistics, monitoring, and decommissioning, and provides the ability to quickly, securely, and at low cost connect, open, and govern capabilities, services, and data in the form of APIs. It uniformly solves issues such as authentication, authorization, authentication, security, traffic control, caching, service routing, protocol conversion, gray release, monitoring, and alarm in the API governance life cycle.

[0041] The specific settings and functions of the service integration full life cycle management module are as follows. API development realizes the unified and standardized management of integration interfaces, formulates interface design specifications, standardizes the R & D process of the R & D team from API definition, management to automated testing, forms a unified, collaborative and standardized API management tool, and improves the collaboration efficiency of the API R & D team.

[0042] The API degradation unit provides the API degradation function, supporting multiple degradation control strategies, including timeout degradation (returning the default value when timed out), failure times degradation (degrading when the availability rate drops), traffic limiting, fault degradation (degrading when relying on external system failures), and denial of service degradation.

[0043] The API online testing unit supports API online testing, test case management and test case reuse. It supports saving the existing call messages (including information such as call paths and request parameters) as test cases, and can automatically use the saved test cases for testing when the API is released according to the configuration. Through the ability dial test function, users can perform self-service test creation or sign-up for the ability API on the page. The page can automatically generate the call path, packet header, and packet body required for the request according to the ability information and user information.

[0044] The routing management unit provides routing management capabilities, supporting static routing policies based on configured routing tables; supporting route selection according to actual user needs. The integrated service platform parses and combines APIs, processes data conversion, and distributes each combination link in the combined API; routes messages to different endpoints according to different conditions, which can be divided into static routing and dynamic routing.

[0045] The visual and drag-and-drop service orchestration unit provides visual and drag-and-drop service orchestration capabilities. It can encapsulate the entire process into a data object for saving and use to restore the service orchestration diagram. The integrated service platform parses the service message process and returns the final result to the client caller. The following principles should be followed: the orchestrated service should be stateless and automated, and there should be no manual processing process; service composition and orchestration obtain new services by combining and orchestrating the original services according to business requirements.

[0046] The status management unit provides the ability of status management. It can query the transaction log list of the service, including log contents such as the time of service transaction, service code, service call component, service call institution, internal processing time of the integrated service platform, service provider processing time, success or exception status, exception code, message flow endpoint execution time, transaction request message, and response message. This helps quickly analyze the reasons for API positioning exceptions.

[0047] The authentication management unit provides the ability of authentication management, supporting functions such as Token authentication mode of OpenAPI interface, black and white list control, national cryptography authentication, API fusing strategy, API capability authorization, etc., improving the security of calls.

[0048] The log statistical analysis unit provides log statistical analysis functions, such as indicators like API call times, success and failure rates, response time, API call exceptions, growth trends, etc. The integrated service platform provides multi-dimensional API statistical reports, which can count the API call times according to business domains, business systems, time periods, callers / callees, etc., and can summarize into more advanced indicators according to the corresponding dimensions. It can display curve graphs according to dimensions such as call volume, success rate, and average time-consuming.

[0049] The API monitoring unit provides API monitoring, providing functions such as performance monitoring, log collection and analysis, etc. It provides API integration topology capabilities. The integrated service platform can display the integration relationship topology diagram between internal modules of the system, as well as the connection status between modules. It can display the global integration relationship topology diagram between systems, as well as the connection status between systems.

[0050] The API load balancing unit provides API load balancing capabilities. When there are multiple URL addresses for the same service at the backend, the platform supports configuring load weights to achieve load balancing of server-side interfaces. The integrated service platform can provide a unified interface service list display, but lacks detailed descriptions such as user permission management, online joint debugging, and interface usage methods. The interface management platform isolates personal permissions according to tenant spaces through unified management, and views, jointly debugs, and exports interfaces within the permission scope. It supports importing interfaces in formats such as Postman, JSON, and Swagger, supports automated interface testing, and can view and download test reports after the test is completed.

[0051] In some embodiments of the present application, the integrated service monitoring module of the platform base analyzes and displays the number of integrated services, the access service source systems, and the service status, and provides data and detailed page development. Exemplarily, it includes:

[0052] The operation log unit implements the monitoring and management module to support the large-screen data display of the integrated service platform. It is mainly responsible for comprehensively monitoring various operation indicators of the system, providing complete operation logs, error logs, audit logs, and message logs, and supporting multiple log retrieval methods. The API capability operation unit implements the monitoring of API capability operation, supports the monitoring of fluctuations in capability call situations, process monitoring, and host monitoring; supports early warning and exception handling, and functions such as early warning rule configuration and early warning reception method configuration. The capability comprehensive display unit implements the comprehensive display of the capabilities of the integrated service platform, including the display of data such as the directory list, service monitoring and alarm, service link tracing, and log management center in the API gateway of the integrated service platform. The service link tracing unit implements the service in the API gateway to provide a topology diagram of the call relationships of each component, and then can drill down from the topology diagram to the detailed performance of each functional component, module, and method, providing the entire data link tracing. In addition to using automatic probes to report data, annotations can also be used to manually upload business data in a buried-point manner; the tracking information can also be integrated into mainstream log frameworks for output, such as Log4j, Logback, etc. And the log unified management unit implements the log management center to provide unified log management functions for the services in the API gateway, unify the access of logs, and provide functions such as log storage, analysis, and search.

[0053] In some embodiments of the present application, the asset visualization module integrates and manages and monitors existing services through two dimensions of business domain and organizational structure. The integrated asset visualization management system mainly monitors the running status and running data of the message integration service and the service integration service through a visual interface. Exemplarily, it includes: The message integration service display unit implements the message integration service: mainly including the running status monitoring of the message integration service system and the statistical data of message production / consumption. Read the publish and subscribe information through the interface provided by Pulsar. The service integration service display unit implements the service integration service: provides the relevant information filling and management of the integrated service assets, and conducts data statistics on the running status monitoring of the service integration service system and the service interface calls, and can query according to content such as business domain and project; and the asset graph analysis unit implements the asset graph analysis: API assets are displayed using tools such as knowledge graphs.

[0054] In some embodiments of the present application, the platform further includes an authentication and authorization module, and the authentication and authorization module includes an access permission policy control sub-module set based on different service access relationships. The different service access relationships include:

[0055] Internal service access. When accessing internal services, it is necessary to distinguish whether the service has been integrated with 4A. If the original service has completed 4A integration or has configured an authentication policy, it is recommended to use basic authentication, such as Key-Auth, and cooperate with the Consumer to perform auxiliary authentication through the service name and version number. If the original service has not configured an authentication policy, use signature authentication such as JWT-Auth as the main authentication.

[0056] Internal service accessing external services. External services should have their own authentication policies to ensure security, and only perform basic authentication work to ensure security. Use basic authentication such as Key-Auth, and cooperate with the Consumer to perform authentication through the service name and version number.

[0057] External service accessing internal services. In this case, the target service is exposed from the intranet to the extranet area, and it is necessary to ensure the security of communication. Adopt a plug-in based on an authentication protocol, for example, use the OpenID-Connect plug-in for authentication. OpenID Connect (OIDC) is an identity authentication protocol based on OAuth 2.0, which can be docked with an identity authentication service that supports this protocol to achieve identity authentication for client requests. This application provides an authentication and authorization module to implement different access permission policies for different service access relationships.

[0058] To implement the aforementioned enterprise integration service platform based on the cloud-native architecture, the embodiment of this application also provides a construction method for the enterprise integration service platform based on the cloud-native architecture. The standard specifications followed by the platform construction comply with the relevant regulations and requirements uniformly formulated by the enterprise. The data interaction interfaces between this system and other systems follow the data format specifications of XML and JSON. The data interaction between different services and modules in the system follows the JMS specification. The push and circulation of messages generated in the system follow the JDBC specification.

[0059] The development language of this invention is mainly JAVA, adopting the Spring Cloud microservice architecture, and the front-end display is implemented using Vue. The system provides services to users in the B / S mode. The operating environment of this invention is mainly enterprise version Linux. In the production environment, if there are no special requirements, Linux needs to be used to run the application program.

[0060] The presentation layer adopts a front-end and back-end separation technology architecture and is developed through vue.js. vue.js is a lightweight front-end framework that supports features such as data-driven, componentization, and two-way binding. It is easy to learn and use, has good performance and maintainability, and is suitable for developing interactive single-page applications.

[0061] The application layer is developed using the Spring Boot framework. The application layer also uses Mybatis as the persistence layer framework. Mybatis is an excellent persistence layer framework that supports customized SQL, stored procedures, and advanced mapping, improving development efficiency and readability.

[0062] The data layer uses the database CERDB. CERDB is a database that supports features such as horizontal scalability, high availability, and high concurrency, and has good compatibility and stability, making it suitable as the core database for the data layer.

[0063] The core data configuration uses the etcd database, providing a reliable way to store data that needs to be accessed by distributed systems or machine clusters. The API control center writes the configuration data into ETCD, and the API gateway fetches the APIs and APP-related information from ETCD, thereby implementing functions such as access authentication, flow control, and routing.

[0064] Nginx + lua is used as the gateway layer, achieving high-performance, high-concurrency, and highly reliable network services, and supporting functions such as dynamic configuration, protocol conversion, and log processing.

[0065] In addition to using open-source frameworks and commercial software, the present invention also combines self-developed technologies and product integration. Through self-development, customized functional modules are developed for specific business requirements. And in order to ensure the stability of the integrated service platform during actual production operation, detailed testing and settings are carried out.

[0066] Regarding the system capacity and carrying capacity, the embodiments of the present application have carried out detailed data description and in-depth analysis. First, based on the historical data of business growth and industry trend prediction, clear performance indicators are set for the system: the system can support processing 10,000 requests per second and maintain a response time within 500 milliseconds in 99.9% of the cases. To achieve these performance indicators, high-performance servers, storage devices, and network devices are required, and the system architecture is optimized. High-performance servers that can process 1,000 concurrent requests per second are used, the storage devices have high-speed read and write capabilities, and the network devices ensure low latency and high bandwidth. Through load balancing technology, traffic is effectively evenly distributed to multiple servers, thereby improving the overall processing capacity of the system. The introduction of a distributed cache system effectively reduces data access latency, and the read speed is increased by more than 50%.

[0067] During actual operation, the present invention has carried out a large number of performance tests and stress tests. These tests not only simulate daily business scenarios but also cover the system performance in extreme cases. The test results show that the present invention can maintain a stable response time under 80% load and still maintain high-efficient data processing capabilities in high-concurrency scenarios.

[0068] To further enhance the system's carrying capacity, the present invention adopts an elastic scaling design. When the system load exceeds a preset threshold (for example, the CPU usage rate exceeds 75% or the number of concurrent requests exceeds 1000), it can automatically increase server resources to ensure that the system can still maintain a stable response time and performance level during peak periods. This design improves the resource utilization rate by 40% and the system availability to 99.95% when the system copes with sudden business growth.

[0069] At the same time, the present invention also establishes a perfect monitoring and alarm mechanism, which can monitor the system status in real time and predict potential problems. The monitoring system collects key performance indicator data once a minute, including CPU usage rate, memory occupancy, network traffic, and disk I / O, etc. Once the system indicators approach or exceed the threshold (for example, the CPU usage rate exceeds 75%), the system will immediately send an alarm to notify the operation and maintenance team so that they can take measures within 30 minutes before the problem occurs. Through these mechanisms, the system failure rate is reduced by 60%, ensuring that the system always maintains the best operating state.

[0070] In summary, this system not only has the characteristics of stability, high efficiency, and scalability, but also reaches the leading level in the industry in terms of system capacity and carrying capacity. By introducing mature technologies and tools in the industry and combining the advantages of independent research and development and product integration, the present invention realizes the rapid construction and efficient operation of the system, providing strong support for the rapid development of the business.

[0071] To enable those skilled in the art to better understand the solution of the present invention, the following will clearly and completely describe some operation processes provided by the application method of the enterprise integration service platform based on the cloud native architecture. Obviously, the described functional processes are only part of the functions of the present invention, rather than all the functions. The application method of the enterprise integration service platform based on the cloud native architecture provided in the embodiments of the present application includes that a user realizes one of the integration service registration process, the integration service usage process, and the message service consumption process based on front-end operations.

[0072] Among them, (1) The integration service registration process. The integration service registration process refers to the complete process in which a user creates, develops, tests, and finally submits an API for registration on the platform, aiming to ensure that the design and release of the API comply with the management standards of the platform. The process is as shown in the following figure.

[0073] 1) API design: The user designs the API according to specific business requirements, determines the functions, input and output parameters, and their interaction methods of the API, and ensures that the design can meet the actual usage scenarios and requirements.

[0074] 2) API Development: After the user completes the design, they start API development, write the implementation code, and ensure the correctness and efficiency of the API's functional logic, thus laying a foundation for subsequent testing and use.

[0075] 3) API Testing: After development is completed, the user conducts comprehensive testing on the API, including functional testing and performance testing, to verify the stability and response speed of the API and ensure that it can work properly in actual applications.

[0076] 4) Submitting a Registration Request: After the API passes the test, the user submits the API to the registration system, initiating the registration approval process for the API so that the newly created API can be officially incorporated into platform management.

[0077] 5) Approval: The project manager or administrator reviews the API registration request submitted by the user to confirm whether the API complies with the platform's management standards and security specifications. After passing the review, the API will be officially registered and released.

[0078] (2) Integrated Service Usage Process. The integrated service usage process involves the signing approval and permission confirmation steps before the user calls the registered API, ensuring permission management and security control during the call process. The process is as shown in the following figure.

[0079] 1) API Signing: Before using the API, the user needs to sign a contract with the API provider, clarify the rights and obligations of both parties, and ensure compliance with relevant usage rules and terms when calling the API.

[0080] 2) Initiating a Signing Application: The user fills in relevant information and submits a signing application according to the signing requirements, initiating the API signing approval process to ensure the transparency and standardization of the signing process.

[0081] 3) First-level Approval: The administrator conducts a preliminary review of the submitted signing application, evaluates the reasonableness and compliance of the business requirements, and ensures that all terms comply with company policies and platform regulations.

[0082] 4) Second-level Approval: If the first-level approval passes, the second-level approver will conduct a final review of the signing application to ensure that all relevant matters are properly handled and confirm the validity of the signing. When the signing conditions are not met, the approver can reject the signing request. The user can view the list of APIs for which they have completed the signing.

[0083] (3) Message Service Consumption Process. The message service consumption process involves the user using the message service function of the platform, especially message subscription, configuration of consumption strategies, and actual consumption of messages. The process is as shown in the following figure.

[0084] 1) Apply for using the message service: The user submits an application to use the message service function provided by the platform to create a message channel and configure the corresponding message processing policy.

[0085] 2) Allocate tenant permissions: The administrator processes the user's application and allocates the necessary tenant permissions to ensure that the use of the message service complies with the security requirements of data isolation.

[0086] 3) Allocate a namespace: The administrator allocates a specific namespace for the user to facilitate the management and organization of message resources and ensure that the message flows between different users do not interfere with each other.

[0087] 4) Customize the Topic: The user customizes the message Topic according to business requirements and sets specific publishing and subscribing rules to flexibly process messages in actual use.

[0088] 5) Customize the consumption policy: The user further configures the consumption policy of the message, defines parameters such as the processing order of messages and the number of concurrent processes to improve the efficiency and accuracy of message processing.

[0089] 6) Consume messages: The user starts to consume the subscribed messages according to the preset consumption policy to ensure that the messages can be delivered to the business system in a timely and accurate manner for processing.

[0090] In some embodiments of the present application, an electronic device is further provided, including: at least one processor; a memory connected to the at least one processor; wherein, the memory stores instructions executable by the at least one processor, and the at least one processor executes the foregoing enterprise integration service platform based on cloud native architecture, the construction method of the enterprise integration service platform based on cloud native architecture, or the application method of the enterprise integration service platform based on cloud native architecture. Its internal structure diagram can be as Figure 2 shown. Figure 2Schematically shown is an internal structure diagram of an electronic device according to an embodiment of the present application. The electronic device includes a processor A01, a network interface A02, a memory (not shown in the figure), and a database (not shown in the figure) connected through a system bus. Among them, the processor A01 of the electronic device is used to provide computing and control capabilities. The memory of the electronic device includes an internal memory A03 and a non-volatile storage medium A04. The non-volatile storage medium A04 stores an operating system B01, a computer program B02, and a database (not shown in the figure). The internal memory A03 provides an environment for the operation of the operating system B01 and the computer program B02 in the non-volatile storage medium A04. The network interface A02 of the electronic device is used to communicate with an external terminal through a network connection. When the computer program B02 is executed by the processor A01, it is used to implement an enterprise integration service platform based on a cloud-native architecture, a construction method of an enterprise integration service platform based on a cloud-native architecture, or an application method of an enterprise integration service platform based on a cloud-native architecture.

[0091] Those skilled in the art can understand that Figure 2 the structure shown in

[0092] is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the electronic device to which the solution of the present application is applied. The specific electronic device may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0093] In an embodiment provided by the present application, a machine-readable storage medium is provided. Instructions are stored on the machine-readable storage medium, and when the instructions are executed by a processor, the processor is configured to execute the aforementioned enterprise integration service platform based on a cloud-native architecture, the construction method of an enterprise integration service platform based on a cloud-native architecture, or the application method of an enterprise integration service platform based on a cloud-native architecture.

[0094] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0095] This application is described with reference to the flowcharts and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present application. It should be understood that each flow and / or block in the flowchart and / or block diagram can be implemented by computer program instructions, as well as the combination of flows and / or blocks in the flowchart and / or block diagram. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to generate a machine, such that the instructions executed by the processor of the computer or other programmable data processing devices generate means for implementing the functions specified in the Figure 1 one or more flows and / or blocks Figure 1 one or more blocks.

[0096] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, such that the instructions stored in the computer-readable memory generate a manufactured article including instruction means that implement the functions specified in the Figure 1 one or more flows and / or blocks Figure 1 one or more blocks.

[0097] These computer program instructions can also be loaded onto a computer or other programmable data processing device, such that a series of operation steps are executed on the computer or other programmable device to generate a computer-implemented process, and thus the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in the Figure 1 one or more flows and / or blocks Figure 1 one or more blocks.

[0098] In a typical configuration, a computing device includes one or more processors (CPUs), an input / output interface, a network interface, and memory.

[0099] The memory may include non-permanent memory in the form of computer-readable media, random access memory (RAM), and / or non-volatile memory, such as read-only memory (ROM) or flash memory (flash RAM). The memory is an example of computer-readable media.

[0100] A computer-readable medium includes both permanent and non-permanent, removable and non-removable media and can implement information storage by any method or technology. The information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassette tapes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer-readable medium does not include transitory computer-readable media such as modulated data signals and carrier waves.

[0101] It should also be noted that the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, such that a process, method, article or apparatus comprising a series of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article or apparatus. Without further limitation, an element defined by the statement "comprising an..." does not exclude the presence of additional identical elements in the process, method, article or apparatus comprising the element.

[0102] The above are only embodiments of the present application and are not intended to limit the present application. For those skilled in the art, various changes and modifications can be made to the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included within the scope of the claims of the present application.

Claims

1. An enterprise integration service platform based on cloud native architecture, characterized in that: The platform includes: Message service integration module, used to provide creation, allocation, execution and management of messages and message channels; Application service integration module, used to provide plug-ins and APIs; The service integration lifecycle management module is used to realize the classification and detailed display of capabilities, as well as capability-based retrieval and API management; The platform base integrated service monitoring module is used to analyze and display the number of integrated services, access service source systems, and service status, and provide data and detailed page development; and The asset visualization module is used to monitor the running status and running data of the message integration service module and the application service integration service through a visualization interface.

2. The platform according to claim 1, characterized in that The message service integration module includes: Topic creation unit, used to support the expansion of the number of topics to millions through a computing and storage separation architecture; Tenant isolation unit, used to support multi-tenancy through two key concepts: tenant and namespace; The publish-subscribe management unit is used to group consumers to consume messages. Each consumer group is a subscription, and consumers can have different consumption modes: exclusive, failover, or shared. A message resending unit, used to re-consume failed messages by specifying the number of message retries or the delay of message resending; and The online capacity expansion unit is used to support online capacity expansion by adopting a computing and storage separation architecture design.

3. The platform according to claim 1, characterized in that: The application service integration module includes: A flow control unit, which is used to support flow control according to multiple dimensions; Authentication and authorization unit, which supports multiple built-in authentication methods and can implement other authentication methods through custom plug-ins; The forwarding proxy unit is used to support forwarding proxies of multiple protocols and implement access and load balancing of multiple backend services; The speed limit strategy unit is used to support speed limit strategies for different dimensions; A cache acceleration unit, used to support caching of API response results; and The logging unit is used to support real-time recording of API access logs and provide visual log query and analysis tools.

4. The platform according to claim 1, characterized in that: The service integration full life cycle management module includes: API development unit, which is used to achieve unified and standardized management of integrated interfaces, compile interface design specifications, and form a unified, coordinated, and standardized API management tool; API degradation unit, used to support multiple degradation control strategies; API online testing unit, used to support test case management and test case calling; Routing management unit, used to support static routing policies based on configured routing tables; Visually draggable service orchestration unit, used to encapsulate the entire process into a data object and save it for restoring the service orchestration diagram; A status management unit, used to query the transaction log list and service information of the service; Authentication management unit, used to support the Token authentication method of the OpenAPI interface; Log statistics analysis unit, used to provide multi-dimensional API statistics reports; API monitoring unit, which provides performance monitoring, log collection and log analysis functions; and The API load balancing unit is used to support the configuration of load weight when there are multiple URL addresses for the same backend service.

5. The platform according to claim 1, characterized in that: The platform base integrated service monitoring module includes: Operation log unit, used to comprehensively monitor various operation indicators of the system; API capability operation unit, used to support the monitoring of API capability operations; A comprehensive capability display unit is used to comprehensively display the capabilities of the integrated service platform; A service link tracking unit, used to analyze the call relationship topology diagram of each component of the service provider in the API gateway, and provide the entire data link tracking based on the relationship topology diagram; and The unified log management unit is used to provide unified log management functions for services in the API gateway.

6. The platform according to claim 1, characterized in that: The asset visualization module includes: The message integration service display unit is used to monitor and display the running status of the message service integration module and display the statistical data of message production / consumption; A service integration service display unit, used to monitor and display the running status of the application service integration module; and The asset graph analysis unit is used to display API assets using the knowledge graph.

7. The platform according to claim 1, characterized in that The platform also includes an authentication module, which includes an access permission policy control submodule set based on different service access relationships, where the different service access relationships include: access between internal services, internal service access to external services, and external service access to internal services.

8. A method for constructing an enterprise integration service platform based on a cloud native architecture, based on the enterprise integration service platform based on a cloud native architecture as claimed in any one of claims 1 to 7, characterized in that: The method includes: The Spring Cloud microservice architecture is adopted, and the front-end display is implemented with Vue. The system provides services to users in a B / S mode. Use Nginx plus lua script as the gateway layer; A data layer is set on the gateway layer, and the core data in the data layer adopts etcd database; An application layer is set on the data layer, and the application layer is developed using the SpringBoot framework and Mybatis is used as the persistence layer framework; The platform is hosted by a distributed server cluster, distributes traffic to multiple servers in the distributed server cluster through load balancing technology, schedules server resources using an elastic scaling mechanism, and uses a monitoring and alarm mechanism to monitor system status in real time and predict potential problems.

9. An application method of an enterprise integration service platform based on a cloud native architecture, based on the enterprise integration service platform based on a cloud native architecture as claimed in any one of claims 1 to 7, characterized in that: The method comprises: Acquire a user instruction based on the front end, and start one of an integrated service registration process, an integrated service use process, and a message service consumption process based on the user instruction; The integration service registration process includes: API design, API development, API testing, submission of registration request and approval; The integration service usage process includes: API signing, signing application initiation, first-level approval and second-level approval; The message service consumption process includes: applying for the use of message services, allocating tenant permissions, allocating namespaces, customizing topics, customizing consumption strategies, and consuming messages.

10. An electronic device, characterized in that: include: at least one processor; a memory connected to the at least one processor; In which, the memory stores instructions that can be executed by the at least one processor, and the at least one processor implements the enterprise integration service platform based on cloud native architecture as described in any one of claims 1 to 7, or the method for constructing an enterprise integration service platform based on cloud native architecture as described in claim 8, or the method for applying an enterprise integration service platform based on cloud native architecture as described in claim 9 by executing the instructions stored in the memory.

Images