CN116980480B - Method and system for processing fusing information based on micro-service network model - Google Patents
Method and system for processing fusing information based on micro-service network model Download PDFInfo
- Publication number
- CN116980480B CN116980480B CN202311237139.3A CN202311237139A CN116980480B CN 116980480 B CN116980480 B CN 116980480B CN 202311237139 A CN202311237139 A CN 202311237139A CN 116980480 B CN116980480 B CN 116980480B
- Authority
- CN
- China
- Prior art keywords
- service
- request
- fusing
- information
- fused
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 37
- 238000012545 processing Methods 0.000 title claims abstract description 17
- 238000001914 filtration Methods 0.000 claims abstract description 8
- 238000011144 upstream manufacturing Methods 0.000 claims abstract description 7
- 230000014509 gene expression Effects 0.000 claims description 4
- 230000010365 information processing Effects 0.000 claims description 3
- 238000012423 maintenance Methods 0.000 abstract description 8
- 238000012805 post-processing Methods 0.000 abstract 1
- 230000009471 action Effects 0.000 description 6
- 239000000306 component Substances 0.000 description 6
- 238000010586 diagram Methods 0.000 description 5
- 230000004048 modification Effects 0.000 description 5
- 238000012986 modification Methods 0.000 description 5
- 230000008569 process Effects 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 4
- 238000007664 blowing Methods 0.000 description 3
- 238000012544 monitoring process Methods 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 239000008358 core component Substances 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000003672 processing method Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/562—Brokering proxy services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/566—Grouping or aggregating service requests, e.g. for unified processing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/59—Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The application relates to the field of network architecture, and discloses a method and a system for processing fusing information based on a micro-service network model, which solve the problem that network fusing post-processing cannot be customized, so that operation and maintenance personnel shorten the problem positioning time and improve the efficiency. The method comprises the following steps: the downstream host sends out a request for calling the service; the information package filtering table forwards a request for calling the service to a service agent program component, and the service agent program component judges whether the service is fused or not; if the service is not fused, distributing the flow of the access service to an upstream host; if the service is fused, the traffic accessing the fused service is uniformly routed to a designated custom service, and the custom service is configured to return fused information and error information by acquiring the original request information of the request.
Description
Technical Field
The application relates to the field of network architecture, in particular to a method and a system for processing fusing information based on a micro-service network model.
Background
This section is intended to provide a background or context for embodiments of the present application that are recited in the claims. The description herein is not admitted to be prior art by inclusion in this section.
The combination of K8s (kubernetes) +ission has become a de facto standard for current cloud native and microservice building. The K8s is a portable and expandable open source platform for managing containerized workload and service, is oriented to infrastructure, tightly integrates resources such as calculation, network and storage, provides an optimal running environment for the container, provides a packaged and easy-to-use workload and service arrangement interface for the application, and provides a resource specification, elasticity, running parameters, scheduling and other configuration management interfaces required by operation and maintenance, and is a new generation of cloud primary infrastructure platform. The Service of K8s obtains information of Service (Service) and Endpoint (Endpoint) from Kube-api (one of core components of K8 s) based on Kube-proxy (one of core components of K8 s) of each node, and forwards a request for Service to the corresponding Endpoint through load balancing. But K8s only provides 4-layer load balancing capability. For gateways accessed from outside, K8s uses access points (ingres) exposed to the outside by the service in the cluster to receive external traffic, but similarly, only 4-layer forwarding capability is provided, and 7-layer routing capability is not provided, which greatly limits the use of ingres.
The current micro-service fusing mechanism based on the atio is not perfect: first, fuses cannot be uniformly set, and can be set one by one according to micro services, so that if the micro services are numerous, the setting is quite troublesome. Secondly, service fusing can only use the default returned error of the atio, and the service fusing can not be customized, so that a user can not accurately know the fused position and specific error information when fusing.
In the prior art, if fusing occurs, only 50x errors are returned, the fusing of which link in the service chain is not prompted, and the return errors are not customizable, so that the efficiency of operation and maintenance personnel in processing network fusing is low.
Disclosure of Invention
The invention aims to provide a fusing information processing method and system based on a micro-service network model, which can customize after network service is fused, so that operation and maintenance personnel can shorten the problem positioning time and improve the efficiency.
The application discloses a method for processing fusing information based on a microservice network model, which comprises the following steps:
the downstream host sends out a request for calling the service;
the information packet filtering table forwards the request for calling the service to a service agent program component, and the service agent program component judges whether the service is fused or not;
if the service is not fused, distributing the flow of the access service to an upstream host;
if the service is fused, the traffic accessing the fused service is uniformly routed to a specified custom service, and the custom service is configured to return fused information and error information by acquiring original request information of the request.
In a preferred embodiment, before determining whether the network is blown, the method further comprises:
a common fuse is created in the namespace where the services are located, the common fuse being configured to fuse all services within the same namespace.
In a preferred embodiment, the naming names of the common fuses satisfy the matching of regular expressions.
In a preferred embodiment, the packet filter table forwarding the request to invoke a service to a service broker component further comprises:
the information packet filtering table forwards the request for calling the service to a virtual listener in the service agent program component;
the virtual listener forwards the request for calling the service to the corresponding listener according to the original target address and the port;
and the corresponding listener distributes the traffic according to the port rule.
In a preferred embodiment, the uniformly routing the traffic of the access fuse service to the specified custom service further includes:
the flow of the access fusing service enters load balancing and is forwarded to a service providing cluster corresponding to a default service through a service gateway;
the service providing cluster directs traffic of the access fuse service to the custom service.
In a preferred embodiment, after the service providing cluster directs the traffic of the access fusing service to the custom service, the method further includes:
the user-defined service finds a target service according to the configuration and matches a corresponding target service rule;
and the target service carries out flow hijacking on the flow accessing the fusing service through the side car container and forwards the flow to the corresponding container.
In a preferred embodiment, the fusing information includes a fused service name, an interface name, and a parameter set.
The application also discloses a processing system of fusing information based on the micro-service network model, comprising:
a packet filter table configured to forward a request for invoking a service from a downstream host;
a service agent component configured to accept the request and determine whether a service is blown, and if the service is blown, distribute traffic of the service to an upstream host; the method comprises the steps of,
and the custom service container is configured to receive the traffic of the service when the service is fused, and return fused information and error information by acquiring the original request information of the request.
In a preferred embodiment, a common fuse is also included, configured to blow all services within the same namespace.
The application also discloses a computer readable storage medium having stored therein computer executable instructions which when executed by a processor implement steps in a method as described hereinbefore.
In the method, the step of forwarding to the cluster corresponding to the service is added in the link of directly returning the error by service fusing, and the cluster guides the flow to a customizable container group and returns the specific information of the error, so that the customization of the error information can be realized, and the operation and maintenance personnel can locate and solve the problem more quickly, thereby improving the usability of the system;
further, instead of setting a fuse corresponding to each service in the past, by setting a common fuse under the same naming space, fuses with the same configuration can use one configuration without each configuration, so that the burden of configuration and operation and maintenance can be reduced, and unified configuration modification is facilitated.
The technical features disclosed in the above summary, the technical features disclosed in the following embodiments and examples, and the technical features disclosed in the drawings may be freely combined with each other to constitute various novel technical solutions (which should be regarded as having been described in the present specification) unless such a combination of technical features is technically impossible. For example, in one example, feature a+b+c is disclosed, in another example, feature a+b+d+e is disclosed, and features C and D are equivalent technical means that perform the same function, technically only by alternative use, and may not be adopted simultaneously, feature E may be technically combined with feature C, and then the solution of a+b+c+d should not be considered as already described because of technical impossibility, and the solution of a+b+c+e should be considered as already described.
Drawings
FIG. 1 is a schematic flow diagram according to one embodiment of the present application;
FIG. 2 is a schematic diagram of a fuse configuration according to one embodiment of the present application;
FIG. 3 is a flow diagram according to one embodiment of the present application;
FIG. 4 is a flow diagram according to one embodiment of the present application;
fig. 5 is a schematic architecture diagram according to one embodiment of the present application.
Detailed Description
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present application. However, it will be understood by those skilled in the art that the claimed invention may be practiced without these specific details and with various changes and modifications from the embodiments that follow.
Description of the partial concepts:
fusing: service fusing is also known as service isolation or overload protection. In micro-service application, services have certain dependency relationship to form a certain dependency chain, if a certain target service is invoked slowly or has a large amount of overtime, the services are not available, other dependent services are indirectly caused to be unavailable, the whole dependency chain is probably blocked most seriously, and finally, a business system is crashed (also called avalanche effect). At this time, the fusing is performed on the call of the service, and the target service is not continuously called for the subsequent request, but is directly returned, so that the resource can be quickly released. After the target service condition is improved, the call can be restored.
A fuse: the device is a switching device, when a certain service unit fails, an alternative response (FallBack) which accords with expectations and can be processed is returned to a calling party through fault monitoring (similar to fuse blowing) of a circuit breaker, and the exception which cannot be processed by the calling party is not waited for a long time or thrown, so that the thread of the service calling party is ensured not to be occupied for a long time and unnecessarily, and the spread of faults in a distributed system and even avalanche are avoided.
Pod: pod is the smallest unit of K8s, and a container (container) is contained in pod, which is a collection of a group of containers. The pod corresponds to a logical host, and each pod has its own ip address. The containers within the pod share the same ip and port by default, and the file system of each container is completely isolated from the other containers.
Cluster: the cluster is a newer technology, through which relatively high gains in terms of performance, reliability and flexibility can be obtained at a lower cost, and task scheduling is the core technology in a clustered system. A cluster is a group of mutually independent computers interconnected by a high-speed network, which form a group and are managed in a single system mode. When a client interacts with a cluster, the cluster appears as an independent server. Cluster configuration is used to increase availability and scalability.
iptables: is an IP packet filtering table integrated with the latest version 3.5 Linux kernel. If the Linux system is connected to the internet or a LAN, a server or a proxy server connecting the LAN and the internet, the system is advantageous for better control of IP packet filtering and firewall configuration on the Linux system.
Istio: is a micro-service management, protection and monitoring framework. The use of the Istio allows a very simple creation of a service network with load balancing, inter-service authentication, monitoring etc. functions without any modification of the code of the service.
For the purpose of making the objects, technical solutions and advantages of the present application more apparent, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.
The first embodiment of the present application relates to a method for processing fusing information based on a micro-service network model, the flow of which is shown in fig. 1, and the method comprises the following steps:
in step 101, a downstream host issues a request to invoke a service.
In step 102, the packet filter table forwards the request to invoke the service to the service broker component, which determines if the service is blown.
If the service is not blown, the traffic to access the service is distributed to the upstream host in step 103.
In step 104, if the service is blown, the traffic accessing the blown service is uniformly routed to a designated custom service, and the custom service is configured to return the blown information and the error information by acquiring the original request information of the request.
Optionally, before determining whether the network is blown, the method may further include: a common fuse is created in the namespace in which the services reside, the common fuse being configured to fuse services within the same namespace. Alternatively, as shown in fig. 2, the optimized fuses may be configured in namespaces where services are located, the fuses may be isolated from namespaces like pod and service, and fuses under one namespace may not affect or be applicable to services of other namespaces. So that a common fuse can be established in a namespace.
Alternatively, the naming names of the common fuses may satisfy the matching of regular expressions. For example, abc may represent services beginning with abc, and all services under that namespace. Therefore, the fuses with the same configuration can use one configuration without each configuration, thus reducing the burden of configuration and operation and maintenance and being beneficial to uniformly modifying the configuration.
Optionally, as shown in fig. 3, the following steps may be further included in step 102:
in step 1021, the packet filter table forwards the request to invoke the service to the virtual listener in the service agent component.
In step 1022, the virtual listener forwards the request for invoking the service to the corresponding listener according to the original target address and port;
in step 1023, the corresponding listener distributes the traffic according to the port rule.
Optionally, uniformly routing the traffic accessing the fusing service to the specified custom service may further include: the traffic of the access fusing service enters load balancing and is forwarded to a service providing cluster corresponding to the default service through a service gateway, and the service providing cluster guides the traffic of the access fusing service to the custom service.
Optionally, after the service providing cluster directs the traffic of accessing the fusing service to the custom service, the method may further include: the user-defined service finds out a target service according to the configuration and matches with a corresponding target service rule, and the target service carries out flow hijacking on the flow accessing the fusing service through the side car container and forwards the flow to the corresponding container.
Alternatively, the fusing information may include a fused service name, an interface name, and a parameter set.
In order to better understand the technical solutions of the present application, the following description is given with reference to a specific example, in which details are listed mainly for the sake of understanding, and are not meant to limit the scope of protection of the present application.
As shown in fig. 4, service srvA initiates a call to service srvB. The request is intercepted by the packet filter table (iptables) of the container group (pod), which may be addressed to 192.168.200.3, serving srvA, and forwarded to port 15001. The Virtual Listener (Virtual Listener) of the service agent component (edge container envoy) listens on the 15001 port, receiving the request. The request is forwarded by the virtual listener to the listener (listener) 0.0.0.0_9080 according to the original target IP (wild) and port (9080).
If no blowing occurs, the request is routed according to the http_conn_filter and the circumflex_filter configuration of 0.0.0.0_9080 Listener: 9080, for distribution. If a blow occurs, the request is routed: 8080 forwards. And (3) routing: 8080 forwards to the Cluster (Cluster) corresponding to the default service, i.e. the Cluster Outbound Cluster is sent out of the Cluster Outbound 8080 message, thus directing traffic to the DefaultSrv service, the address may be 192.168.200.10. The DefaultSrv service is a container group pod that is dedicated to the execution of the fusing process, includes customizable containers, and can customize the return information. For example, the service may log the error by retrieving the original request information and returning the blown service name, interface name and parameter set, or send the error to the operation and maintenance personnel through a messaging service. In this way, the service personnel can locate and solve the problem more quickly, thereby improving the usability of the system.
In the configuration of "9080" route where no blowing occurs, the cluster corresponding to the request with host (host) name info 9080 is outbound 9080 info default. The outbound 9080 info. Default. Svc. Cluster. Local cluster is a dynamic resource, and the endpoint is 192.168.200.4:9080 obtained through the query of the terminal discovery service (EDS). The request is forwarded to 192.168.200.4, the container where the info service resides. Traffic is intercepted by the packet filter table rules and forwarded to the 15001 port. The Envoy's virtual listener listens on port 15001, receiving the request. The request is forwarded by the virtual listener to the 192.168.200.4_9080 listener based on the request's original destination address IP (192.168.200.4) and port 9080. According to the http_connection_manager_filter configuration of the 192.168.200.4_9080 listener, the Cluster corresponding to the request is an internal receiving Cluster. The request is forwarded to 127.0.0.1:9080. Traffic eventually reaches service srvB.
A second embodiment of the present application relates to a system for processing fusing information based on a micro-service network model, the system comprising:
a packet filter table configured to forward a request for invoking a service from a downstream host;
a service agent component configured to accept the request and determine whether the service is blown, and if so, distribute traffic for the service to an upstream host; the method comprises the steps of,
the custom service container is configured to receive the traffic of the service when the service is fused, and return fusing information and error information by acquiring the original request information of the request.
Optionally, the system may further include one or more common fuses configured to blow services within the same namespace.
The first embodiment is a method embodiment corresponding to the present embodiment, and the technical details in the first embodiment can be applied to the present embodiment, and the technical details in the present embodiment can also be applied to the first embodiment.
In order to better understand the technical solutions of the present application, the following description is given with reference to a specific example, in which details are listed mainly for the sake of understanding, and are not meant to limit the scope of protection of the present application.
The application integrally follows the container network architecture of k8s+ission, as shown in fig. 5, after the traffic is balanced from the load, the traffic is routed to a designated virtual service through an ission service gateway, the virtual service finds the service according to the configuration (if a target service (destination service) is set, the corresponding destination service rule is matched, and the fuse is configured in destination service), and the service is hijacked by the pod inner side vehicle (sidecar) traffic and forwarded to the corresponding container.
Accordingly, embodiments of the present application also provide a computer-readable storage medium having stored therein computer-executable instructions which, when executed by a processor, implement the method embodiments of the present application. Computer-readable storage media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer 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 technology, compact disc read only memory (CD-ROM), digital Versatile Disks (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium which can be used to store information that can be accessed by a computing device. Computer-readable storage media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.
It is noted that in this application relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. In the present application, if it is mentioned that a certain action is performed according to a certain element, it means that the action is performed at least according to the element, and two cases are included: the act is performed solely on the basis of the element and is performed on the basis of the element and other elements. Multiple, etc. expressions include 2, 2 times, 2, and 2 or more, 2 or more times, 2 or more.
The sequence numbers used in describing the steps of the method do not themselves constitute any limitation on the order of the steps. For example, the step with the larger sequence number is not necessarily performed after the step with the smaller sequence number, but the step with the larger sequence number may be performed first and then the step with the smaller sequence number may be performed in parallel, as long as the order of execution is reasonable for those skilled in the art. As another example, steps having consecutive numbered numbers (e.g., step 101, step 102, step 103, etc.) are not limiting as other steps may be performed therebetween, e.g., there may be other steps between step 101 and step 102.
This specification includes combinations of the various embodiments described herein. Reference to an embodiment alone (e.g., "one embodiment" or "some embodiments" or "preferred embodiments"); however, unless indicated as mutually exclusive or as would be apparent to one of skill in the art, the embodiments are not mutually exclusive. It should be noted that the term "or" is used in this specification in a non-exclusive sense unless the context clearly indicates otherwise or requires otherwise.
All documents mentioned in the present specification are considered to be included in the disclosure of the present application as a whole, so that they may be regarded as a basis for modification if necessary. Furthermore, it should be understood that the foregoing description is only of the preferred embodiments of the present invention and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, improvement, or the like, which is within the spirit and principles of one or more embodiments of the present disclosure, is intended to be included within the scope of one or more embodiments of the present disclosure.
In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
Claims (10)
1. The method for processing the fusing information based on the micro-service network model is characterized by comprising the following steps of:
the downstream host sends out a request for calling the service;
the information packet filtering table forwards the request for calling the service to a service agent program component, and the service agent program component judges whether the service is fused or not;
if the service is not fused, distributing the flow of the access service to an upstream host;
if the service is fused, the traffic accessing the fused service is uniformly routed to a specified custom service, and the custom service is configured to return fused information and error information by acquiring original request information of the request.
2. The method for processing fusing information based on a micro service network model as claimed in claim 1, further comprising, before determining whether fusing of the network occurs:
a common fuse is created in the namespace where the services are located, the common fuse being configured to fuse all services within the same namespace.
3. The method for processing fusing information based on the micro-service network model of claim 2, wherein the naming names of the common fuses satisfy matching of regular expressions.
4. The method for processing fusing information based on a micro-service network model of claim 1, wherein the packet filtering table forwarding the request to invoke a service to a service broker component further comprises:
the information packet filtering table forwards the request for calling the service to a virtual listener in the service agent program component;
the virtual listener forwards the request for calling the service to the corresponding listener according to the original target address and the port;
and the corresponding listener distributes the traffic according to the port rule.
5. The method for processing fusing information based on a micro service network model as claimed in claim 1, wherein uniformly routing the traffic accessing the fusing service to the designated custom service further comprises:
the flow of the access fusing service enters load balancing and is forwarded to a service providing cluster corresponding to a default service through a service gateway;
the service providing cluster directs traffic of the access fuse service to the custom service.
6. The method for processing fusing information based on the micro-service network model as recited in claim 5, further comprising, after the service providing cluster directs the traffic of the access fusing service to the custom service:
the user-defined service finds a target service according to the configuration and matches a corresponding target service rule;
and the target service carries out flow hijacking on the flow accessing the fusing service through the side car container and forwards the flow to the corresponding container.
7. The method for processing fusing information based on a micro service network model as claimed in claim 1, wherein the fusing information includes a fused service name, an interface name, and a parameter set.
8. A micro-service network model-based fusing information processing system, comprising:
a packet filter table configured to forward a request for invoking a service from a downstream host;
a service agent component configured to accept the request and determine whether a service is blown, and if the service is blown, distribute traffic of the service to an upstream host; the method comprises the steps of,
and the custom service container is configured to receive the traffic of the service when the service is fused, and return fused information and error information by acquiring the original request information of the request.
9. The micro-service network model based fusing information processing system of claim 8, further comprising a common fuse configured to fuse all services within a same namespace.
10. A computer readable storage medium having stored therein computer executable instructions which when executed by a processor implement the steps of the method of any of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311237139.3A CN116980480B (en) | 2023-09-25 | 2023-09-25 | Method and system for processing fusing information based on micro-service network model |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311237139.3A CN116980480B (en) | 2023-09-25 | 2023-09-25 | Method and system for processing fusing information based on micro-service network model |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116980480A CN116980480A (en) | 2023-10-31 |
| CN116980480B true CN116980480B (en) | 2024-02-27 |
Family
ID=88480006
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311237139.3A Active CN116980480B (en) | 2023-09-25 | 2023-09-25 | Method and system for processing fusing information based on micro-service network model |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116980480B (en) |
Citations (18)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108600005A (en) * | 2018-04-23 | 2018-09-28 | 国云科技股份有限公司 | A method of defence micro services avalanche effect |
| CN108737548A (en) * | 2018-05-24 | 2018-11-02 | 南京邮电大学 | Distributed WEB micro services container aggregated structure system and its implementation |
| CN110149364A (en) * | 2019-04-15 | 2019-08-20 | 厦门市美亚柏科信息股份有限公司 | Method, apparatus, the storage medium of micro services are provided based on data service platform |
| CN110535902A (en) * | 2019-07-16 | 2019-12-03 | 平安普惠企业管理有限公司 | The processing method and electronic device of monitoring intelligent are realized based on micro services |
| CN111782259A (en) * | 2020-06-24 | 2020-10-16 | 北京计算机技术及应用研究所 | Micro-service management method based on reverse proxy |
| CN111787073A (en) * | 2020-06-18 | 2020-10-16 | 多加网络科技(北京)有限公司 | Current-limiting fusing platform and method for unified service |
| CN112054998A (en) * | 2020-08-10 | 2020-12-08 | 中粮招商局(深圳)粮食电子交易中心有限公司 | Proxy service method, device, equipment and computer readable storage medium |
| CN112187511A (en) * | 2020-08-28 | 2021-01-05 | 苏州浪潮智能科技有限公司 | Method, system, equipment and medium for positioning micro-service fusing abnormity |
| CN112306701A (en) * | 2019-07-25 | 2021-02-02 | 中移动信息技术有限公司 | Service fusing method, device, equipment and storage medium |
| CN112764913A (en) * | 2021-04-09 | 2021-05-07 | 腾讯科技（深圳）有限公司 | Service fusing method and device, storage medium and electronic equipment |
| CN112788031A (en) * | 2021-01-11 | 2021-05-11 | 百果园技术(新加坡)有限公司 | Envoy architecture-based micro-service interface authentication system, method and device |
| CN112988434A (en) * | 2019-12-13 | 2021-06-18 | 中国银联股份有限公司 | Service fuse, service fusing method and computer-readable storage medium |
| CN113609490A (en) * | 2021-07-28 | 2021-11-05 | 国家电网有限公司客户服务中心 | Data API combined type safety control mechanism suitable for multi-element scenes |
| CN114157551A (en) * | 2021-11-29 | 2022-03-08 | 中国平安财产保险股份有限公司 | Fusing identification method, device, equipment and storage medium suitable for micro-service |
| US11457080B1 (en) * | 2018-11-23 | 2022-09-27 | Amazon Technologies, Inc. | Service mesh management |
| CN116069264A (en) * | 2023-03-13 | 2023-05-05 | 南京飓风引擎信息技术有限公司 | Application program data information storage control system |
| CN116302346A (en) * | 2023-03-10 | 2023-06-23 | 天翼云科技有限公司 | Fault processing method and device for side car container |
| CN116346587A (en) * | 2023-04-14 | 2023-06-27 | 上海浦东发展银行股份有限公司 | Service grid disaster recovery method, equipment and medium |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11601358B2 (en) * | 2020-12-17 | 2023-03-07 | HashiCorp | Cross datacenter communication using a mesh gateway |
| CN112965848A (en) * | 2021-03-05 | 2021-06-15 | 北京百度网讯科技有限公司 | Fusing degradation method, device, equipment and medium for micro service |
-
2023
- 2023-09-25 CN CN202311237139.3A patent/CN116980480B/en active Active
Patent Citations (18)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108600005A (en) * | 2018-04-23 | 2018-09-28 | 国云科技股份有限公司 | A method of defence micro services avalanche effect |
| CN108737548A (en) * | 2018-05-24 | 2018-11-02 | 南京邮电大学 | Distributed WEB micro services container aggregated structure system and its implementation |
| US11457080B1 (en) * | 2018-11-23 | 2022-09-27 | Amazon Technologies, Inc. | Service mesh management |
| CN110149364A (en) * | 2019-04-15 | 2019-08-20 | 厦门市美亚柏科信息股份有限公司 | Method, apparatus, the storage medium of micro services are provided based on data service platform |
| CN110535902A (en) * | 2019-07-16 | 2019-12-03 | 平安普惠企业管理有限公司 | The processing method and electronic device of monitoring intelligent are realized based on micro services |
| CN112306701A (en) * | 2019-07-25 | 2021-02-02 | 中移动信息技术有限公司 | Service fusing method, device, equipment and storage medium |
| CN112988434A (en) * | 2019-12-13 | 2021-06-18 | 中国银联股份有限公司 | Service fuse, service fusing method and computer-readable storage medium |
| CN111787073A (en) * | 2020-06-18 | 2020-10-16 | 多加网络科技(北京)有限公司 | Current-limiting fusing platform and method for unified service |
| CN111782259A (en) * | 2020-06-24 | 2020-10-16 | 北京计算机技术及应用研究所 | Micro-service management method based on reverse proxy |
| CN112054998A (en) * | 2020-08-10 | 2020-12-08 | 中粮招商局(深圳)粮食电子交易中心有限公司 | Proxy service method, device, equipment and computer readable storage medium |
| CN112187511A (en) * | 2020-08-28 | 2021-01-05 | 苏州浪潮智能科技有限公司 | Method, system, equipment and medium for positioning micro-service fusing abnormity |
| CN112788031A (en) * | 2021-01-11 | 2021-05-11 | 百果园技术(新加坡)有限公司 | Envoy architecture-based micro-service interface authentication system, method and device |
| CN112764913A (en) * | 2021-04-09 | 2021-05-07 | 腾讯科技（深圳）有限公司 | Service fusing method and device, storage medium and electronic equipment |
| CN113609490A (en) * | 2021-07-28 | 2021-11-05 | 国家电网有限公司客户服务中心 | Data API combined type safety control mechanism suitable for multi-element scenes |
| CN114157551A (en) * | 2021-11-29 | 2022-03-08 | 中国平安财产保险股份有限公司 | Fusing identification method, device, equipment and storage medium suitable for micro-service |
| CN116302346A (en) * | 2023-03-10 | 2023-06-23 | 天翼云科技有限公司 | Fault processing method and device for side car container |
| CN116069264A (en) * | 2023-03-13 | 2023-05-05 | 南京飓风引擎信息技术有限公司 | Application program data information storage control system |
| CN116346587A (en) * | 2023-04-14 | 2023-06-27 | 上海浦东发展银行股份有限公司 | Service grid disaster recovery method, equipment and medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116980480A (en) | 2023-10-31 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112868206B (en) | Method, system and computer readable medium for providing service broker functionality | |
| WO2020147466A1 (en) | Method for invoking server and proxy server | |
| US7257817B2 (en) | Virtual network with adaptive dispatcher | |
| US7899047B2 (en) | Virtual network with adaptive dispatcher | |
| US20230224756A1 (en) | Binding indications for load balancing and redundancy for communications between network function instances in a 5g core network | |
| CN113572838B (en) | Network access method, device, equipment and medium based on Kubernetes | |
| EP3413511B1 (en) | Vnfm determining method and network function virtualization orchestrator | |
| US20210274328A1 (en) | Internet of vehicles message notification method and apparatus | |
| CN113301116A (en) | Cross-network communication method, device, system and equipment for microservice application | |
| US9148388B2 (en) | Methods, systems, and computer readable media for performing enhanced service routing | |
| CN113938520A (en) | Service registration method, device and storage medium | |
| EP4209905A1 (en) | Service mesh system employing microservice, and service governance method | |
| CN113542437B (en) | Network system, network proxy method and device | |
| CN112104640B (en) | Data processing method, device and equipment of gateway and readable storage medium | |
| CN116633775B (en) | Container communication method and system of multi-container network interface | |
| CN113220484A (en) | Micro-service calling method and device, electronic equipment and storage medium | |
| CN113301079B (en) | Data acquisition method, system, computing device and storage medium | |
| CN113608865A (en) | Flow control method, device, system, electronic equipment and storage medium | |
| CN116980480B (en) | Method and system for processing fusing information based on micro-service network model | |
| US20220141080A1 (en) | Availability-enhancing gateways for network traffic in virtualized computing environments | |
| CN113839876A (en) | Transmission path optimization method and equipment for internal network | |
| CN117950828A (en) | Application calling method and device, electronic equipment and computer readable storage medium | |
| CN117879955A (en) | Micro-service communication method, micro-service communication device, computer equipment and storage medium | |
| JP2024517909A (en) | Method and apparatus for deploying container services - Patents.com | |
| CN116319787A (en) | Communication method and forwarding device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |