pomelo源碼分析（六）

原創 youyudehexie 2020-02-21 14:26 
Server.prototype.start = function(cb) {  
    registerDefaultModules(this.app);   //註冊默認模塊  
    loadModules(this.app, this.masterConsole); //執行模塊  
  
    var self = this;  
    this.masterConsole.start(function(err) {  
        if(err) {  
            cb(err);  
            return;  
        }  
        starter.runServers(self.app);  
        cb();  
    });  
      
    this.masterConsole.on('register', function(record) {  
        logger.debug('[master] new register connection: %j, %j', record.id, record.type);  
        self.registered[record.id] = record;  
        if(checkRegistered(self)) {  
            logger.info('[master] all servers have started and notify after start now...');  
            self.masterConsole.agent.notifyAll(AfterStart.moduleId);  
        }  
    });  
  
    this.masterConsole.on('disconnect', function(id, type, reason) {  
        crashLogger.info(util.format('[%s],[%s],[%s],[%s]', type, id, Date.now(), reason || 'disconnect'));  
    });  
};

接上一章

	this.masterConsole.on('register', function(record) {
		logger.debug('[master] new register connection: %j, %j', record.id, record.type);
		self.registered[record.id] = record;
		if(checkRegistered(self)) {
			logger.info('[master] all servers have started and notify after start now...');
			self.masterConsole.agent.notifyAll(AfterStart.moduleId);
		}
	});

	this.masterConsole.on('disconnect', function(id, type, reason) {
		crashLogger.info(util.format('[%s],[%s],[%s],[%s]', type, id, Date.now(), reason || 'disconnect'));
	});

通過masterConsole，調用consoleService，consoleService調用masterAgent監聽register事件，監聽的具體函數如下

/**
 * master listen to a port and handle register and request
 *
 * @param {String} port
 * @api public
 */
MasterAgent.prototype.listen = function(port) {
	if(this.state > ST_INITED) {
		logger.error('master agent has started or closed.');
		return;
	}
	this.state = ST_STARTED;
	this.server = sio.listen(port); //io.socket 監聽port
	this.server.set('log level', 0);
	
	var self = this;
	this.server.server.on('error', function(err) {
		self.emit('error', err);  //對MasterAgent 發送事件信息
	});

	this.server.sockets.on('connection', function(socket) {
		var id, type, registered;

		socket.on('register', function(msg) {
			// register a new connection
			if(msg && msg.type) {
				if(msg.type === 'client') {
					// client connection not join the map
					if(!msg.id) {
						// client should has a client id
						return;
					}
					if(self.clients[msg.id]) {
						socket.emit('register', {code: protocol.PRO_FAIL, msg: 'id has been registered. id:' + msg.id});
						return;
					}
					addConnection(self, msg.id, msg.type, msg.pid, socket);
					id = msg.id;
					type = msg.type;
					registered = true;
					socket.emit('register', {code: protocol.PRO_OK, msg: 'ok'});
					return;
				}

				if(msg.id) {
					// if is a normal server
					if(self.idMap[msg.id]) {
						socket.emit('register', {code: protocol.PRO_FAIL, msg: 'id has been registered. id:' + msg.id});
						return;
					}
					var record = addConnection(self, msg.id, msg.type, msg.pid, socket);
					id = msg.id;
					type = msg.type;
					registered = true;
					socket.emit('register', {code: protocol.PRO_OK, msg: 'ok'});
					self.emit('register', record); 
				}
			}
		});		// end of on 'register'

		// message from monitor
		socket.on('monitor', function(msg) {
			if(!registered) {
				// not register yet, ignore any message
				return;
			}

			if(type === TYPE_CLIENT) {
				logger.error('invalid message to monitor, but current connect type is client.');
				return;
			}

			msg = protocol.parse(msg);
			if(msg.respId) {
				// a response from monitor
				var cb = self.callbacks[msg.respId];
				if(!cb) {
					logger.warn('unknown resp id:' + msg.respId);
					return;
				}
				delete self.callbacks[msg.respId];
				utils.invokeCallback(cb, msg.error, msg.body);
				return;
			}

			// a request or a notify from monitor
			self.consoleService.execute(msg.moduleId, 'masterHandler', msg.body, function(err, res) {
				if(protocol.isRequest(msg)) {
					var resp = protocol.composeResponse(msg, err, res);
					if(resp) {
						socket.emit('monitor', resp);
					}
				} else {
					//notify should not have a callback
					logger.warn('notify should not have a callback.');
				}
			});
		});		// end of on 'monitor'

		// message from client
		socket.on('client', function(msg) {
			if(!registered) {
				// not register yet, ignore any message
				return;
			}
			if(type !== TYPE_CLIENT) {
				logger.error('invalid message to client, but current connect type is ' + type);
				return;
			}
			msg = protocol.parse(msg);
			// a request or a notify from client 
			// and client should not have any response to master for master would not request anything from client
			self.consoleService.execute(msg.moduleId, 'clientHandler', msg.body, function(err, res) {
				if(protocol.isRequest(msg)) {
					var resp = protocol.composeResponse(msg, err, res);
					if(resp) {
						socket.emit('client', resp);
					}
				} else {
					//notify should not have a callback
					logger.warn('notify should not have a callback.');
				}
			});
		});		// end of on 'client'

		socket.on('disconnect', function() {
			removeConnection(self, id, type);
			self.emit('disconnect', id, type);
		});

		socket.on('error', function(err) {
			self.emit('error', id, type, err);
		});
	});		// end of on 'connection'
};		// end of listen

