a POJOs based application framework for node.js
fantasyni
Bearcat -- a POJOs based application framework
Bearcat is a POJOs based application framework which provides a lightweight container for writing simple, maintainable node.js. Bearcat provides an infrastructural backbone to manage business objects so that developers can focus on application-level business logic. Bearcat enables you to build applications from "plain old javaScript object"(POJO) and to apply enterprise services non-invasively to POJOs.
- Homepage: http://bearcatnode.github.io/bearcat/
- Mailing list: https://groups.google.com/group/bearcatnode/
- Wiki: https://github.com/bearcatnode/bearcat/wiki/
- Issues: https://github.com/bearcatnode/bearcat/issues/
- Tags: nodejs, POJO, IoC, AOP, consistent configuration
Features
lightweight container
- Dependency injection implementated Inversion of Control (IoC) to manage POJOs
- AOP based declarative middleware services
- Consistent development and configuration
Easy
- Simple meta configuration and POJOs
- Lightweight: high development efficiency based on node.js
- Reuseable: POJOs can be used to any development environment
- Invasive: there's no dependence on a container API
- Modular: you just use only those parts that you need
- One stop shop: no need for a dedicated Singleton or factory for every object etc
Powerful
- Good reference materials: full docs, many examples includes web todo, realtime app
- well-tested: test cases coverage is over 95%
Extensible
- Custom features: you can add custom codes to container
What is POJO ?
POJO is an acronym for Plain Old Java Object, you can refer to POJO wikipedia. It is mostly used in Java Platform which is used to emphasize that a given object is an ordinary Java Object, not a special object.
In Node, what is POJO ?
It must be Plain Old JavaScript Object, which is simple, ordinary, and not anonymous.
To be not anonymous, it must have Constructor function.
So POJO can be like this:
var POJO = function() {
this.props = null;
}
POJO.prototype.method = function() {
}
module.exports = POJO;
Why should we use POJO ?
- POJO is simple, everyone can write it
- POJO makes development consistently, all your codes is POJOs
- POJO makes it friendly to document