Cagey core
WORK IN PROGRESS
[key-jee]
- abbreviation: (CAGEY) Create A Game Engine Yourself
- adjective: cautious, wary, or shrewd
- adjective: Nicolas Cage-like
Logo created with https://logomakr.com
What is Cagey?
Cagey is a code philosophy that makes the development of stateful game servers in Node.js easy, testable, flexible and
maintainable. It provides a foundation of rules for how things are supposed to connect, and an ecosystem of plugins that
follow this. The whole point of Cagey is to make integration with other technologies obvious and simple, while keeping a
very strict separation of concerns. For more information on these rules that plugins need to follow, please read
[#plugin-development](Plugin development).
Software development (which very much includes framework development) is not a solved problem. And as we move on and try
new concepts, we have to make some very strict decisions. That does not mean we believe these truths to be objective
truths, nor that we won't ever change our minds on these.
There are several layers at which you can observe your server technology. At its very heart, we want as much of our code
as possible to reflect business logic, not framework patterns, or the database we chose, or the network technology,
etc. If we ever want to switch frameworks, databases, loggers, KPI services, etc. this should be as painless as
possible. The fundamental nature of our business logic should not be contaminated by these choices.
Cagey attempts to solve this by keeping concerns separated as follows:
- Cagey Core
- Cagey Plugins
- Concept aware
- Technology unaware
- Enable easy integration and switching of technologies in or out of a project
- Technology integrations
- Made easy by Cagey plugins
- 100% user land code (code can be inspired from documentation and examples that plugins provide)
- As easy to change as any other user land code
Getting started
This installs Cagey core and the most commonly used plugins:
npm install cagey cagey-sessions cagey-peer-network cagey-client-messenger
Examples
See the ./examples folder and the various plugins for examples.
API
Cagey core and Cagey plugins
Many Cagey API emit events. All events may be listened to with async (...) => {}
functions. The execution will only
progress once all their promises have been resolved, and no errors were thrown.
Cagey core
A cagey object provides process lifecycle management features.
factory
const cagey = require('cagey').create();
Creates and returns an instance of the Cagey
class.
async cagey.shutdown()
This emits:
"beforeShutdown" ()
on the cagey."shutdown" ()
on the cagey.
The events being emitted can be used to stop certain subsystems, and close connections.
Please note that this method does not kill the process. Cagey expects you to clean up or unref all I/O handlers, so
that Node.js will gracefully shut down when all work is done. If you really insist on killing the process, you can do
this manually:
cagey.on('shutdown', () => { process.exit(0); });
Plugins
Plugin development
When developing plugins for Cagey, please keep the following rules in mind.
- Plugins are supposed to be technology concepts, not implementations. Integration examples should be documented
alongside your plugin (in an
examples/
folder, in your ReadMe file or in documentation elsewhere). - A plugin solves only a single problem and should not exclude other plugins from being used on the same project.
Having said that, documented integration patterns of the plugin may absolutely depend on other existing plugins.
- Prefix your NPM package name with
cagey-
. - Wherever relevant, try to use the same dependencies for core functionality. This creates a consistent user experience,
And reduces dependency chaos. For example:
- Parsing duration strings into milliseconds: parse-duration
- A well written plugin has:
- Documentation
- Usage examples
- Unit tests
- Static code analysis
- A license that is identical to or compatible with Cagey
License
MIT
Credit
Cagey is developed and maintained by Wizcorp.