masterAgent 和 monitorAgent主要任務就是負責監聽端口傳入的各種事件，下圖是截取http://golanger.cn的圖，圖裏面畫對次過程描述得非常清晰


master 捕捉 'register‘事件，等待MasterAgent發出'register’事件信號的時候，執行以下代碼

    this.masterConsole.on('register', function(record) {  
        logger.debug('[master] new register connection: %j, %j', record.id, record.type);  
        self.registered[record.id] = record;  
        if(checkRegistered(self)) {  
            logger.info('[master] all servers have started and notify after start now...');  
            self.masterConsole.agent.notifyAll(AfterStart.moduleId);  
        }  
    });

執行 self.masterConsole.agent.notifyAll(AfterStart.moduleId);

通知所有模塊都執行AftersStart,通知所有模塊都執行afterstart，到這裏爲止，pomelo的啓動流程基本結束

我們看看官方是怎麼定義這一些列的啓動過程


組件可以根據需要，提供不同的生命週期接口，pomelo框架會在生命週期的各個階段觸發相應的回調。組件的生命週期接口類型如下：

  • start(cb) 服務器啓動回調。在當前服務器啓動過程中，會按註冊順序觸發各組件的這個接口。組件啓動完畢後，需要調用cb函數通知框架執行後續流程。
  • afterStart(cb) 服務器啓動完畢回調。當pomelo管理下的所有服務器進程都啓動完成後會觸發這個接口。一些需要等待全局就緒的工作可以放到這裏來完成。
  • stop(force, cb) 服務器關閉回調。在服務器關閉期間，會根據註冊順序的逆序來觸發這個回調接口，主要用來通知各個組件保存各自的數據和釋放資源。force表示是否要強制關閉。操作完畢後，同樣需要調用cb函數來繼續後續流程。

最後，截取我的啓動日誌作爲文章的結尾

"C:\Program Files\nodejs\node.exe" chatofpomelo\game-server\app.js
[2013-03-23 11:47:43.609] [INFO] \chatofpomelo\game-server\node_modules\pomelo\lib\application.js - app.init invoked   #啓動mater 第一個服務器
[2013-03-23 11:47:43.982] [INFO] \chatofpomelo\game-server\node_modules\pomelo\lib\application.js - application inited: "master-server-1"
[2013-03-23 11:47:45.075] [INFO] console - info: 'socket.io started'
[2013-03-23 11:47:45.076] [INFO] \chatofpomelo\game-server\node_modules\pomelo\lib\master\starter.js - Executing cd #通過mater裏面，runServer命令啓動採用cmd命令的方式啓動多個相關服務器組
 D:\src\pomelo\chatofpomelo\game-server && node  D:\src\pomelo\chatofpomelo\game-server\app.js env=development serverType=connector serverId=connector-server-1 locally
