CN105791295A - Application server based on Node.js - Google Patents

Application server based on Node.js Download PDF

Info

Publication number
CN105791295A
CN105791295A CN201610124561.1A CN201610124561A CN105791295A CN 105791295 A CN105791295 A CN 105791295A CN 201610124561 A CN201610124561 A CN 201610124561A CN 105791295 A CN105791295 A CN 105791295A
Authority
CN
China
Prior art keywords
application
subprocess
container
work
request
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.)
Granted
Application number
CN201610124561.1A
Other languages
Chinese (zh)
Other versions
CN105791295B (en
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.)
Ningbo University of Technology
Original Assignee
Ningbo University of Technology
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 Ningbo University of Technology filed Critical Ningbo University of Technology
Priority to CN201610124561.1A priority Critical patent/CN105791295B/en
Publication of CN105791295A publication Critical patent/CN105791295A/en
Application granted granted Critical
Publication of CN105791295B publication Critical patent/CN105791295B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40Support for services or applications
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/1001Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1004Server selection for load balancing

Abstract

The invention relates to an application server based on Node.js. The application server comprises a Node.js operation application service system, an application data resource and an outer application server, wherein the Node.js operation application service system comprises an application server engine, a local application container and an outer application container. The application server engine comprises a host process and a sub-process container for carrying a plurality of operation sub-processes. Each operation sub-process is authorized to use an HTTP server and an application domain manager. The local application container bears a plurality of local applications. The local application container comprises a local application interface unit and a local application manager. The local application in the local application manager is connected with the application data resource through the local application interface unit. The outer application container bears a plurality of outer applications. Each outer application is composed of an outer application interface unit and interacts with an outer application server. Compared with the prior art, the application server is advantageous in that the application server can simultaneously support a plurality of user service requests.

Description

