[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

CN113986325A - Development platform, design method, storage medium and terminal for multi-version service integration - Google Patents

Development platform, design method, storage medium and terminal for multi-version service integration Download PDF

Info

Publication number
CN113986325A
CN113986325A CN202111099026.2A CN202111099026A CN113986325A CN 113986325 A CN113986325 A CN 113986325A CN 202111099026 A CN202111099026 A CN 202111099026A CN 113986325 A CN113986325 A CN 113986325A
Authority
CN
China
Prior art keywords
service
version
information
routing
dynamic
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.)
Pending
Application number
CN202111099026.2A
Other languages
Chinese (zh)
Inventor
高亚峰
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shanghai Fanyu Information Technology Co ltd
Original Assignee
Shanghai Fanyu Information Technology Co ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Shanghai Fanyu Information Technology Co ltd filed Critical Shanghai Fanyu Information Technology Co ltd
Priority to CN202111099026.2A priority Critical patent/CN113986325A/en
Publication of CN113986325A publication Critical patent/CN113986325A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/70Software maintenance or management
    • G06F8/71Version control; Configuration management
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/70Software maintenance or management
    • G06F8/76Adapting program code to run in a different environment; Porting

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The invention provides a multi-version service integrated development platform, a design method, a storage medium and a terminal, wherein the multi-version service integrated development platform comprises: the registration center is used for acquiring the service information of the multi-version service and carrying out centralized management on the service information; and the dynamic route is connected with the registration center, and acquires the dynamic route configuration information of each version of service based on the service information so as to allow a user to dynamically switch different versions of service. The invention integrates multi-version services through the registration center to form a set of centralized development/test environment, and supports coexistence of multi-version services; and dynamic routing is employed to support dynamic switching between multi-version services. The invention shares resources and only needs to maintain one set of environment, thereby effectively reducing the consumption of manpower and resources in multi-branch parallel development, reducing the repeated workload, reducing the difficulty of maintenance and update, and effectively improving the environmental stability and the efficiency and the quality of parallel development by monitoring and regularly synchronizing service information in real time.

Description