[2013-03-23 11:47:45.221] [INFO] \chatofpomelo\game-server\node_modules\pomelo\lib\master\starter.js - Executing cd D:\src\pomelo\chatofpomelo\game-server && node  D:\src\pomelo\chatofpomelo\game-server\app.js env=development serverType=connector serverId=connector-server-2 locally
[2013-03-23 11:47:45.239] [INFO] \chatofpomelo\game-server\node_modules\pomelo\lib\master\starter.js - Executing cd D:\src\pomelo\chatofpomelo\game-server && node  D:\src\pomelo\chatofpomelo\game-server\app.js env=development serverType=connector serverId=connector-server-3 locally
[2013-03-23 11:47:45.397] [INFO] \chatofpomelo\game-server\node_modules\pomelo\lib\master\starter.js - Executing cd D:\src\pomelo\chatofpomelo\game-server && node  D:\src\pomelo\chatofpomelo\game-server\app.js env=development serverType=chat serverId=chat-server-1 locally
[2013-03-23 11:47:45.468] [INFO] \chatofpomelo\game-server\node_modules\pomelo\lib\master\starter.js - Executing cd D:\src\pomelo\chatofpomelo\game-server && node  D:\src\pomelo\chatofpomelo\game-server\app.js env=development serverType=chat serverId=chat-server-2 locally
[2013-03-23 11:47:45.552] [INFO] \chatofpomelo\game-server\node_modules\pomelo\lib\master\starter.js - Executing cd D:\src\pomelo\chatofpomelo\game-server && node  D:\src\pomelo\chatofpomelo\game-server\app.js env=development serverType=chat serverId=chat-server-3 locally
[2013-03-23 11:47:45.647] [INFO] \chatofpomelo\game-server\node_modules\pomelo\lib\master\starter.js - Executing cd D:\src\pomelo\chatofpomelo\game-server && node  D:\src\pomelo\chatofpomelo\game-server\app.js env=development serverType=gate serverId=gate-server-1 locally
[2013-03-23 11:47:45.750] [INFO] \chatofpomelo\game-server\node_modules\pomelo\node_modules\pomelo-admin\lib\consoleService.js - try to connect master: "master", "127.0.0.1", 3005
[2013-03-23 11:47:45.970] [INFO] console - [2013-03-23 11:47:45.606] [INFO] \node_modules\pomelo\lib\application.js - app.init invoked #開始執行初始化對應的服務器


[2013-03-23 11:47:45.970] [INFO] console - [2013-03-23 11:47:45.895] [INFO] \node_modules\pomelo\lib\application.js - app.init invoked 


[2013-03-23 11:47:46.791] [INFO] console - [2013-03-23 11:47:45.980] [INFO] \node_modules\pomelo\lib\application.js - app.init invoked


[2013-03-23 11:47:46.791] [INFO] console - [2013-03-23 11:47:46.078] [INFO] \node_modules\pomelo\lib\application.js - app.init invoked


[2013-03-23 11:47:46.792] [INFO] console - [2013-03-23 11:47:46.139] [INFO] \node_modules\pomelo\lib\application.js - app.init invoked


[2013-03-23 11:47:46.792] [INFO] console - [2013-03-23 11:47:46.294] [INFO] \node_modules\pomelo\lib\application.js - app.init invoked


[2013-03-23 11:47:46.792] [INFO] console - [2013-03-23 11:47:46.368] [INFO] \node_modules\pomelo\lib\application.js - app.init invoked