A kind of application server based on Node.js
Technical field
The present invention relates to a kind of application server based on Node.js, for providing the Server system software environment building web application.
Background technology
Node.js is born in May, 2009, is a kind of JavaScript running environment being implemented in ChromeV8 engine, and briefly Node.js is exactly the JavaScript operating in service end, it is built-in http server, it is possible to be directly realized by website and server capability.The JavaScript technology of this server end significantly enhances the motility of system development.Adopt Node.js can directly utilize JavaScript and carry out the exploitation of server end logic and page script, for the PHPs such as traditional PHP, JSP, give the motility that web developers is bigger, it is not necessary to build the http server of classes such as Apache in advance.But, too high motility also brings the excessive multiformity of standard and programmed method, and the more difficult selection of general web developers also finds out PHPs such as being similar to PHP, JSP one class conveniently development mode.Simultaneously, the http server directly created by Node.js have employed single-threaded asynchronous event treatment mechanism, although there being certain advance on treatment effeciency, but consider that distributed extensive website is applied in the demand of the aspect such as system throughput, fault-tolerance, the disposal ability and the means that depend on merely Node.js self are comparatively single, the more difficult system constructing high-performance, high reliability of common developer.The more important thing is, 80 ports are adopted when the general online service of Web server, when multiple independent Web to share a web server host simultaneously time, 80 ports can only be monopolized by a Web server, if now directly adopting the function that the carried http server of Node.js is supported, then only service the application of single website, waste 80 port resources of preciousness.
Although Node.js belongs to a kind of great development prospect, represent the programming language of following HTTP Website development technological development direction and platform technology is subject to the extensive concern of countries in the world researcher and developer, Node.js technology allows the JavaScript development language as website background logic, but this also makes general Websites application developer except logic is applied in the website realizing oneself, http server must also be set up for the website of oneself, add workload and complexity.Belonging to single-threaded structure based on the Node.js website realized, be mainly used in the application of single website, the concurrency for asking in a large number processes not strong, when an error occurs also without corresponding counter-measure.Therefore Node.js also has as a kind of emerging programming technique, its corresponding method and development mode much needs aspect perfect further.
Application server is for carrying the software frame of the application such as Web site and service logic and platform, construct a kind of application server based on Node.js, developer can be facilitated to carry out the exploitation of novel Node.js website and application, also it is expected to use Node.js self http server possessed more superior than single from system effectiveness and fault-tolerance aspect, is also expected to access multiple Node.js website easily simultaneously and makes it share same web server host resource.
Summary of the invention
The technical problem to be solved is to provide a kind of application server based on Node.js for above-mentioned prior art, applies for carrying the Web based on Node.js, can support multiple application simultaneously.
This invention address that the technical scheme that above-mentioned technical problem adopts is: a kind of application server based on Node.js, it is characterised in that: including: Node.js runs application service system, application data resource and external application servers;Wherein Node.js operation application service system includes application server engine, locally applied container and applications container;Aforementioned applications server engine includes host process and carries the subprocess container of some work subprocess, and each work subprocess is all authorized to use http server and application domain manager;Locally applied container carries some locally applied, and locally applied container comprises locally applied interface unit and locally applied manager, and locally applied in locally applied manager is connected with application data resource by locally applied interface unit;Applications container carries some applications, and each applications is made up of applications interface unit, is responsible for mutual with external application servers;
Wherein Node.js runs the application server engine monitoring users service request of application service system, after user sends service request, processes by below scheme:
S101, user initiate service request;
S102, application server engine accept user and service request and carry out following process;
If S103 service request content is locally applied, then it is for further processing, otherwise proceeds to step S107;
S104, the http address information acquisition Apply Names serviced according to user in request, send in locally applied manager corresponding locally applied by service request;
After the locally applied acquisition service request that S105, locally applied manager are corresponding, call application data resource by locally applied interface unit and carry out service request handling;
Result is fed back to application server engine after completing service request handling by S106, locally applied manager corresponding locally applied;
S107, application server engine service the http address in request according to user and obtain Apply Names, and service request signal is sent into applications corresponding in applications container;
Service request signal is forwarded to external application servers by applications interface unit by S108, applications;
Result is fed back to application server engine by applications container by S109, external application servers;
Result is fed back to user by S110, application server engine, it is achieved user responds.
As improvement, application server engine carries out user's service request handling and depends on http server and application domain manager, and subprocess container has several work subprocess, each work subprocess has http server and the right to use of application domain manager, and the concrete work process of application server engine comprises the steps:
S201, application server engine start, initially enter duty;
S202, application server engine create http server;
S203, application server engine create application domain manager;
S204, application server engine read the configuration file of service request, obtain the work subprocess quantity N servicing request in configuration file;
S205, parameters optimization N: first determining whether that whether N is less than 1, in this way, just N assignment is 1;As no, just N assignment is CPU quantity;
S206, establishment service processes manager;
S207, startup host process;
S208, starting N number of work subprocess and enter S209 and continue executing with in subprocess container, each work subprocess proceeds to step S211 process;
S209, host process monitoring work subprocess state also carry application domain manager, carry out application domain management;
If S210 occurs that work subprocess i lost efficacy, then restart work subprocess i, proceed to step S209;
After N number of work subprocess in S211 subprocess container starts, each work subprocess obtains the right to use of http server and application domain manager;
N number of work subprocess in S212, subprocess container enters idle condition, monitors HTTP request;
If S213 user initiates HTTP service request, from subprocess container, choose vacant working subprocess j;
S214, work subprocess j complete HTTP service request and process and proceed to step S212, transfer idle condition to and continue monitoring service request.
Improving, Node.js runs application service system and realizes user by application domain manager and service the distribution of request and distribute, and then realizes the application server support function to multiple application again;Wherein the host process workflow of application server engine is:
S301, host process start;
S302, host process startup work subprocess, work subprocess obtains application domain manager;
The application in locally applied container and applications container retrieved by S303, application domain manager;
List of application set up by S304, application domain manager, and all application are sent into list of application;
S305, host process monitoring work subprocess state also carry out application domain management;
If a certain application exception occurs S306, then proceed to step S309;
If S307 occurs work subprocess to lose efficacy, enter next step;
S308, host process restart inefficacy work subprocess;
The application of this exception deleted by S309, application domain manager, and proceeds to next step;
If S310 occurs newly-increased or deletes application, adjust list of application, and proceed to step S304.
Work subprocess in subprocess container is responsible for that user services request and is distributed concrete application, and its specific works flow process is as follows:
S401, progress of work i start;
S402, progress of work i obtain the http server right to use;
S403, progress of work i obtain the application domain manager right to use;
S404, progress of work i enter idle process queue, wait in line user and service request;
S405, user send HTTP request;
S406, progress of work i dequeue, obtain user's request;
S407, progress of work i read the Apply Names of user's request from http address;
Request is sent into the application that request is corresponding by the application domain manager in S408, progress of work i;
S409, apply request and processed and http server that result is back in progress of work i, and then realize the response of user's request: if this applies with basing on practicality, then locally applied container is sent in request, processed by locally applied container again, obtain application data resource, and then complete user's response;If this application is applications, then request send into applications container, by applications container transfer external application servers carry out user ask response, return response results;
Multiple work subprocess in subprocess container can be simultaneously different accordingly user service request.
Compared with prior art, it is an advantage of the current invention that: carry the Web based on Node.js and apply, can support that multiple user services request simultaneously.
Accompanying drawing explanation
Fig. 1 is the block diagram of the application server in the embodiment of the present invention based on Node.js;
Fig. 2 is the overview flow chart of user's service request response process in the embodiment of the present invention;
Fig. 3 is server engine workflow diagram in the embodiment of the present invention;
Fig. 4 is the workflow diagram of host process in the embodiment of the present invention;
Fig. 5 is the workflow diagram of single work subprocess in the embodiment of the present invention.
Detailed description of the invention
Below in conjunction with accompanying drawing embodiment, the present invention is described in further detail.
The application server based on Node.js as shown in Figure 1, runs application service system, application data resource and external application servers including Node.js;Wherein Node.js operation application service system includes application server engine, locally applied container and applications container;Aforementioned applications server engine includes host process and carries the subprocess container of some work subprocess, and each work subprocess is all authorized to use http server and application domain manager;Locally applied container carries some locally applied, and locally applied container comprises locally applied interface unit and locally applied manager, and locally applied in locally applied manager is connected with application data resource by locally applied interface unit;Applications container carries some applications, and each applications is made up of applications interface unit, is responsible for interacting with external application servers;
Wherein Node.js runs the application server engine monitoring users service request of application service system, after user sends service request, processes by below scheme:
S101, user initiate service request;
S102, application server engine accept user and service request and carry out following process;
If S103 service request content is locally applied, then it is for further processing, otherwise proceeds to step S107;
S104, the http address information acquisition Apply Names serviced according to user in request, send in locally applied manager corresponding locally applied by service request;
After the locally applied acquisition service request that S105, locally applied manager are corresponding, call application data resource by locally applied interface unit and carry out service request handling;
Result is fed back to application server engine after completing service request handling by S106, locally applied manager corresponding locally applied;
S107, application server engine service the http address in request according to user and obtain Apply Names, and service request signal is sent into applications corresponding in applications container;
Service request signal is forwarded to external application servers by applications interface unit by S108, applications;
Result is fed back to application server engine by applications container by S109, external application servers;
Result is fed back to user by S110, application server engine, it is achieved user responds.
Application server engine carries out user's service request handling and depends on http server and application domain manager, and subprocess container has several work subprocess, each work subprocess has http server and the right to use of application domain manager, and the concrete work process of application server engine comprises the steps:
S201, application server engine start, initially enter duty;
S202, application server engine create http server;
S203, application server engine create application domain manager;
S204, application server engine read the configuration file of service request, obtain the work subprocess quantity N servicing request in configuration file;
S205, parameters optimization N: first determining whether that whether N is less than 1, in this way, just N assignment is 1;As no, just N assignment is CPU quantity;
S206, establishment service processes manager;
S207, startup host process;
S208, starting N number of work subprocess and enter S209 and continue executing with in subprocess container, each work subprocess proceeds to step S211 process;
S209, host process monitoring work subprocess state also carry application domain manager, carry out application domain management;
If S210 occurs that work subprocess i lost efficacy, then restart work subprocess i, proceed to step S209;
After N number of work subprocess in S211 subprocess container starts, each work subprocess obtains the right to use of http server and application domain manager;
N number of work subprocess in S212, subprocess container enters idle condition, monitors HTTP request;
If S213 user initiates HTTP service request, from subprocess container, choose vacant working subprocess j;
S214, work subprocess j complete HTTP service request and process and proceed to step S212, transfer idle condition to and continue monitoring service request.
Node.js runs application service system and realizes user by application domain manager and service the distribution of request and distribute, and then realizing the application server support function to multiple application: application management is responsible for by application domain manager, address information in asking according to user determines that the application belonged to is asked in this service, thus making requests on the distribution of message and distributing, then processed respectively by each self-application;Wherein the host process workflow of application server engine is:
S301, host process start;
S302, host process startup work subprocess, work subprocess obtains application domain manager;
The application in locally applied container and applications container retrieved by S303, application domain manager;
List of application set up by S304, application domain manager, and all application are sent into list of application;
S305, host process monitoring work subprocess state also carry out application domain management;
If a certain application exception occurs S306, then proceed to step S309;
If S307 occurs work subprocess to lose efficacy, enter next step;
S308, host process restart inefficacy work subprocess;
The application of this exception deleted by S309, application domain manager, and proceeds to next step;
If S310 occurs newly-increased or deletes application, adjust list of application, and proceed to step S304.
Work subprocess in subprocess container is responsible for that user services request and is distributed concrete application, and its specific works flow process is as follows:
S401, progress of work i start;
S402, progress of work i obtain the http server right to use;
S403, progress of work i obtain the application domain manager right to use;
S404, progress of work i enter idle process queue, wait in line user and service request;
S405, user send HTTP request;
S406, progress of work i dequeue, obtain user's request;
S407, progress of work i read the Apply Names of user's request from http address;
Request is sent into the application that request is corresponding by the application domain manager in S408, progress of work i;
S409, apply request and processed and http server that result is back in progress of work i, and then realize the response of user's request: if this applies with basing on practicality, then locally applied container is sent in request, processed by locally applied container again, obtain application data resource, and then complete user's response;If this application is applications, then by request send into applications container, by applications container transfer external application servers carry out user ask response, return response results;
Multiple work subprocess in subprocess container can be simultaneously different accordingly user service request.

