Pomelo is a fast, scalable game server framework for node.js. It provides the basic development framework and many related components, including libraries and tools. Pomelo is also suitable for real-time web applications; its distributed architecture makes pomelo scale better than other real-time web frameworks.
- Homepage: http://pomelo.netease.com/
- Mailing list: https://groups.google.com/group/pomelo
- Documentation: http://github.com/NetEase/pomelo
- Wiki: https://github.com/NetEase/pomelo/wiki/
- Issues: https://github.com/NetEase/pomelo/issues/
- Tags: game, nodejs
- Multiple-player game: mobile, social, web, MMO rpg(middle size)
- Realtime application: chat, message push, etc.
- Distributed (multi-process) architecture, can be easily scale up
- Flexible server extension
- Full performance optimization and test
- Simple API: request, response, broadcast, etc.
- Lightweight: high development efficiency based on node.js
- Convention over configuration: almost zero config
- Many clients support, including javascript, flash, android, iOS, cocos2d-x, C
- Many libraries and tools, including command line tool, admin tool, performance test tool, AI, path finding etc.
- Good reference materials: full docs, many examples and an open-source MMO RPG demo
- Support plugin architecture, easy to add new features through plugins. We also provide many plugins like online status, master high availability.
- Custom features, users can define their own network protocol, custom components very easy.
Fast, scalable, real-time game server development is not an easy job, and a good container or framework can reduce its complexity. Unfortunately, unlike web, finding a game server framework solution is difficult, especially an open source solution. Pomelo fills this gap, providing a full solution for building game server frameworks. Pomelo has the following advantages:
- The architecture is scalable. It uses a multi-process, single thread runtime architecture, which has been proven in the industry and is especially suited to the node.js thread model.
- Easy to use, the development model is quite similar to web, using convention over configuration, with almost zero config. The API is also easy to use.
- The framework is extensible. Based on the node.js micro module principle, the core of pomelo is small. All of the components, libraries and tools are individual npm modules, and anyone can create their own module to extend the framework.
- The reference materials and documentation are quite complete. In addition to the documentation, we also provide an open-source MMO RPG demo (HTML5 client), which is a far better reference material than any book.
With the following references, you can quickly familiarize yourself with the pomelo development process:
- NetEase, Inc. (@NetEase)
- Peter Johnson(@missinglink)
- Aaron Yoshitake
- @D-Deo
- Eduard Gotwig
- Eric Muyser(@stokegames)
- @GeforceLee
- Harold Jiang(@jzsues)
- @ETiV
- kaisatec
- roytan883
- wuxian
- zxc122333
- newebug
- jiangzhuo
- youxiachai
- qiankanglai
- xieren58
- prim
- Akaleth
- pipi32167
- ljhsai
- zhanghaojie
- airandfingers
(The MIT License)
Copyright (c) 2012-2017 NetEase, Inc. and other contributors
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.