[2013-03-23 11:47:47.116] [DEBUG] \chatofpomelo\game-server\node_modules\pomelo\lib\master\master.js - [master] new register connection: "master-server-1", "master"
[2013-03-23 11:47:47.806] [INFO] console - [2013-03-23 11:47:46.482] [INFO] \node_modules\pomelo\lib\application.js - application inited: "gate-server-1" #初始化成功信息


[2013-03-23 11:47:47.829] [INFO] console - [2013-03-23 11:47:46.274] [INFO] \node_modules\pomelo\lib\application.js - application inited: "chat-server-2"


[2013-03-23 11:47:47.840] [INFO] console - [2013-03-23 11:47:46.225] [INFO] \node_modules\pomelo\lib\application.js - application inited: "chat-server-1"


[2013-03-23 11:47:47.840] [INFO] console - [2013-03-23 11:47:46.074] [INFO] \node_modules\pomelo\lib\application.js - application inited: "connector-server-3"


[2013-03-23 11:47:47.873] [INFO] console - [2013-03-23 11:47:45.678] [INFO] \node_modules\pomelo\lib\application.js - application inited: "connector-server-1"


[2013-03-23 11:47:47.875] [INFO] console - [2013-03-23 11:47:46.420] [INFO] \node_modules\pomelo\lib\application.js - application inited: "chat-server-3"


[2013-03-23 11:47:47.913] [INFO] console - [2013-03-23 11:47:45.994] [INFO] \node_modules\pomelo\lib\application.js - application inited: "connector-server-2"


[2013-03-23 11:47:47.914] [INFO] console - [2013-03-23 11:47:47.911] [INFO] console - info: 'socket.io started' #開始對剛初始化成功的服務器進行端口監聽


[2013-03-23 11:47:48.013] [INFO] console - [2013-03-23 11:47:47.832] [INFO] console - info: 'socket.io started'


[2013-03-23 11:47:48.035] [INFO] console - [2013-03-23 11:47:47.947] [INFO] \node_modules\pomelo\node_modules\pomelo-admin\lib\consoleService.js - try to connect master: "gate", "127.0.0.1", 3005  #monitor監聽端口


[2013-03-23 11:47:48.035] [INFO] console - [2013-03-23 11:47:47.826] [INFO] console - info: 'socket.io started'


[2013-03-23 11:47:48.043] [INFO] console - [2013-03-23 11:47:47.831] [INFO] console - info: 'socket.io started'


[2013-03-23 11:47:48.046] [INFO] console - [2013-03-23 11:47:47.958] [INFO] \node_modules\pomelo\node_modules\pomelo-admin\lib\consoleService.js - try to connect master: "chat", "127.0.0.1", 3005


[2013-03-23 11:47:48.049] [INFO] console - [2013-03-23 11:47:47.866] [INFO] console - info: 'socket.io started'


[2013-03-23 11:47:48.051] [INFO] console - [2013-03-23 11:47:47.962] [INFO] \node_modules\pomelo\node_modules\pomelo-admin\lib\consoleService.js - try to connect master: "connector", "127.0.0.1", 3005


[2013-03-23 11:47:48.060] [INFO] console - [2013-03-23 11:47:47.873] [INFO] console - info: 'socket.io started'


[2013-03-23 11:47:48.102] [INFO] console - [2013-03-23 11:47:48.031] [INFO] \node_modules\pomelo\node_modules\pomelo-admin\lib\consoleService.js - try to connect master: "connector", "127.0.0.1", 3005


[2013-03-23 11:47:48.156] [INFO] console - [2013-03-23 11:47:47.924] [INFO] \node_modules\pomelo\node_modules\pomelo-admin\lib\consoleService.js - try to connect master: "connector", "127.0.0.1", 3005


[2013-03-23 11:47:48.187] [INFO] console - [2013-03-23 11:47:47.957] [INFO] \node_modules\pomelo\node_modules\pomelo-admin\lib\consoleService.js - try to connect master: "chat", "127.0.0.1", 3005