Development platform, design method, storage medium and terminal for multi-version service integration
Technical Field
The invention relates to the field of computers, in particular to a development platform, a design method, a storage medium and a terminal for multi-version service integration.
Background
In the daily multi-branch development process of software, in order to ensure the independence of each branch and further ensure the accuracy of development and test to the maximum extent, an independent environment is generally required to be prepared for each branch.
However, the creation and maintenance of each independent environment requires a lot of resources such as manpower and servers, and especially, a distributed system, each system is composed of tens to hundreds of subsystems, and establishing independent environments for such subsystems respectively causes huge consumption of manpower and resources, and the subsequent updating and maintenance of these independent environments are also very difficult projects.
In order to reduce the manpower, resource consumption and the difficulty of updating and maintaining, one or two sets of fixed environments are generally provided. However, the fixed environment will greatly limit the efficiency of multi-branch parallel development and easily cause confusion in branch development.
Disclosure of Invention
In view of the above-mentioned shortcomings of the prior art, the present invention provides a development platform, a design method, a storage medium and a terminal for multi-version service integration, which are used for simultaneously meeting the requirements of multi-branch parallel development and reducing the consumption of environmental resources in the prior art.
To achieve the above and other related objects, a first aspect of the present invention provides a multi-version service integration development platform, including: the registration center is used for acquiring the service information of the multi-version service and carrying out centralized management on the service information; and the dynamic route is connected with the registration center, and acquires the dynamic route configuration information of each version of service based on the service information so as to allow a user to dynamically switch different versions of service.
In some embodiments of the first aspect of the present invention, the dynamic routing comprises: http dynamic routing, service dynamic routing, and message dynamic routing.
In some embodiments of the first aspect of the present invention, the service information of the multi-version service includes location information and status information; and the dynamic route acquires matched target service information based on the service request information of the user and the position information and the state information of the multi-version service.
In some embodiments of the first aspect of the present invention, the dynamic route comprises a service dynamic route; the service dynamic route receives service request information of a user, wherein the service request information comprises identity identification information and route configuration information; and the service dynamic route acquires a calling path of the target service based on the service request information so as to enable a user to call the required service.
In some embodiments of the first aspect of the present invention, the dynamic route comprises a distributed route comprising a first distributed route and a second distributed route; wherein the first distributed route is used for a user to set a routing rule, and the second distributed route is connected with the first distributed route to synchronize the routing rule.
In some embodiments of the first aspect of the present invention, the multi-version service comprises: a default version service and a development/test version service.
To achieve the above and other related objects, a second aspect of the present invention provides a method for designing a multi-version service integrated development platform, comprising: acquiring service information of multi-version service through a registration center and carrying out centralized management on the service information; and acquiring dynamic routing configuration information of each version of service through dynamic routing and based on the service information so as to dynamically switch different versions of service for users.
To achieve the above and other related objects, a third aspect of the present invention provides a computer-readable storage medium having a computer program stored thereon, the computer program, when executed by a processor, implementing a method of designing a development platform for multi-version service integration.
To achieve the above and other related objects, a fourth aspect of the present invention provides an electronic terminal, comprising: a processor and a memory; the memory is used for storing computer programs, and the processor is used for executing the computer programs stored by the memory so as to enable the terminal to execute the design method of the multi-version service integrated development platform.
As described above, the development platform, the design method, the storage medium and the terminal for multi-version service integration provided by the present invention have the following beneficial effects: integrating multi-version services through a registration center to form a set of concentrated development/test environment and support coexistence of multi-version services; and dynamic routing is adopted to support dynamic switching among multi-version services, and the development test requirements of users are met. The invention has the advantages that the resources are shared, only one set of environment needs to be maintained, and the manpower and resource consumption in the multi-branch parallel development is effectively reduced; only one set of environment needs to be maintained, so that the repeated workload is reduced, and the subsequent maintenance and updating difficulty is reduced; the real-time monitoring and the periodic synchronization of the service information effectively improve the environmental stability; when a new project is started and developed, independent environment building is not needed, development can be started immediately, local joint debugging and cross-team joint debugging are started by one key in the development process, and the efficiency and the quality of multi-branch parallel development are obviously improved.
Drawings
Fig. 1 is a schematic structural diagram of a development platform for multi-version service integration according to an embodiment of the present invention.
Fig. 2 is a schematic diagram of an integrated development environment of a development platform according to an embodiment of the present invention.
Fig. 3 is a schematic flowchart illustrating a work flow of a development platform in a personal routing mode according to an embodiment of the present invention.
Fig. 4 is a schematic flowchart illustrating a work flow of a development platform in a default routing mode according to an embodiment of the present invention.
Fig. 5 is a schematic diagram illustrating a working flow of a development platform in a circle routing mode according to an embodiment of the present invention.
Fig. 6 is a flowchart illustrating a method for designing a multi-version service integrated development platform according to an embodiment of the present invention.
Fig. 7 is a schematic structural diagram of an electronic terminal according to an embodiment of the invention.
Detailed Description
The embodiments of the present invention are described below with reference to specific embodiments, and other advantages and effects of the present invention will be easily understood by those skilled in the art from the disclosure of the present specification. The invention is capable of other and different embodiments and of being practiced or of being carried out in various ways, and its several details are capable of modification in various respects, all without departing from the spirit and scope of the present invention. It is to be noted that the features in the following embodiments and examples may be combined with each other without conflict.
It is noted that in the following description, reference is made to the accompanying drawings which illustrate several embodiments of the present invention. It is to be understood that other embodiments may be utilized and that mechanical, structural, electrical, and operational changes may be made without departing from the spirit and scope of the present invention. The following detailed description is not to be taken in a limiting sense, and the scope of embodiments of the present invention is defined only by the claims of the issued patent. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention.
Also, as used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context indicates otherwise. It will be further understood that the terms "comprises," "comprising," and/or "comprising," when used in this specification, specify the presence of stated features, operations, elements, components, items, species, and/or groups, but do not preclude the presence, or addition of one or more other features, operations, elements, components, items, species, and/or groups thereof. The terms "or" and/or "as used herein are to be construed as inclusive or meaning any one or any combination. Thus, "A, B or C" or "A, B and/or C" means "any of the following: a; b; c; a and B; a and C; b and C; A. b and C ". An exception to this definition will occur only when a combination of elements, functions or operations are inherently mutually exclusive in some way.
The invention aims to provide a development platform, a design method, a storage medium and a terminal for multi-version service integration, and aims to solve the technical problems that in the prior art, the establishment and maintenance of an independent environment consume resources such as manpower and servers, the fixed environment limits the multi-branch parallel development efficiency, and the fixed environment is easy to cause the confusion of branch development.
In order to make the objects, technical solutions and advantages of the present invention more apparent, the technical solutions in the embodiments of the present invention are further described in detail by the following embodiments in conjunction with the accompanying drawings. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
Example one
As shown in fig. 1, an embodiment of the present invention provides a structural schematic diagram of a development platform for multi-version service integration, which includes: the registration center 11 is used for acquiring service information of multi-version services and performing centralized management on the service information; and the dynamic route 12 is connected with the registration center 11, and acquires dynamic route configuration information of each version of service based on the service information so as to allow a user to dynamically switch different versions of service.
The registry 11 records the mapping of services and service addresses. Each version of service registers its own service information to the registry, where the service information may include location information, such as an ip Address (Internet Protocol Address), a url (Uniform Resource Locator), a domain name, and may also include state information, such as service start, service stop, and service pause. The registry stores and manages the information, and when a user (such as a software developer/tester) needs to call a relevant service, the registry inquires about the address of the required service and calls a corresponding version of the service through the address. Among them, the registry 11 may be selected from Zookeeper, Consul, Eureka, Nacos, and the like.
A dynamic route 12 is connected to the registry. The router in the dynamic routing can automatically establish a routing table of the router, exchange routing information in real time, and timely adjust and acquire the latest routing table according to the latest routing information so that a user can acquire an optimal service call path and an optimal switching call path between services of different versions.
Preferably, the dynamic routing 12 includes http dynamic routing, service dynamic routing, and message dynamic routing. The http dynamic route is used for receiving and forwarding an http request, and Nginx can be selected; the service dynamic route is used for dynamically configuring dynamic access paths of services of various versions, and specifically, a DUBBO dynamic route or a Spring Cloud dynamic route and the like can be selected; the message dynamic routing is used for sending queue messages and sending subject messages, and particularly, the ActiveMQ message dynamic routing can be selected.
In some examples, the user issues service request information, and the dynamic route 12 calculates and acquires matching target service information based on the service request information of the user and the location information and the status information of the multi-version service synchronized from the registry 11. The dynamic route 12 calculates and acquires an optimal calling path for the user to call the target service based on the target service information (such as ip address, domain name, url, etc. of the target service) and the newly exchanged route information. The calling of the target service comprises the following steps: generalized calls, parallel service calls, asynchronous service calls, synchronous service calls, and the like.
In some examples, the service dynamic route receives service request information of a user, the service request information including identification information and routing configuration information; and the service dynamic route acquires a calling path of the target service based on the service request information so as to enable a user to call the required service. The development environment integrates multiple versions of multiple services, such as a default version and a development/test version (wherein the default version is an irremodifiable version, when a user needs to develop one of the services, the development/test version of the service is called, the default version is called by the other services, and the services are mutually matched and coordinated to realize program functions), wherein the default version and the development/test version can be classified according to client types, application scenes, client requirements, development teams and the like. The user selects a certain version of a certain service from the service list to call based on the dynamic service routing, and the dynamic service routing can meet the flexible routing requirement of the user.
In the preferred embodiment of the present embodiment, the dynamic route 12 includes a distributed route, which includes a first distributed route and a second distributed route; wherein the first distributed route is used for a user to set a routing rule, and the second distributed route is connected with the first distributed route to synchronize the routing rule. Specifically, Zookeeper, Nacos, or Consul may be used to implement configuration and coordination of routing rules of each router. The routing rule is set in one place, then the routing rule is synchronized to different using places, and the optimal calling path of the service is obtained through local calculation based on the routing rule, so that the routing efficiency is improved to the maximum extent, and further the development efficiency is improved.
Further, as shown in fig. 2, an integrated development environment diagram of a development platform is provided in the embodiment of the present invention, and the registry 11 stores address information (location information) of a service provider, attribute information related to service release, state information, and the like. The service provider in FIG. 2 includes u-service, u-service v ', p-service, g-service, and g-service v', where u-service and u-service v 'respectively represent different versions of u-service, g-service and g-service v' respectively represent different versions of g-service, and p-service represents p-service. front-ui represents a front-end user interface, and a user can select the type and the version of the service through the front-end user interface, so that flexible switching and calling of the service are realized.
Fig. 3-5 are schematic diagrams illustrating the work flow of the development platform under different routing modes, respectively, where fig. 3 is a personal routing mode, fig. 4 is a default routing mode, and fig. 5 is a circle routing mode. In FIG. 4, in the default routing mode, browser B obtains the desired service via the illustrated service path. In contrast to fig. 3, browser B has a different routing rule and a different service path than browser a. In fig. 5, in the circle routing mode, the routing rules of the browser a and the browser B are the same, and the service paths are the same. The work flows of fig. 3 to fig. 5 are basically the same, and therefore, the work flow of the development platform will be described in detail below by taking fig. 3 as an example only:
as shown in fig. 3, in the personal routing mode, the browser a sends service request information to the http route, where the service request information includes the identity information and the routing configuration information of the browser a; the http route forwards the service request information to a registration center, and synchronizes all service information and routing rules from the registration center; the http routing calculates and obtains corresponding target service information based on the service request information, the received service information and the routing rule; the http routing feeds the target service information back to a front-end user interface (front-ui), the user selects a certain version of a certain service according to needs on the front-end user interface (for example, the service version can be freely switched by simple selection), the service routing calculates and obtains an optimal calling path of the target service based on the service request information and the target service information, and the browser a calls the required service through the optimal calling path. In some examples, the development platform includes a request distribution center, and when multi-branch synchronous parallel development is performed, service request information is processed by the request distribution center after a request call amount of a service reaches a preset threshold, such as request filtering, request caching, request distribution, and the like.
It should be noted that the division of each module of the above platform is only a division of a logic function, and the actual implementation may be wholly or partially integrated into one physical entity, or may be physically separated. And these modules can be realized in the form of software called by processing element; or may be implemented entirely in hardware; and part of the modules can be realized in the form of calling software by the processing element, and part of the modules can be realized in the form of hardware. For example, the registry may be a processing element separately set up, or may be implemented by being integrated in a chip of the apparatus, or may be stored in a memory of the apparatus in the form of program code, and a processing element of the apparatus calls and executes the functions of the registry. Other modules are implemented similarly. In addition, all or part of the modules can be integrated together or can be independently realized. The processing element described herein may be an integrated circuit having signal processing capabilities. In implementation, each step of the above method or each module above may be implemented by an integrated logic circuit of hardware in a processor element or an instruction in the form of software.
For example, the above modules may be one or more integrated circuits configured to implement the above methods, such as: one or more Application Specific Integrated Circuits (ASICs), or one or more microprocessors (DSPs), or one or more Field Programmable Gate Arrays (FPGAs), among others. For another example, when one of the above modules is implemented in the form of a Processing element scheduler code, the Processing element may be a general-purpose processor, such as a Central Processing Unit (CPU) or other processor capable of calling program code. For another example, these modules may be integrated together and implemented in the form of a system-on-a-chip (SOC).
Example two
As shown in fig. 6, an embodiment of the present invention provides a flow chart of a design method for a multi-version service integrated development platform, including:
and S61, acquiring the service information of the multi-version service through the registration center and carrying out centralized management on the service information. Furthermore, the registry monitors and updates the service information of the multi-version service in real time and regularly, so that the stability of a development environment is improved, and the efficiency and quality of multi-branch parallel development are improved.
And S62, acquiring dynamic routing configuration information of each version of service through dynamic routing and based on the service information so as to dynamically switch different versions of service for users. Taking default version service and development/test version service as examples, an application program is divided into a plurality of services, the services are mutually matched and coordinated to realize the program function, when a user needs to develop one of the services, the development/test version of the service is called, and the default version is called by the other services, so that the development orderliness is guaranteed.
It should be noted that the method provided in this embodiment is similar to the development platform and the implementation manner provided in the foregoing, and therefore, the description is omitted. It should also be noted that in some embodiments, the method may be applied to a controller, such as an arm (advanced RISC machines) controller, an fpga (field Programmable Gate array) controller, a soc (system on chip) controller, a dsp (digital Signal processing) controller, or an mcu (microcontroller unit) controller, among others. In some embodiments, the methods are also applicable to computers including components such as memory, memory controllers, one or more processing units (CPUs), peripheral interfaces, RF circuits, audio circuits, speakers, microphones, input/output (I/O) subsystems, display screens, other output or control devices, and external ports; the computer includes, but is not limited to, Personal computers such as desktop computers, notebook computers, tablet computers, smart phones, smart televisions, Personal Digital Assistants (PDAs), and the like. In other embodiments, the method may also be applied to servers, which may be arranged on one or more physical servers, or may be formed of a distributed or centralized cluster of servers, depending on various factors such as function, load, etc.
EXAMPLE III
As shown in fig. 7, an embodiment of the present invention provides a schematic structural diagram of an electronic terminal. The electronic terminal provided by the embodiment comprises: a processor 71, a memory 72, a communicator 73; the memory 72 is connected to the processor 71 and the communicator 73 through a system bus and is used for mutual communication, the memory 72 is used for storing computer programs, the communicator 73 is used for communicating with other devices, and the processor 71 is used for running the computer programs so as to enable the electronic terminal to execute the steps of the design method of the multi-version service integrated development platform.
The above-mentioned system bus may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The system bus may be divided into an address bus, a data bus, a control bus, and the like. 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 realizing communication between the database access device and other devices (such as a client, a read-write library and a read-only library). The Memory may include a Random Access Memory (RAM), and may further include a non-volatile Memory (non-volatile Memory), such as at least one disk Memory.
The Processor may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; the device can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, discrete hardware component.
Example four
An embodiment of the present invention provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the method for designing the multi-version service integrated development platform.
Those of ordinary skill in the art will understand that: all or part of the steps for implementing the above method embodiments may be performed by hardware associated with a computer program. The aforementioned computer program may be stored in a computer readable storage medium. When executed, the program performs steps comprising the method embodiments described above; and the aforementioned storage medium includes: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.
In summary, the present invention provides a multi-version service integration development platform, a design method, a storage medium and a terminal, which integrate multi-version services through a registry to form a set of centralized development/test environment to support coexistence of multi-version services; and dynamic routing is employed to support dynamic switching between multi-version services. The invention has the advantages that the resources are shared, only one set of environment needs to be maintained, and the manpower and resource consumption in the multi-branch parallel development is effectively reduced; only one set of environment is required to be maintained, so that the repeated workload is reduced, the subsequent maintenance and updating difficulty is reduced, and the environmental stability is greatly improved by combining monitoring and periodic synchronization; when a new project is started and developed, independent environment building is not needed, development can be started immediately, local joint debugging and cross-team joint debugging are started by one key in the development process, and the efficiency and the quality of multi-branch parallel development are obviously improved. Therefore, the present invention effectively overcomes various disadvantages of the prior art and has high industrial utilization value.
The foregoing embodiments are merely illustrative of the principles and utilities of the present invention and are not intended to limit the invention. Any person skilled in the art can modify or change the above-mentioned embodiments without departing from the spirit and scope of the present invention. Accordingly, it is intended that all equivalent modifications or changes which can be made by those skilled in the art without departing from the spirit and technical spirit of the present invention be covered by the claims of the present invention.

