A cloud-native hybrid integration approach based on blockchain
Through the cloud-native hybrid integration method based on blockchain, the hybrid integration platform has been solved in different standards, complex networks, multi-protocol conversion and security issues in cross-cloud and cross-domain environments, and unified resource management in cross-network environments is realized and collaboration, providing solutions for rapid cloud access and cross-departmental business collaboration.
Patent Information
- Application Number
- CN202210083778.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-01-21
- Publication Date
- 2024-11-05
- Estimated Expiration
- 2042-01-21
AI Technical Summary
The existing hybrid integration platform faces different standards, complex networks, multi-protocol conversion, elastic scaling and security issues in cross-cloud and cross-domain environments, making it difficult to achieve rapid expansion and unified management.
Adopting a cloud-native hybrid integration method based on blockchain, the unified integration and collaboration of API authentication, data, messages and services are realized by building a cloud-native distributed gateway, unified integration service, designer orchestration and blockchain metadata access. .
It realizes intelligent resource request scheduling, unified integrated management of multi-network and multi-platform resources in a cross-network environment, supports cross-department, cross-network, and cross-platform data, service and message collaboration, and provides standards for rapid cloud access and cross-departmental business collaboration. Solution.
Smart Images

Figure CN114840329B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of service integration technology, and in particular to a cloud-native hybrid integration method based on blockchain. Background Art
[0002] The hybrid integration platform is based on multiple modes such as cross-cloud and local links to achieve an organic combination of applications, data, files, messages, etc. With the evolution of technology, cross-cloud and cross-domain modes have evolved to cross-end and are widely promoted in application scenarios such as edge computing.
[0003] In actual production environments, hybrid integration platforms face multiple problems during promotion:
[0004] 1) Different standards: The data and service standards of different application developers are different and cannot be unified in the short term;
[0005] 2) Complex networks: There are internal and external government networks, business-specific networks, and networks within networks;
[0006] 3) Multi-protocol conversion: RPC, RMI, SOAP, CORBA, JMS, MQTT, Restful and other protocols;
[0007] 4) Elastic expansion: In high-concurrency scenarios, ensure that data integration and message integration can be elastically expanded quickly;
[0008] 5) Security issues: There are risks in the secure transmission of data, services, and messages across departments. Summary of the invention
[0009] In response to the needs and shortcomings of current technological development, the present invention provides a cloud-native hybrid integration method based on blockchain.
[0010] The cloud-native hybrid integration method based on blockchain of the present invention adopts the following technical solutions to solve the above technical problems:
[0011] A cloud-native hybrid integration method based on blockchain, the implementation process of which includes:
[0012] Step S1: Build a cloud-native distributed gateway to implement identity and permission verification services for API access, API service high availability, circuit breaking, degradation, and elastic scaling services;
[0013] Step S2: In a multi-cloud environment, a unified integrated service is built on a heterogeneous virtualized resource pool based on container, kata, and kubernetes technologies, and the built integrated service is automatically registered with the cloud-native distributed gateway;
[0014] Step S3: Create a designer based on a web interface, which can realize the orchestration and scheduling of integration capabilities and ultimately provide an application-oriented service API;
[0015] Step S4: The user uses various integration capabilities through the blockchain and calls the integration services registered in the distributed gateway through the service API provided by the designer, ultimately achieving access to metadata in the distributed gateway.
[0016] Optionally, execute step S1, and the specific operations of building a cloud-native distributed gateway include:
[0017] Step S1.1, build an adapter through the microservice architecture development protocol to access different forms of services;
[0018] Step S1.2, uniformly manage metadata of adapter access services;
[0019] Step S1.3: Build a container image through the container to achieve rapid deployment of the cloud-native distributed gateway.
[0020] Optionally, all APIs provided by the built cloud-native distributed gateway support synchronous and asynchronous calls. When the access system selects the asynchronous call method according to actual business needs, the asynchronous call gateway will call back the result through the callback address provided by the user after the API is executed.
[0021] The built cloud-native distributed gateway records all API call logs and provides an API metering system. The logs include information such as the caller, API Code, input parameters, output parameters, response time, success and failure flags, and provide API collaborative statistical analysis functions.
[0022] Optionally, execute step S2 to build a data integration service. The construction process is as follows:
[0023] Step S2.1.1, realize unified adaptation of heterogeneous data sources through data persistence engine;
[0024] Step S2.1.2: Use the data access function to build a logical + physical data resource pool;
[0025] Step S2.1.3: Use the data subscription function to implement subscription / push management of the data integration service catalog;
[0026] After building the data integration service, data from different sources is accessed through adaptation, and data is pushed to subscribers through publish / subscribe methods to achieve real-time data flow and data collaboration across departments and networks.
[0027] Optionally, execute step S2 to build a message integration service. The construction process is as follows:
[0028] Step S2.2.1, adapting to the underlying infrastructure resources through the adapter, and adapting to the virtualization / container resource pool through the adapter, to achieve rapid construction of a multi-tenant message queue based on virtualization;
[0029] Step S2.2.2, using the application as a tenant and serving as a message service instance of an open message integration service;
[0030] Step S2.2.3, application development realizes the application of data / services through subscription / push mode;
[0031] Through the constructed message integration service, ① asynchronous call service is provided for the access party. At this time, the call request is transmitted in the form of message. The cloud native distributed gateway listens to the message and processes the task. After the processing is completed, a notification is sent to the message middleware. ② The computing tasks are decoupled to realize the message-based streaming computing service.
[0032] Optionally, execute step S2 to build a business integration service. The construction process is as follows:
[0033] Step S2.3.1, realize the registration access management of different services by adapting different protocols of http / tcp / socket;
[0034] Step S2.3.2: After the service registration is approved, the service catalog of the distributed gateway is automatically published by calling the API of the distributed gateway;
[0035] Step S2.3.3: The developer subscribes to and applies for the required services through the distributed gateway;
[0036] The API of the business integration service runs on the access system. The distributed gateway routes to the subsystem through the API Code and performs request / response conversion. At the same time, since the API will eventually be called on the access system, the distributed gateway needs to perform load balancing based on the configuration of the access system. For query APIs, the results are cached according to the API type and frequency to ensure efficient API calls.
[0037] Optionally, when executing step S3, the created designer provides a visual panel to create integrated orchestration tasks, supporting visual orchestration of data, service, and application-related components;
[0038] The created designer provides components for basic processes, data conversion, script execution, message queues, and process events to support cross-network and cross-application integration conversion, support scheduled and real-time integration modes, support encapsulating existing services and hybrid integration orchestration results into Restful APIs for external use, and combine data authentication and user authorization modes to achieve unified authorization management.
[0039] Optionally, step S4 is executed, and the access party system is mapped to a user within the organization. At this time,
[0040] The access system can deploy its own chaincode according to its own needs and provide SDK for calling integrated services.
[0041] The access system can also apply to create a channel, join a channel, or create a user. After approval, the channel can be created, joined, or a user can be created. The user can then download the CA certificate and access the blockchain.
[0042] Preferably, all API authorizations, data authorization process information, and result information are stored in the blockchain.
[0043] The cloud-native hybrid integration method based on blockchain of the present invention has the following beneficial effects compared with the prior art:
[0044] The present invention is suitable for intelligent scheduling of resource requests in a cross-network environment, and for unified integrated management of multiple networks, multiple platforms, and multiple resources. Through hybrid integrated orchestration and intelligent scheduling, it can realize application scenarios such as data collaboration, service collaboration, message collaboration, and device collaboration across departments, networks, and platforms, and provide a standard solution for rapid cloud migration of non-cloud applications and cross-departmental business collaboration. BRIEF DESCRIPTION OF THE DRAWINGS
[0045] Attached Figure 1 It is a flow chart of the method of the present invention. DETAILED DESCRIPTION
[0046] In order to make the technical solution, the technical problem solved and the technical effect of the present invention more clearly understood, the technical solution of the present invention is clearly and completely described below in conjunction with specific embodiments.
[0047] Embodiment 1:
[0048] Combined with Figure 1 This embodiment proposes a cloud-native hybrid integration method based on blockchain, and its implementation process includes:
[0049] Step S1: Build a cloud-native distributed gateway to implement identity and permission authentication services for API access, API service high availability, circuit breaking, degradation, and elastic scaling services.
[0050] The specific operations for building a cloud-native distributed gateway include:
[0051] Step S1.1, build an adapter through the microservice architecture development protocol to access different forms of services;
[0052] Step S1.2, uniformly manage metadata of adapter access services;
[0053] Step S1.3: Build a container image through the container to achieve rapid deployment of the cloud-native distributed gateway.
[0054] In this embodiment, all APIs provided by the cloud-native distributed gateway support synchronous calls and asynchronous calls. When the access system selects the asynchronous call method according to actual business needs, the asynchronous call gateway will call back the result through the callback address provided by the user after the API is executed.
[0055] In this embodiment, the cloud-native distributed gateway records all API call logs and provides an API metering system. The logs include information such as the caller, APICode, input parameters, output parameters, response time, success and failure flags, and provide API collaborative statistical analysis functions.
[0056] Step S2: In a multi-cloud environment, a unified integrated service is built on a heterogeneous virtualized resource pool based on container, kata, and kubernetes technologies, and the built integrated service is automatically registered with the cloud-native distributed gateway.
[0057] Execute step S2 to build integration services, including data integration services, message integration services, and business integration services.
[0058] (A) The process of building a data integration service is as follows:
[0059] Step S2.1.1, realize unified adaptation of heterogeneous data sources through data persistence engine;
[0060] Step S2.1.2: Use the data access function to build a logical + physical data resource pool;
[0061] Step S2.1.3: Use the data subscription function to implement subscription / push management of the data integration service catalog.
[0062] After building the data integration service, data from different sources is accessed through adaptation, and data is pushed to subscribers through publish / subscribe methods to achieve real-time data flow and data collaboration across departments and networks.
[0063] (B) The process of building a message integration service is as follows:
[0064] Step S2.2.1, adapting to the underlying infrastructure resources through the adapter, and adapting to the virtualization / container resource pool through the adapter, to achieve rapid construction of a multi-tenant message queue based on virtualization;
[0065] Step S2.2.2, using the application as a tenant and serving as a message service instance of an open message integration service;
[0066] Step S2.2.3: Application development realizes the application of data / services through subscription / push mode.
[0067] Through the constructed message integration service, ① asynchronous call service is provided for the access party. At this time, the call request is transmitted in the form of message. The cloud native distributed gateway listens to the message and processes the task. After the processing is completed, a notification is sent to the message middleware. ② The computing tasks are decoupled to realize the message-based streaming computing service.
[0068] (C) The process of building business integration services is as follows:
[0069] Step S2.3.1, realize the registration access management of different services by adapting different protocols of http / tcp / socket;
[0070] Step S2.3.2: After the service registration is approved, the service catalog of the distributed gateway is automatically published by calling the API of the distributed gateway;
[0071] Step S2.3.3: Developers subscribe to and apply for required services through the distributed gateway.
[0072] The API of the business integration service runs on the access system. The distributed gateway routes to the subsystem through the API Code and performs request / response conversion. At the same time, since the API will eventually be called on the access system, the distributed gateway needs to perform load balancing based on the configuration of the access system. For query APIs, the results are cached according to the API type and frequency to ensure efficient API calls.
[0073] Step S3: Create a designer based on a web interface, which can implement the orchestration and scheduling of integration capabilities and ultimately provide an application-oriented service API.
[0074] The designer created based on the web interface ① provides a visual panel to create integrated orchestration tasks and supports the visual orchestration of data, service, and application-related components; ② provides components for basic processes, data conversion, script execution, message queues, and process events to support cross-network and cross-application integration conversion, support scheduled and real-time integration modes, support encapsulating existing services and hybrid integrated orchestration results into Restful APIs for external use, and combines data authentication and user authorization modes to achieve unified authorization management.
[0075] Step S4: The user uses various integration capabilities through the blockchain and calls the integration services registered in the distributed gateway through the service API provided by the designer, ultimately achieving access to metadata in the distributed gateway.
[0076] In this step, the access system is mapped to a user within the organization.
[0077] The access system can deploy its own chaincode according to its own needs and provide SDK for calling integrated services.
[0078] The access system can also apply to create a channel, join a channel, or create a user. After approval, the channel can be created, joined, or a user can be created. The user can then download the CA certificate and access the blockchain.
[0079] Preferably, all API authorizations, data authorization process information, and result information are stored in the blockchain.
[0080] In summary, the cloud-native hybrid integration method based on blockchain of the present invention solves the problem of completing data integration, service integration, message integration, device integration, application integration, and hybrid orchestration between different networks and departments in a cross-network environment in a blockchain trusted environment.
[0081] The above specific examples are used to explain the principles and implementation methods of the present invention in detail. These examples are only used to help understand the core technical content of the present invention. Based on the above specific embodiments of the present invention, any improvements and modifications made by technicians in this technical field without departing from the principles of the present invention should fall within the scope of patent protection of the present invention.
Claims
1. A cloud-native hybrid integration method based on blockchain, characterized in that ,The implementation process includes: Step S1: Build a cloud-native distributed gateway to implement identity and permission verification services for API access, high availability, circuit breaking, degradation, and elastic scaling services for API services. The specific operations of building a cloud-native distributed gateway include: Step S1.1, build an adapter through the microservice architecture development protocol to access different forms of services; Step S1.2, uniformly manage metadata of adapter access services; Step S1.3: Build a container image through the container to achieve rapid deployment of the cloud-native distributed gateway; Step S2: In a multi-cloud environment, data integration services, message integration services, and business integration services are built on heterogeneous virtualized resource pools based on containers, kata, and kubernetes technologies. The built integration services are automatically registered to the cloud native distributed gateway. The process of building data integration services is as follows: Step S2.1.1, realize unified adaptation of heterogeneous data sources through data persistence engine; Step S2.1.2: Use the data access function to build a logical + physical data resource pool; Step S2.1.3: Use the data subscription function to implement subscription / push management of the data integration service catalog; After building data integration services, data from different sources can be adapted and accessed, and data can be pushed to subscribers through publish / subscribe methods to achieve real-time data flow and data collaboration across departments and networks. The process of building a message integration service is as follows: Step S2.2.1, adapting to the underlying infrastructure resources through the adapter, and adapting to the virtualization / container resource pool through the adapter, to achieve rapid construction of a multi-tenant message queue based on virtualization; Step S2.2.2, using the application as a tenant and serving as a message service instance of an open message integration service; Step S2.2.3, application development realizes the application of data / services through subscription / push mode; Through the built message integration service, ① asynchronous call services are provided to the access party. At this time, the call request is transmitted in the form of a message. The cloud native distributed gateway listens to the message and processes the task. After the processing is completed, a notification is sent to the message middleware. ② The computing tasks are decoupled to realize the message-based streaming computing service; The process of building a business integration service is as follows: Step S2.3.1, realize the registration access management of different services by adapting different protocols of http / tcp / socket; Step S2.3.2: After the service registration is approved, the service catalog of the distributed gateway is automatically published by calling the API of the distributed gateway; Step S2.3.3: The developer subscribes to and applies for the required services through the distributed gateway; Step S3: Create a designer based on the web interface. The designer provides a visual panel to create integrated orchestration tasks and supports visual orchestration of data, service, and application-related components. The created designer provides components of basic processes, data conversion, script execution, message queues, and process events to support cross-network and cross-application integrated conversion, support timed and real-time integration modes, support encapsulating existing services and hybrid integrated orchestration results into Restful APIs for external use, and realize unified authorization management by combining data authentication and user authorization modes. Step S4, the user uses various integration capabilities through the blockchain, and calls the integrated services registered in the distributed gateway through the service API provided by the designer, and finally realizes the access to the metadata in the distributed gateway; in this process: the access party system is mapped to a user within the organization. At this time, the access party system can deploy its own chaincode according to its own needs, provide SDK for calling the integrated service, and the access party system can also apply to create a channel, join a channel, and create a user. After approval, the channel is created, joined or created, and the user can download the CA certificate and access the blockchain; the blockchain stores all API authorization, data authorization process information, and result information.
2. According to a blockchain-based cloud native hybrid integration method according to claim 1, it is characterized in that: All APIs provided by the built cloud-native distributed gateway support synchronous and asynchronous calls. When the access system selects the asynchronous call method according to actual business needs, the asynchronous call gateway will call back the result through the callback address provided by the user after the API is executed. The built cloud-native distributed gateway records all API call logs and provides an API metering system. The logs include information such as the caller, API Code, input parameters, output parameters, response time, success and failure flags, and provide API collaborative statistical analysis functions.
3. According to a blockchain-based cloud native hybrid integration method according to claim 1, it is characterized in that: The API of the business integration service runs on the access system. The distributed gateway routes to the subsystem through the API Code and performs request / response conversion. At the same time, since the API will eventually be called on the access system, the distributed gateway needs to perform load balancing based on the configuration of the access system. For query APIs, the results are cached according to the API type and frequency to ensure efficient API calls.