[2013-03-23 11:47:48.195] [DEBUG] \chatofpomelo\game-server\node_modules\pomelo\lib\master\master.js - [master] new register connection: "chat-server-2", "chat"
[2013-03-23 11:47:48.200] [DEBUG] \chatofpomelo\game-server\node_modules\pomelo\lib\master\master.js - [master] new register connection: "gate-server-1", "gate"
[2013-03-23 11:47:48.202] [DEBUG] \chatofpomelo\game-server\node_modules\pomelo\lib\master\master.js - [master] new register connection: "connector-server-3", "connector"
[2013-03-23 11:47:48.231] [DEBUG] \chatofpomelo\game-server\node_modules\pomelo\lib\master\master.js - [master] new register connection: "chat-server-1", "chat"
[2013-03-23 11:47:48.239] [INFO] console - [2013-03-23 11:47:47.969] [INFO] \node_modules\pomelo\node_modules\pomelo-admin\lib\consoleService.js - try to connect master: "chat", "127.0.0.1", 3005


[2013-03-23 11:47:48.242] [DEBUG] \chatofpomelo\game-server\node_modules\pomelo\lib\master\master.js - [master] new register connection: "chat-server-3", "chat" #完成事件監聽註冊
[2013-03-23 11:47:48.259] [DEBUG] \chatofpomelo\game-server\node_modules\pomelo\lib\master\master.js - [master] new register connection: "connector-server-1", "connector"
[2013-03-23 11:47:48.292] [DEBUG] \chatofpomelo\game-server\node_modules\pomelo\lib\master\master.js - [master] new register connection: "connector-server-2", "connector"
[2013-03-23 11:47:48.293] [INFO] \chatofpomelo\game-server\node_modules\pomelo\lib\master\master.js - [master] all servers have started and notify after start now...
[2013-03-23 11:47:48.295] [DEBUG] \chatofpomelo\game-server\node_modules\pomelo\lib\modules\afterStart.js - after start: "master-server-1"
[2013-03-23 11:47:48.295] [INFO] \chatofpomelo\game-server\node_modules\pomelo\lib\modules\afterStart.js - server "master-server-1" started.
[2013-03-23 11:47:48.296] [INFO] console - [2013-03-23 11:47:48.294] [DEBUG] \node_modules\pomelo\lib\modules\afterStart.js - after start: "chat-server-2"
[2013-03-23 11:47:48.295] [INFO] \node_modules\pomelo\lib\modules\afterStart.js - server "chat-server-2" started.


[2013-03-23 11:47:48.301] [INFO] console - [2013-03-23 11:47:48.297] [DEBUG] \node_modules\pomelo\lib\modules\afterStart.js - after start: "gate-server-1" #執行啓動完成後的操作


[2013-03-23 11:47:48.301] [INFO] console - [2013-03-23 11:47:48.296] [DEBUG] \node_modules\pomelo\lib\modules\afterStart.js - after start: "connector-server-3"


[2013-03-23 11:47:48.312] [INFO] console - [2013-03-23 11:47:48.295] [DEBUG] \node_modules\pomelo\lib\modules\afterStart.js - after start: "chat-server-1"


[2013-03-23 11:47:48.312] [INFO] console - [2013-03-23 11:47:48.297] [DEBUG] \node_modules\pomelo\lib\modules\afterStart.js - after start: "connector-server-2"


[2013-03-23 11:47:48.312] [INFO] console - [2013-03-23 11:47:48.304] [INFO] console - info: 'socket.io started'


[2013-03-23 11:47:48.314] [INFO] console - [2013-03-23 11:47:48.305] [DEBUG] \node_modules\pomelo\lib\modules\afterStart.js - after start: "connector-server-1"


[2013-03-23 11:47:48.314] [INFO] console - [2013-03-23 11:47:48.307] [DEBUG] \node_modules\pomelo\lib\modules\afterStart.js - after start: "chat-server-3"