Claims (10)

1. A multi-versioning service integrated development platform, comprising:
the registration center is used for acquiring the service information of the multi-version service and carrying out centralized management on the service information;
and the dynamic route is connected with the registration center, and acquires the dynamic route configuration information of each version of service based on the service information so as to allow a user to dynamically switch different versions of service.
2. The multi-versioning service integration development platform of claim 1, wherein the dynamic routing comprises: http dynamic routing, service dynamic routing, and message dynamic routing.
3. The multi-version service integrated development platform of claim 1, wherein the service information of the multi-version service comprises location information and status information; and the dynamic route acquires matched target service information based on the service request information of the user and the position information and the state information of the multi-version service.
4. The multi-versioning service integration development platform of claim 2, wherein the dynamic routing comprises dynamic routing of services; the service dynamic route receives service request information of a user, wherein the service request information comprises identity identification information and route configuration information; and the service dynamic route acquires a calling path of the target service based on the service request information so as to enable a user to call the required service.
5. The multi-versioning service integration development platform of claim 1, wherein the dynamic routing comprises distributed routing including a first distributed routing and a second distributed routing; wherein the first distributed route is used for a user to set a routing rule, and the second distributed route is connected with the first distributed route to synchronize the routing rule.
6. The multi-version service integrated development platform of claim 1, wherein the multi-version service comprises: a default version service and a development/test version service.
7. A design method for a multi-version service integrated development platform is characterized by comprising the following steps:
acquiring service information of multi-version service through a registration center and carrying out centralized management on the service information;
and acquiring dynamic routing configuration information of each version of service through dynamic routing and based on the service information so as to dynamically switch different versions of service for users.
8. The method for designing a multi-version service integrated development platform according to claim 7, comprising: and the registration center monitors and updates the service information of the multi-version service in real time and periodically.
9. A computer-readable storage medium on which a computer program is stored, the computer program, when being executed by a processor, implementing a method for designing a multi-version service integrated development platform according to any one of claims 7 to 8.
10. An electronic terminal, comprising: a processor and a memory;
the memory is used for storing a computer program, and the processor is used for executing the computer program stored by the memory to enable the terminal to execute the design method of the multi-version service integrated development platform according to any one of claims 7 to 8.
CN202111099026.2A 2021-09-18 2021-09-18 Development platform, design method, storage medium and terminal for multi-version service integration Pending CN113986325A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111099026.2A CN113986325A (en) 2021-09-18 2021-09-18 Development platform, design method, storage medium and terminal for multi-version service integration

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111099026.2A CN113986325A (en) 2021-09-18 2021-09-18 Development platform, design method, storage medium and terminal for multi-version service integration

