CN113141405B - Service access method, middleware system, electronic device, and storage medium - Google Patents
Service access method, middleware system, electronic device, and storage medium Download PDFInfo
- Publication number
- CN113141405B CN113141405B CN202110440844.8A CN202110440844A CN113141405B CN 113141405 B CN113141405 B CN 113141405B CN 202110440844 A CN202110440844 A CN 202110440844A CN 113141405 B CN113141405 B CN 113141405B
- Authority
- CN
- China
- Prior art keywords
- service
- deployed
- address information
- request
- cluster
- 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
Images
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/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/63—Routing a service request depending on the request content or context
Abstract
The invention discloses a service access method, a middleware system, electronic equipment and a storage medium, wherein the method is applied to the middleware system and comprises the following steps: creating a first component inside the middleware system based on the address information of the deployed service and the internal address of the deployed service on the cluster; receiving a request for a first service of the deployed services; inquiring an internal address corresponding to the request in the first assembly according to the address information of the request; modifying the address information of the request into an internal address corresponding to the request; and sending the request to the corresponding deployed service based on the address information modified by the request. In the embodiment of the invention, the internal address of the request is determined by the components in the middleware system, so that the middleware system is prevented from being coupled with an external module, and the success rate of service access is improved.
Description
Technical Field
The present invention relates to the field of network technologies, and in particular, to a service access method, a middleware system, an electronic device, and a storage medium.
Background
The container technology is a virtualization technology which saves more computing resources than a virtual machine technology and is more flexible, with the development of the container technology, a plurality of container arrangement standards appear, and Kubernets are a standard in the field of container arrangement in a separate way, wherein Kubernets are called K8S for short. Knative is a common architecture scheme applied to the K8S standard, and based on the advantages of K8S, more and more enterprises use middleware provided by Knative technology to deploy services to a K8S cluster.
By using the service deployed on the cluster by the middleware, the middleware can generate an internal address of the service on the cluster, and a user can access the service deployed on the cluster by sending a request. In one embodiment, a user first sends a request to a gateway outside the cluster, and the gateway determines an internal address of the request and sends the request to a service to which the internal address points.
However, in the above embodiment, the gateway and the middleware may be understood as 2 different modules, and if the external gateway configures the internal address generated by the middleware, a coupling phenomenon may easily occur between the gateway and the middleware, which may cause a user access failure, which may result in a low success rate of service access.
Disclosure of Invention
The embodiment of the invention aims to provide a service access method, a middleware system, electronic equipment and a storage medium, and solves the technical problem of low success rate of service access. The specific technical scheme is as follows:
in a first aspect of the embodiments of the present invention, a service access method is first provided, which is applied to a middleware system, and includes:
creating a first component inside the middleware system based on address information of a deployed service and an internal address of the deployed service on a cluster, wherein the first component stores mapping between the address information and the internal address;
receiving a request for a first service of the deployed services;
inquiring an internal address corresponding to the request in the first component according to the address information of the request, wherein the address information of the request is the same as the address information of the first service;
modifying the address information of the request into an internal address corresponding to the request;
and sending the request to the corresponding deployed service based on the address information modified by the request.
In a second aspect of the embodiments of the present invention, there is also provided a middleware system, including:
a controller; the controller is used for creating a first component based on address information of deployed services and internal addresses of the deployed services on a cluster, and the first component stores mapping between the address information and the internal addresses;
the first component to receive a request for a first service of the deployed services; inquiring an internal address corresponding to the request in the first component according to the address information of the request, wherein the address information of the request is the same as the address information of the corresponding first service; modifying the address information of the request into an internal address corresponding to the request; and sending the request to the corresponding deployed service based on the address information modified by the request.
In a third aspect of the embodiments of the present invention, there is also provided a computer-readable storage medium, having stored therein instructions, which, when run on a computer, cause the computer to execute the service access method according to any of the above-mentioned embodiments.
In a fourth aspect of the present invention, there is also provided a computer program product containing instructions which, when run on a computer, cause the computer to perform the service access method of any one of the above embodiments.
In the embodiment of the invention, a first component is created inside the middleware system based on the address information and the internal address of the deployed service, wherein the first component stores the mapping between the address information and the internal address. Under the condition that a request of a user for a first service in deployed services is received, the internal address of the request can be determined through the first component, so that the address information of the request is modified, the request is sent to the corresponding deployed service, and the access of the service is realized. In this embodiment, the internal address of the request is determined by the component inside the middleware system, and the middleware system is prevented from being coupled with an external module, so that the success rate of service access is improved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the prior art descriptions will be briefly described below.
FIG. 1 is a flow chart of a method of service access in an embodiment of the present invention;
fig. 2 is a schematic view of an application scenario of a service access method in an embodiment of the present invention;
FIG. 3 is a schematic structural diagram of a middleware system according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of an electronic device in an embodiment of the invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be described below with reference to the drawings in the embodiments of the present invention.
The service access method provided by the embodiment of the invention is applied to a container cluster management platform, and the container cluster management platform can be K8S.
Currently, most of the services are deployed to the K8S cluster by using middleware provided by a Knative technology. After the service is deployed to the cluster, the middleware generates an internal address of the service on the cluster, and it should be understood that the location of the service on the cluster can be determined according to the internal address.
There may be a case where a user sends a request corresponding to the service to access the service deployed on the cluster, where each request corresponds to address information. The gateway arranged outside the cluster is used for determining an internal address corresponding to the request and then sending the request to the service pointed by the internal address, wherein the external gateway can be a Nginx gateway which is a high-performance reverse proxy server.
However, in the above case, it is necessary to configure a mapping between an internal address and address information in the external gateway, and the internal address is generated by the middleware, which easily causes a coupling phenomenon between the gateway and the middleware, resulting in a user access failure, which results in a low success rate of service access.
Based on the technical problems, the invention provides the following technical concepts:
and setting a component in the middleware, sending a request sent by a user to the component, determining an internal address corresponding to the request by the component, and sending the request to a service pointed by the internal address by the component. Therefore, the request can be sent to the corresponding service without setting an external gateway, and the coupling between the external gateway and the middleware is avoided, so that the user access failure is avoided, and the success rate of service access is low.
Referring to fig. 1, fig. 1 is a flowchart illustrating a service access method according to an embodiment of the present invention. The service access method provided by the embodiment of the invention comprises the following steps:
s101, based on address information of the deployed service and an internal address of the deployed service on the cluster, a first component is created inside the middleware system.
The middleware system in this embodiment includes a target component and a corresponding controller. The target component is used for determining a service to be deployed, wherein the service to be deployed needs to be migrated to the cluster; the controller is used for migrating the service to be deployed to the cluster. Please refer to the following embodiments for the creation of the target component and the controller corresponding to the target component.
The deployed service may also be understood as a service deployed on each node of the cluster, and the deployed service includes address information and an internal address.
After the service is deployed, the controller generates an internal address corresponding to the service, where the internal address is used to indicate the location of the service in the cluster, as described above.
The address information of the service includes an external address and a path of the service, the path of any service in the deployed services is different, and the external address of any service in the deployed services may be the same or different.
For example, the external addresses of the service a and the service B may be mp-test. Qiyi.com, and it is apparent that the 2 services share one external domain name, and in the case that the external addresses of the 2 services are the same, the 2 services may be distinguished through the paths of the service a and the service B.
The controller is used to create a first component, where the first component may be a Virtual Service (VS) component, or may be another type of component, and is not specifically limited herein, and the first component may be used to control traffic and forward the traffic to different nodes in the cluster, that is, forward the traffic to different services deployed in the cluster. The first component stores mapping between address information and internal addresses of any service in deployed services.
In some embodiments, as described above, since the deployed services may share one external address, the first component may also only store a mapping of the path and the internal address of any one of the deployed services.
In some embodiments, the external addresses of part of the deployed services are the same, and only the path prefixes are different, and for the purpose of reducing the storage space, the first component may also only store the mapping between the path prefix and the internal address of any one of the deployed services.
For example, the external address of service a is the same as the external address of service B, both being mp-test.qiyi.com; the prefix of the service A path is/mp/a, the prefix of the service B path is/mp/B, the internal address of the service A is servicea.test.example.com, and the internal address of the service B is serviceb.test.example.com. In this case, the first component stores a mapping between/mp/a and service.test.example.com, and a mapping between/mp/b and service.test.example.com.
S102, a request for a first service in the deployed services is received.
In this embodiment, after the service is deployed to the cluster, the middleware system receives a request of a user for a service in the deployed services, where a service corresponding to the request may be referred to as a first service, and it should be understood that the first service belongs to the deployed services.
The request comprises address information, and the address information included in the request is the same as the address information of the service corresponding to the request.
The request may be referred to as traffic, and the request may be transmitted to the corresponding service, or the traffic may be routed to the corresponding service.
It should be understood that the middleware system is configured with an internal gateway, and upon receiving the request, the middleware system forwards the request sent by the user to the first component via the internal gateway.
S103, inquiring an internal address corresponding to the request in the first assembly according to the address information of the request.
As described above, the first component stores the mapping between the address information and the internal address of any one of the deployed services, and the first component queries the internal address corresponding to the request.
It should be appreciated that, as described above, in some embodiments, only the mapping relationship between the path prefix and the internal address may be stored in the first component, and in this case, the internal address corresponding to the request may be determined according to the path prefix of the request.
For example, the first component stores a mapping between/mp/a and service.test.example.com, and a mapping between/mp/b and service.test.example.com, and if a path prefix of a request is/mp/a, it may be determined that an internal address corresponding to the request is service.test.example.com.
S104, modifying the address information of the request into an internal address corresponding to the request;
in this embodiment, after querying the internal address corresponding to the request, the first component modifies the address information of the request into the internal address, so as to forward the request to the cluster.
And S105, sending the request to the corresponding deployed service based on the address information modified by the request.
An optional implementation manner is that, based on the address information modified by the request, the first component directly sends the request to the corresponding deployed service on the cluster, so as to implement user access.
Another optional implementation manner is that the first component forwards the request after modifying the address information to the interior gateway, and the interior gateway sends the request to the corresponding deployed service on the cluster, so as to implement user access.
In the embodiment of the invention, a first component is created inside the middleware system based on the address information and the internal address of the deployed service, wherein the first component stores the mapping between the address information and the internal address. Under the condition that a request of a user for a first service in deployed services is received, the internal address of the request can be determined through the first component, so that the address information of the request is modified, the request is sent to the corresponding deployed service, and the access of the service is realized. In this embodiment, the internal address of the request is determined by the component inside the middleware system, so that the middleware system is prevented from being coupled with an external module, and the success rate of service access is improved.
How to deploy services in a cluster is described in detail below:
optionally, before creating the first component inside the middleware system based on the address information of the deployed service and the internal address of the deployed service on the cluster, the method further includes:
acquiring service information and address information of a service to be deployed; deploying the service to be deployed in the cluster according to the service information and the address information of the service to be deployed to obtain deployed service; generating an internal address of the deployed service on the cluster.
Currently, one way to deploy services on a cluster using middleware is: the middleware comprises a resource component and a controller corresponding to the resource component, and a user writes service information of all services to be deployed into the resource component, wherein the service information at least comprises service names and service ports of the services to be deployed. And the resource component sends the service information of the service to be deployed to the cluster, the cluster sends a message to a controller corresponding to the resource component according to the service information, and the controller deploys the service on the cluster after receiving the message sent by the cluster. The message comprises a unique identifier of the resource assembly, and the controller monitors the resource assembly based on the identifier after receiving the message sent by the cluster, so as to analyze the service information stored by the resource assembly and deploy the service on the cluster.
The middleware in this embodiment includes a target component and a controller corresponding to the target component, where the target component multiplexes all resource attribute fields of the resource component, and the target component further has a function that is not included in the resource component to acquire address information of a service to be deployed, that is, the target component in this embodiment has all functions of the resource component and can also acquire address information of the service to be deployed.
That is to say, the user may write the service information and the address information of the service to be deployed into the target component, and the controller deploys the service to be deployed in the cluster according to the service information and the address information of the service to be deployed, so as to obtain the deployed service, and please refer to the subsequent embodiments for the technical solution of how to deploy the service.
After the services are deployed to the cluster, the controller generates internal addresses for all deployed services. It should be noted that, in the process of deploying a service, only an internal address of the service in a cluster is generated, and the address information of the service is not changed, so that the address information of the same service before deployment is the same as the address information of the same service after deployment.
In the following, it is specifically explained how the controller and the target component deploy services on the cluster:
sending the service information and the address information of the service to be deployed to the cluster; receiving a deployment instruction sent by the cluster based on the service information and the address information; and responding to the deployment instruction, and deploying the service to be deployed in the cluster.
The deploying, in response to the deployment instruction, the service to be deployed in the cluster comprises:
in response to the deployment instruction, creating a second component in the middleware system according to the service information of the service to be deployed; deploying the service to be deployed at the cluster using the second component.
In this embodiment, the target component sends the identification information, the service information of the service to be deployed, and the address information to the cluster. Based on a k8s Custom Resource Definition (CRD) mechanism, after receiving service information and address information of a service to be deployed, a cluster detects an internal environment of the cluster, and sends a deployment instruction to a controller if the internal environment operates normally and the service can be deployed, where the deployment instruction is used to instruct a middleware system to deploy the service to be deployed, and the deployment instruction includes identification information of a target component.
The controller analyzes the service information of the service to be deployed stored in the target assembly according to the deployment instruction, creates a second assembly, stores the service information of the service to be deployed, and deploys the service to be deployed by using the second assembly.
The method for analyzing the service information of the service to be deployed stored in the target component at least includes the following two methods:
an optional implementation manner is that the controller monitors the target component based on the identification information and parses the service information stored in the target component.
Another optional implementation manner is that the cluster sends a message to the target component, where the message includes identification information of the target component, so that the controller listens to the target component based on the identification information and parses service information stored by the target component.
To elaborate the relationship between the target component, the controller, the first component, the second component, and the cluster, please refer to FIG. 2.
As shown in fig. 2, the middleware system includes a target component and a controller corresponding to the target component, and the controller creates a first component inside the middleware system according to address information stored in the target component, where the first component stores address information of deployed services and a mapping of an internal address.
The target component sends the identification information, the service information of the service to be deployed, and the address information to the cluster, where the identification information, the service information of the service to be deployed, and the address information are the information in fig. 2. After confirming that the internal environment operates normally, the cluster sends a deployment instruction to the controller, the controller monitors the target assembly according to the deployment instruction, acquires service information stored by the target assembly, creates a second assembly for storing the service information in the middleware system, and deploys the service in the cluster by using the second assembly.
As shown in fig. 3, an embodiment of the present invention further provides a middleware system 200, which includes a controller 201;
the controller is used for creating a first component based on address information of deployed services and internal addresses of the deployed services on a cluster, and the first component stores mapping between the address information and the internal addresses;
the first component to receive a request for a first service of the deployed services; inquiring an internal address corresponding to the request in the first component according to the address information of the request, wherein the address information of the request is the same as the address information of the corresponding first service; modifying the address information of the request into an internal address corresponding to the request; and sending the request to the corresponding deployed service based on the address information modified by the request.
Optionally, the system further comprises a target component 202 corresponding to the controller 201;
the target component 202 is configured to obtain service information and address information of a service to be deployed, where the service information at least includes a service name and a service port of the service to be deployed, and the address information at least includes an external address and a path of the service to be deployed;
the controller 201 is further configured to deploy the service to be deployed in the cluster according to the service information and the address information of the service to be deployed, so as to obtain a deployed service; generating an internal address of the deployed service on the cluster;
the internal address is used for indicating the position of the deployed service in the cluster, and the address information of the deployed service is the same as the address information of the service to be deployed.
Optionally, the target component 202 is further configured to send service information and address information of the service to be deployed to the cluster;
the controller 201 is further configured to receive a deployment instruction sent by the cluster based on the service information and the address information, where the deployment instruction is used to instruct that the service to be deployed is deployed in the cluster; and responding to the deployment instruction, and deploying the service to be deployed in the cluster.
Optionally, the controller 201 is further configured to, in response to the deployment instruction, create a second component according to the service information of the service to be deployed;
the second component is configured to deploy the service to be deployed in the cluster.
An embodiment of the present invention further provides an electronic device, as shown in fig. 4, including a processor 301, a communication interface 302, a memory 303, and a communication bus 304, where the processor 301, the communication interface 302, and the memory 303 complete mutual communication through the communication bus 304.
A memory 303 for storing a computer program;
a processor 301, configured to execute the program stored in the memory 303, wherein when the computer program is executed by the processor 301, the processor is configured to create a first component inside the middleware system based on address information of a deployed service and an internal address of the deployed service on a cluster;
receiving a request for a first service of the deployed services;
inquiring an internal address corresponding to the request in the first component according to the address information of the request;
modifying the address information of the request into an internal address corresponding to the request;
and sending the request to the corresponding deployed service based on the address information modified by the request.
Optionally, the computer program, when executed by the processor 301, is further configured to obtain service information and address information of a service to be deployed;
deploying the service to be deployed in the cluster according to the service information and the address information of the service to be deployed to obtain deployed service;
generating an internal address of the deployed service on the cluster.
Optionally, the computer program, when executed by the processor 301, is further configured to send service information and address information of the service to be deployed to the cluster;
receiving a deployment instruction sent by the cluster based on the service information and the address information;
and responding to the deployment instruction, and deploying the service to be deployed in the cluster.
Optionally, the computer program, when executed by the processor 301, is further configured to, in response to the deployment instruction, create a second component inside the middleware system according to the service information of the service to be deployed;
deploying the service to be deployed in the cluster using the second component.
The communication bus mentioned in the electronic device may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The communication bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown, but this does not mean that there is only one bus or one type of bus.
The communication interface is used for communication between the terminal and other equipment.
The Memory may include a Random Access Memory (RAM), and may also include a non-volatile Memory (non-volatile Memory), such as at least one disk Memory. Alternatively, the memory may be at least one memory device located remotely from the processor.
The Processor may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; the Integrated Circuit may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, a discrete Gate or transistor logic device, or a discrete hardware component.
In yet another embodiment provided by the present invention, a computer-readable storage medium is further provided, which has instructions stored therein, and when the computer-readable storage medium runs on a computer, the computer is caused to execute the service access method described in any one of the above embodiments.
In a further embodiment provided by the present invention, there is also provided a computer program product containing instructions which, when run on a computer, cause the computer to perform the service access method described in any of the above embodiments.
In the above embodiments, all or part of the implementation may be realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the invention to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that includes one or more available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid State Disk (SSD)), among others.
It should be noted that, in this document, 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. Also, 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 phrases "comprising one of 8230; \8230;" 8230; "does not exclude the presence of additional like elements in a process, method, article, or apparatus that comprises the element.
All the embodiments in the present specification are described in a related manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The above description is only for the preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention shall fall within the protection scope of the present invention.
Claims (8)
1. A service access method is applied to a middleware system and comprises the following steps:
creating a first component inside the middleware system based on address information of a deployed service and an internal address of the deployed service on a cluster, wherein the first component stores mapping between the address information and the internal address;
receiving a request for a first service of the deployed services;
inquiring an internal address corresponding to the request in the first component according to the address information of the request, wherein the address information of the request is the same as the address information of the first service;
modifying the address information of the request into an internal address corresponding to the request;
sending the request to a corresponding deployed service based on the address information modified by the request;
wherein, before creating the first component inside the middleware system based on the address information of the deployed service and the internal address of the deployed service on the cluster, the method further comprises:
acquiring service information and address information of a service to be deployed, wherein the service information at least comprises a service name and a service port of the service to be deployed, and the address information at least comprises an external address and a path of the service to be deployed;
deploying the service to be deployed in the cluster according to the service information and the address information of the service to be deployed to obtain deployed service;
generating an internal address of the deployed service on the cluster;
the internal address is used for indicating the position of the deployed service in the cluster, and the address information of the deployed service is the same as the address information of the service to be deployed.
2. The method according to claim 1, wherein the deploying the service to be deployed in the cluster according to the service information and the address information of the service to be deployed comprises:
sending the service information and the address information of the service to be deployed to the cluster;
receiving a deployment instruction sent by the cluster based on the service information and the address information, wherein the deployment instruction is used for instructing the middleware system to deploy the service to be deployed;
and responding to the deployment instruction, and deploying the service to be deployed in the cluster.
3. The method of claim 2, wherein the deploying the service to be deployed in the cluster in response to the deployment instruction comprises:
in response to the deployment instruction, creating a second component in the middleware system according to the service information of the service to be deployed;
deploying the service to be deployed in the cluster using the second component.
4. A middleware system comprising a controller;
the controller is used for creating a first component based on address information of deployed services and internal addresses of the deployed services on a cluster, and the first component stores mapping between the address information and the internal addresses;
the first component to receive a request for a first service of the deployed services; inquiring an internal address corresponding to the request in the first component according to the address information of the request, wherein the address information of the request is the same as the address information of the corresponding first service; modifying the address information of the request into an internal address corresponding to the request; sending the request to a corresponding deployed service based on the address information modified by the request;
wherein the system further comprises a target component corresponding to the controller;
the target component is used for acquiring service information and address information of a service to be deployed, wherein the service information at least comprises a service name and a service port of the service to be deployed, and the address information at least comprises an external address and a path of the service to be deployed;
the controller is further configured to deploy the service to be deployed in the cluster according to the service information and the address information of the service to be deployed, so as to obtain a deployed service; generating an internal address of the deployed service on the cluster;
the internal address is used for indicating the position of the deployed service in the cluster, and the address information of the deployed service is the same as the address information of the service to be deployed.
5. The system of claim 4, wherein the target component is further configured to send service information and address information of the service to be deployed to the cluster;
the controller is further configured to receive a deployment instruction sent by the cluster based on the service information and the address information, where the deployment instruction is used to instruct the middleware system to deploy the service to be deployed; and responding to the deployment instruction, and deploying the service to be deployed in the cluster.
6. The system of claim 5, wherein the controller is further configured to create a second component according to the service information of the service to be deployed in response to the deployment instruction;
the second component is configured to deploy the service to be deployed in the cluster.
7. The electronic equipment is characterized by comprising a processor, a communication interface, a memory and a communication bus, wherein the processor and the communication interface are used for realizing the communication between the processor and the memory through the communication bus;
a memory for storing a computer program;
a processor for implementing the service access method of any one of claims 1 to 3 when executing a program stored on the memory.
8. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out a service access method according to any one of claims 1-3.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110440844.8A CN113141405B (en) | 2021-04-23 | 2021-04-23 | Service access method, middleware system, electronic device, and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110440844.8A CN113141405B (en) | 2021-04-23 | 2021-04-23 | Service access method, middleware system, electronic device, and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113141405A CN113141405A (en) | 2021-07-20 |
| CN113141405B true CN113141405B (en) | 2022-11-15 |
Family
ID=76813685
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110440844.8A Active CN113141405B (en) | 2021-04-23 | 2021-04-23 | Service access method, middleware system, electronic device, and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113141405B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113726855B (en) * | 2021-07-30 | 2023-02-07 | 北京奇艺世纪科技有限公司 | Service aggregation method, device, electronic equipment and computer-readable storage medium |
| CN113726897B (en) * | 2021-09-01 | 2024-04-19 | 马上消费金融股份有限公司 | Data processing method, device and equipment |
| CN113676564B (en) * | 2021-09-28 | 2022-11-22 | 深信服科技股份有限公司 | Data transmission method, device and storage medium |
| CN115714747A (en) * | 2022-12-13 | 2023-02-24 | 重庆紫光华山智安科技有限公司 | Kubernetes-based cluster internal network flow optimization method, equipment, system and medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105897946A (en) * | 2016-04-08 | 2016-08-24 | 北京搜狐新媒体信息技术有限公司 | Obtaining method and system of access address |
| CN108429787A (en) * | 2018-01-30 | 2018-08-21 | 中经社控股有限公司 | Container dispositions method and device, computer storage media, terminal |
| CN111049753A (en) * | 2019-12-18 | 2020-04-21 | 网易（杭州）网络有限公司 | Message sending method and device, electronic equipment and computer readable medium |
| CN111708560A (en) * | 2020-06-17 | 2020-09-25 | 云和恩墨(北京)信息技术有限公司 | Automatic deployment method and device of database high-availability management system |
| CN112130866A (en) * | 2020-10-09 | 2020-12-25 | 腾讯科技（深圳）有限公司 | Application deployment method and related device |
| CN112579310A (en) * | 2019-09-30 | 2021-03-30 | 北京车和家信息技术有限公司 | Service calling method and device |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020107977A1 (en) * | 2000-12-07 | 2002-08-08 | Andrew Dunshea | Multi-server system dynamic re-configuration |
| US8266104B2 (en) * | 2008-08-26 | 2012-09-11 | Sap Ag | Method and system for cascading a middleware to a data orchestration engine |
| US9336060B2 (en) * | 2011-06-17 | 2016-05-10 | Microsoft Technology Licensing, Llc | Middleware services framework for on-premises and cloud deployment |
-
2021
- 2021-04-23 CN CN202110440844.8A patent/CN113141405B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105897946A (en) * | 2016-04-08 | 2016-08-24 | 北京搜狐新媒体信息技术有限公司 | Obtaining method and system of access address |
| CN108429787A (en) * | 2018-01-30 | 2018-08-21 | 中经社控股有限公司 | Container dispositions method and device, computer storage media, terminal |
| CN112579310A (en) * | 2019-09-30 | 2021-03-30 | 北京车和家信息技术有限公司 | Service calling method and device |
| CN111049753A (en) * | 2019-12-18 | 2020-04-21 | 网易（杭州）网络有限公司 | Message sending method and device, electronic equipment and computer readable medium |
| CN111708560A (en) * | 2020-06-17 | 2020-09-25 | 云和恩墨(北京)信息技术有限公司 | Automatic deployment method and device of database high-availability management system |
| CN112130866A (en) * | 2020-10-09 | 2020-12-25 | 腾讯科技（深圳）有限公司 | Application deployment method and related device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113141405A (en) | 2021-07-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113141405B (en) | Service access method, middleware system, electronic device, and storage medium | |
| CN111614738B (en) | Service access method, device, equipment and storage medium based on Kubernetes cluster | |
| EP3291499A1 (en) | Method and apparatus for network service capacity expansion | |
| CN109587281B (en) | Container configuration method and computing node | |
| CN108924274B (en) | Domain name system DNS processing method and device, storage medium and electronic equipment | |
| CN111182089B (en) | Container cluster system, method and device for accessing big data assembly and server | |
| CN109995552B (en) | VNF service instantiation method and device | |
| CN109936641B (en) | Domain name resolution method, virtual switch and distributed DNS system | |
| CN113806037A (en) | Service calling method and device, storage medium and electronic equipment | |
| CN113810230A (en) | Method, device and system for carrying out network configuration on containers in container cluster | |
| CN110633175A (en) | Multi-computer-room data processing method based on micro-service, electronic equipment and storage medium | |
| CN114244654B (en) | URL forwarding method, device, equipment and computer storage medium | |
| CN115314353A (en) | Device and method for realizing single-pod multi-network card based on kubernets | |
| CN111064786A (en) | Account identifier management method and device | |
| CN114710549A (en) | Dynamic management method, system and service node of network card in container platform | |
| WO2021175105A1 (en) | Connection method and apparatus, device, and storage medium | |
| CN113268308B (en) | Information processing method, device and storage medium | |
| CN112751935A (en) | Request processing method and device, electronic equipment and storage medium | |
| CN109375946B (en) | Method and system for managing component package of node package manager | |
| CN115333993B (en) | Method, equipment and storage medium for customizing container group routing in container environment | |
| CN113726855B (en) | Service aggregation method, device, electronic equipment and computer-readable storage medium | |
| CN113612643B (en) | Network configuration method, device and equipment of cloud mobile phone and storage medium | |
| CN114070889B (en) | Configuration method, traffic forwarding device, storage medium, and program product | |
| CN114338809A (en) | Access control method, device, electronic equipment and storage medium | |
| CN117032905B (en) | Method and system for associating container cluster with block storage and virtual machine |
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 |