[2013-03-23 11:47:48.315] [INFO] console - [2013-03-23 11:47:48.296] [INFO] \node_modules\pomelo\lib\modules\afterStart.js - server "chat-server-1" started.


[2013-03-23 11:47:48.315] [INFO] console - [2013-03-23 11:47:48.304] [INFO] \node_modules\pomelo\lib\modules\afterStart.js - server "connector-server-3" started.


[2013-03-23 11:47:48.315] [INFO] console - [2013-03-23 11:47:48.307] [INFO] \node_modules\pomelo\lib\modules\afterStart.js - server "chat-server-3" started.


[2013-03-23 11:47:48.316] [INFO] console - [2013-03-23 11:47:48.306] [INFO] console - info: 'socket.io started'  #完成afterStart操作後，正式啓動完畢
[2013-03-23 11:47:48.306] [INFO] \node_modules\pomelo\lib\modules\afterStart.js - server "connector-server-2" started.


[2013-03-23 11:47:48.316] [INFO] console - [2013-03-23 11:47:48.313] [INFO] console - info: 'socket.io started'
[2013-03-23 11:47:48.316] [INFO] \node_modules\pomelo\lib\modules\afterStart.js - server "connector-server-1" started.


[2013-03-23 11:47:48.339] [INFO] console - [2013-03-23 11:47:48.338] [INFO] console - info: 'socket.io started'


[2013-03-23 11:47:48.339] [INFO] console - [2013-03-23 11:47:48.339] [INFO] \node_modules\pomelo\lib\modules\afterStart.js - server "gate-server-1" started.




youyudehexie
發佈了112 篇原創文章 · 獲贊 37 · 訪問量 68萬+
私信 關注
發表評論
所有評論
還沒有人評論，想成為第一個評論的人麼? 請在上方評論欄輸入並且點擊發布.
相關文章

界面組件DevExpress中文教程 - 如何在Node.js應用中創建報表？

DevExpress Reporting是.NET Framework下功能完善的報表平臺，它附帶了易於使用的Visual Studio報表設計器和豐富的報表控件集，包括數據透視表、圖表，因此您可以構建無與倫比、信息清晰的報表。 獲取Dev

原創 2024-04-30 11:36:22

前端面試題 - NodeJS能用ES6模塊嗎？CommonJS 和 ES6模塊的區別是什麼？

前端面試題 - NodeJS能用ES6模塊嗎？CommonJS 和 ES6模塊的區別是什麼？ JS能寫前端web，也能寫NodeJS。 Node.js 後端應用由模塊組成，其模塊系統採用 CommonJS 規範，它並不是 JavaScri

原創 2024-04-24 23:51:06

流水線運行出錯排查難？AI 來幫你

“我的企業有幾千條流水線，每次流水線運行出錯，都要投入不少的技術人員進去排查，需要花費不少的時間。” 遇到這種情況，怎麼解決。在 AI 爆火的今天，AI 如何助力 DevOps 效率提升？ 雲效與阿里雲通義大模型合作，推出了流水線智能排查能

原創 2024-04-24 21:12:07

JSON Stream

1. 需求背景 在日常開發中經常會遇到大對象或者大文件處理, 比如在nodejs開發中, 一個算法包可能範圍了一個長度爲好幾萬長度的一個對象, 這個對象使用Restful API不好傳遞, 肯定會把這個處理結果保存爲文件, 然後通過通過文件

原創 2024-04-12 23:17:15

直觀易用的大模型開發框架LangChain，你會了沒？

目前LangChain框架在集團大模型接入手冊中的學習案例有限，爲了讓大家可以快速系統地瞭解LangChain大模型框架並開發，產出此文章。本文章包含了LangChain的簡介、基本組件和可跑的代碼案例（包含Embedding、Com

原創 2024-04-11 11:15:54

利用Node.js實現拉勾數據爬取