Publications (1)

Publication Number Publication Date
CN113986325A true CN113986325A (en) 2022-01-28

Family

ID=79736074

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111099026.2A Pending CN113986325A (en) 2021-09-18 2021-09-18 Development platform, design method, storage medium and terminal for multi-version service integration

Country Status (1)

Country Link
CN (1) CN113986325A (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102394928A (en) * 2011-10-31 2012-03-28 华南理工大学 Semanteme web service system under distributed environment
US20140164479A1 (en) * 2012-12-11 2014-06-12 Microsoft Corporation Smart redirection and loop detection mechanism for live upgrade large-scale web clusters
CN109327503A (en) * 2018-08-27 2019-02-12 珠海格力电器股份有限公司 Information management system and method, service router
CN112799682A (en) * 2021-04-13 2021-05-14 杭州太美星程医药科技有限公司 Data acquisition and processing system and method for operating multi-version application thereof

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102394928A (en) * 2011-10-31 2012-03-28 华南理工大学 Semanteme web service system under distributed environment
US20140164479A1 (en) * 2012-12-11 2014-06-12 Microsoft Corporation Smart redirection and loop detection mechanism for live upgrade large-scale web clusters
CN109327503A (en) * 2018-08-27 2019-02-12 珠海格力电器股份有限公司 Information management system and method, service router
CN112799682A (en) * 2021-04-13 2021-05-14 杭州太美星程医药科技有限公司 Data acquisition and processing system and method for operating multi-version application thereof

Similar Documents

Publication Publication Date Title
WO2020147466A1 (en) Method for invoking server and proxy server
CN111813570A (en) Event-driven message interaction method for power Internet of things
CN106649630A (en) Data query method and device
AU2012362829A1 (en) Cloud-edge topologies
Hoang et al. On software-defined networking and the design of SDN controllers
CN103581307A (en) Publishing/subscribing system based on clusters and method for guaranteeing reliability of publishing/subscribing system based on clusters
Ahmed et al. Process state synchronization-based application execution management for mobile edge/cloud computing
RU2008138577A (en) NETWORK SYSTEM
CN111181765A (en) Task processing method and device
CN115934855A (en) Full-link field level blood margin analysis method, system, equipment and storage medium
CN109639818A (en) Service discovery method, device, server and storage medium under a kind of cloud environment
CN105976245A (en) Simulated trading system and method
CN113067865A (en) Real-time interaction method and device for space flight measurement and control data
CN115550354A (en) Data processing method and device and computer readable storage medium
CN116155978A (en) Multi-registry adaptation method, device, electronic equipment and storage medium
CN113992748A (en) Reverse proxy method, system, medium, and terminal
CN114285695B (en) Communication method, device, apparatus, system and storage medium
US20150212834A1 (en) Interoperation method of newtork device performed by computing device including cloud operating system in could environment
CN113986325A (en) Development platform, design method, storage medium and terminal for multi-version service integration
WO2021078058A1 (en) Resource scheduling method, apparatus and device, and computer-readable storage medium
CN102970375A (en) Cluster configuration method and device
CN115391058B (en) SDN-based resource event processing method, resource creation method and system
CN111541608A (en) Network communication method, system and related device
CN110851166A (en) User-unaware application program updating method and device and computer equipment
CN115225450A (en) Multi-data machine room virtualization cluster management system based on edge computing

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