Claims (3)

1. the application server based on Node.js, it is characterised in that: including: Node.js runs application service system, application data resource and external application servers;Wherein Node.js operation application service system includes application server engine, locally applied container and applications container;Aforementioned applications server engine includes host process and carries the subprocess container of some work subprocess, and each work subprocess is all authorized to use http server and application domain manager;Locally applied container carries some locally applied, and locally applied container comprises locally applied interface unit and locally applied manager, and locally applied in locally applied manager is connected with application data resource by locally applied interface unit;Applications container carries some applications, and each applications is made up of applications interface unit, is responsible for mutual with external application servers;
Wherein Node.js runs the application server engine monitoring users service request of application service system, after user sends service request, processes by below scheme:
S101, user initiate service request;
S102, application server engine accept user and service request and carry out following process;
If S103 service request content is locally applied, then it is for further processing, otherwise proceeds to step S107;
S104, the http address information acquisition Apply Names serviced according to user in request, send in locally applied manager corresponding locally applied by service request;
After the locally applied acquisition service request that S105, locally applied manager are corresponding, call application data resource by locally applied interface unit and carry out service request handling;
Result is fed back to application server engine after completing service request handling by S106, locally applied manager corresponding locally applied;
S107, application server engine service the http address in request according to user and obtain Apply Names, and service request signal is sent into applications corresponding in applications container;
Service request signal is forwarded to external application servers by applications interface unit by S108, applications;
Result is fed back to application server engine by applications container by S109, external application servers;
Result is fed back to user by S110, application server engine, it is achieved user responds.
2. application server according to claim 1, it is characterized in that: application server engine carries out user's service request handling and depends on http server and application domain manager, and subprocess container has several work subprocess, each work subprocess has http server and the right to use of application domain manager, and the concrete work process of application server engine comprises the steps:
S201, application server engine start, initially enter duty;
S202, application server engine create http server;
S203, application server engine create application domain manager;
S204, application server engine read the configuration file of service request, obtain the work subprocess quantity N servicing request in configuration file;
S205, parameters optimization N: first determining whether that whether N is less than 1, in this way, just N assignment is 1;As no, just N assignment is CPU quantity;
S206, establishment service processes manager;
S207, startup host process;
S208, starting N number of work subprocess and enter S209 and continue executing with in subprocess container, each work subprocess proceeds to step S211 process;
S209, host process monitoring work subprocess state also carry application domain manager, carry out application domain management;
If S210 occurs that work subprocess i lost efficacy, then restart work subprocess i, proceed to step S209;
After N number of work subprocess in S211 subprocess container starts, each work subprocess obtains the right to use of http server and application domain manager;
N number of work subprocess in S212, subprocess container enters idle condition, monitors HTTP request;
If S213 user initiates HTTP service request, from subprocess container, choose vacant working subprocess j;
S214, work subprocess j complete HTTP service request and process and proceed to step S212, transfer idle condition to and continue monitoring service request.
3. application server according to claim 2, it is characterised in that: Node.js runs application service system and realizes user by application domain manager and service the distribution of request and distribute, and then realizes the application server engine support function to multiple application:;Wherein the host process workflow of application server engine is:
S301, host process start;
S302, host process startup work subprocess, work subprocess obtains application domain manager;
The application in locally applied container and applications container retrieved by S303, application domain manager;
List of application set up by S304, application domain manager, and all application are sent into list of application;
S305, host process monitoring work subprocess state also carry out application domain management;
If a certain application exception occurs S306, then proceed to step S309;
If S307 occurs work subprocess to lose efficacy, enter next step;
S308, host process restart inefficacy work subprocess;
S309, application domain manager retrieve locally applied container and applications container, reload this application, and proceed to next step;
If S310 occurs newly-increased or deletes application, adjust list of application, and proceed to step S304.
Work subprocess in subprocess container is responsible for that user services request and is distributed concrete application, and its specific works flow process is as follows:
S401, work subprocess i start;
S402, work subprocess i obtain the http server right to use;
S403, work subprocess i obtain the application domain manager right to use;
S404, work subprocess i enter idle process queue, wait in line user and service request;
S405, user send HTTP request;
S406, work subprocess i dequeue, obtain user's request;
S407, work subprocess i read the Apply Names of user's request from http address;
Request is sent into the application that request is corresponding by the application domain manager in S408, work subprocess i;
S409, applied request process and result is back to the http server in work subprocess i, and then realize the response of user's request: if this applies with basing on practicality, then locally applied container is sent in request, processed by locally applied container again, obtain application data resource, and then complete user's response;If this application is applications, then by request send into applications container, by applications container transfer external application servers carry out user ask response, return response results;
Multiple work subprocess in subprocess container can be simultaneously different accordingly user service request.
CN201610124561.1A 2016-03-04 2016-03-04 A kind of application server based on Node.js Active CN105791295B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201610124561.1A CN105791295B (en) 2016-03-04 2016-03-04 A kind of application server based on Node.js

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201610124561.1A CN105791295B (en) 2016-03-04 2016-03-04 A kind of application server based on Node.js