引言 拉勾網作爲中國領先的互聯網招聘平臺，彙集了豐富的職位信息，對於求職者和人力資源專業人士來說是一個寶貴的數據源。通過編寫網絡爬蟲程序，我們可以自動化地收集這些信息，爲求職決策和市場研究提供數據支持。Node.js以其非阻塞I/O和事

原創 2024-04-01 23:25:54

AIGC: 5 IT從業者如何使用AI賦能業務?

上圖是一個使用AI生成的圖片， 描述一下這篇文章的背景。 程序員系統學習了OpenAI提供的api接口，並熟練利用提示詞結合業務解決業務問題。 現狀 講一個故事來開始今天的內容。 架構師老李在技術圈裏以其卓越的技術洞察力而著稱。另一邊，C

原創 2024-04-01 12:43:02

運維人少，如何批量管理上百個微服務、上千條流水線？

作者：周靜 隨着微服務和雲原生技術的發展，一個業務系統往往由多個微服務應用組成，多個業務方向涉及幾十上百應用。每個應用研發過程又劃分爲測試、預發、生產多條流水線，也即成百上千條流水線。而一個企業下通常只有 1～2 個運維或架構師負責這些應用

原創 2024-03-21 21:13:40

不同項目要求不同的node版本-- Node 版本管理——NVM

解決問題：我有個舊的vue2的項目使用的事node的版本比較低才能使用，可是現在最新的react要求的node的版本必須是16起。 答：使用Node的管理工具（NVM ），可以自由切換不同的Node.js版本。 nvm （Node Vers

DY-Tao 2024-03-21 21:13:21

實用工具推薦：適用於 TypeScript 網絡爬取的常用爬蟲框架與庫

  隨着互聯網的迅猛發展，網絡爬蟲在信息收集、數據分析等領域扮演着重要角色。而在當前的技術環境下，使用TypeScript編寫網絡爬蟲程序成爲越來越流行的選擇。TypeScript作爲JavaScript的超集，通過類型檢查和麪向對象的特性

原創 2024-03-21 00:24:03

利用axios庫在Node.js中進行代理請求的實踐

前言 隨着互聯網的蓬勃發展，Web應用程序越來越依賴於從外部服務器獲取數據。在這個過程中，我們經常需要通過代理服務器來訪問外部資源。本文將介紹如何充分利用axios庫，在Node.js中進行代理請求的最佳實踐，並通過一個實際案例來展示其

原創 2024-03-07 00:38:46

內含資料下載丨黃東旭：2024 現代應用開發關鍵趨勢——降低成本、簡化架構

作爲一名工程師和創業者，創辦 PingCAP 是我進入創新世界的一次深潛。這段旅程既有令人振奮的發現，也充滿令人生畏的不確定性。作爲這次探險之旅見證的 TiDB ，現在已在全球服務超過 3000 家企業，其中有已經實現了商業成

原創 2024-03-03 22:54:33

更改npm的位置

起因 npm和下載的全局依賴包，默認在C盤，容易裝滿C盤。所以更改npm的位置。 更改npm的位置 設置全局npm。 # 設置npm和下載的全局依賴包位置。 npm config set prefix "D:/Program Files

原創 2023-12-14 22:44:56

哪一個更好？Spring boot還是Node.js

前言 本篇文章有些與衆不同，由於我自己手頭有些關於這個主題的個人經驗，受其啓發寫出此文。雖然SpringBoot和Node.js服務於很不一樣的場景，但是這兩個框架共性驚人。其實每種語言都有不計其數的框架，但僅僅一部分是真正卓越的。如果咱們

原創 2023-10-26 22:45:27

對抗軟件複雜度的戰爭

一、何爲研發效能？ 當我們談研發效能的時候，我們在談些什麼？這個議題被拋出來，有人討論，是因爲存在問題，問題就在於實際的研發效率，已經遠低於預期了。企業初創的時候，一個想法從形成到上線，一個人花兩個小時就完成了，而當企業發展到數千人的時候

原創 2023-10-20 00:22:34