Publications (2)

Publication Number Publication Date
CN105791295A true CN105791295A (en) 2016-07-20
CN105791295B CN105791295B (en) 2019-01-11

Family

ID=56387057

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201610124561.1A Active CN105791295B (en) 2016-03-04 2016-03-04 A kind of application server based on Node.js

Country Status (1)

Country Link
CN (1) CN105791295B (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107070870A (en) * 2017-01-09 2017-08-18 阿里巴巴集团控股有限公司 A kind of data capture method and device
CN107783804A (en) * 2016-08-30 2018-03-09 平安科技(深圳)有限公司 The call method and terminal of a kind of programmable interface
CN113010237A (en) * 2021-03-23 2021-06-22 税友软件集团股份有限公司 Data interaction method, system, electronic equipment and storage medium

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070038683A1 (en) * 2005-08-04 2007-02-15 Pentaho Corporation Business intelligence system and methods
US20130091197A1 (en) * 2011-10-11 2013-04-11 Microsoft Corporation Mobile device as a local server
CN104935619A (en) * 2014-03-20 2015-09-23 上海宝信软件股份有限公司 Middleware-based network service method
US20150281035A1 (en) * 2014-03-30 2015-10-01 AppDynamics, Inc. Monitoring of Node.JS Applications

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070038683A1 (en) * 2005-08-04 2007-02-15 Pentaho Corporation Business intelligence system and methods
US20130091197A1 (en) * 2011-10-11 2013-04-11 Microsoft Corporation Mobile device as a local server
CN104935619A (en) * 2014-03-20 2015-09-23 上海宝信软件股份有限公司 Middleware-based network service method
US20150281035A1 (en) * 2014-03-30 2015-10-01 AppDynamics, Inc. Monitoring of Node.JS Applications

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
陈瑶: "基于Node.js高并发web系统的研究与应用", 《万方学位论文全文数据库》 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107783804A (en) * 2016-08-30 2018-03-09 平安科技(深圳)有限公司 The call method and terminal of a kind of programmable interface
CN107783804B (en) * 2016-08-30 2020-09-11 平安科技(深圳)有限公司 Calling method and terminal of programmable interface
CN107070870A (en) * 2017-01-09 2017-08-18 阿里巴巴集团控股有限公司 A kind of data capture method and device
CN107070870B (en) * 2017-01-09 2020-04-14 阿里巴巴集团控股有限公司 Data acquisition method and device
CN113010237A (en) * 2021-03-23 2021-06-22 税友软件集团股份有限公司 Data interaction method, system, electronic equipment and storage medium

Also Published As

Publication number Publication date
CN105791295B (en) 2019-01-11

Similar Documents

Publication Publication Date Title
CN108737468B (en) Cloud platform service cluster, construction method and device
CN110413386B (en) Multi-process processing method, device, terminal equipment and computer readable storage medium
US9378070B2 (en) Generic distributed processing unit for multi-agent systems
CN105979009A (en) Method for automatically balancing increased load of cloud application container
CN108376079B (en) Automatic application updates
US8806488B2 (en) System for managing personalization information of virtual machine based on cloud computing and method thereof
JP6364160B2 (en) Menu control method, menu control apparatus, and menu control program
CN110943934A (en) Service request processing method, system, terminal and readable storage medium
CN105791295A (en) Application server based on Node.js
CN110633130A (en) Virtual memory management method and device based on memory hot plug technology
CN113206866B (en) Service providing method, device and storage medium in multi-region scene
CN110365743B (en) Zookeeper-based implementation method of load balancer supporting multiple customizable load algorithms
CN113162802A (en) Communication method, equipment and storage medium based on InfiniBand
CN109525443B (en) processing method and device for distributed pre-acquisition communication link and computer equipment
US9519527B1 (en) System and method for performing internal system interface-based communications in management controller
CN116719647A (en) Super-computing cluster management method and device, arrangement management equipment and super-computing cluster
JP2010218151A (en) Virtual computer management mechanism and cpu time allocation control method in virtual computer system
CN108696550B (en) System and method for quickly building and replicating clouds
KR20130028554A (en) Large capacity distributed processing apparatus using a message bus and the method thereof
CN113596105B (en) Content acquisition method, edge node and computer readable storage medium
CN115567594A (en) Microservice request processing method, microservice request processing device, computer equipment and storage medium
Feraudo et al. A Novel OMNeT++-based Simulation Tool for Vehicular Cloud Computing in ETSI MEC-compliant 5G Environments
CN113271229B (en) Equipment control method and device, storage equipment, safety equipment, switch, router and server
KR100227795B1 (en) Method of sourcing application server on the web
CN111414200B (en) Method, apparatus, electronic device and computer readable medium for installing operating system

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant