Skip to content
This repository has been archived by the owner on Sep 17, 2024. It is now read-only.

clear/platos-model

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

97 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Plato's Model

A schema-less, multi-tenancy ODM for MongoDB.

Build Status NPM version

Installation

$ npm install platos-model

Usage

Creating a Model

A Model is representative of a set of similar collections (one per tenant). Creating them is easy:

var Platos = require("platos-model");
Platos.connect("database-name");

var Model = Platos.create("Model");

There's no need to define a schema, we're using document storage so you shouldn't box yourself in. Instead, your Model provides a convenient location for housing common methods and operations relevant to your domain logic. Here's an example:

var Customer = Platos.create("Customer");

//All customers receive a default balance of $20
Customer.prototype.balance = 20;

Customer.prototype.spend = function (amount) {
	this.balance -= amount;
};

This Model can then be accessed anywhere from within your package just by referencing platos-model:

var Customer = require("platos-model").Customer;

Instantiating your Model

Following along from the example above, you'll want to create an instance of your Model:

var bob = new Customer({ name: "Bob", email: "bob@example.com" });
bob.spend(5);
//Bob now has a balance of $15

And of course, this is easily saved to MongoDB:

bob.save(function (err, customer) {
	//'err' will contain any errors
	//'customer' will contain the newly saved document => { "name": "Bob", "balance": 15 }
});

Once saved, you can retrieve the document again with the static Model.find() method:

Customer.find({ balance: 15 }, function (err, customers) {
	//'customers' will contain an Array of all customers with a balance of 15
});

If you don't have a reference to an existing Model (which is very likely in large-scale applications), you can update it in-place without finding it.

Customer.update({ name: "Bob" }, { balance: 50 }, callback);

Or alternatively, if you know some of the existing properties, you can create a partial instance and update based on determined keys:

var bob = new Customer({ name: "Bob", balance: 60 });
bob.update([ "name" ], function (err, updateCount) {
	//All customers named "Bob" will have their balance set to 60
	//and all other existing properties will remain the same
});

Multi-tenancy

If you're building a web app, you'll probably have multiple clients running on the same codebase. It's easy to store different clients' data into separate collections with multi-tenancy:

bob.save("tenant", function (err, customer) { });

Likewise, you can easily search tenant-specific collections:

Customer.find("tenant", { name: "Bob" }, function (err, customers) {
	//'customers' will contain an Array of customers named Bob in the 'tenant.Customer' collection.
});

Inheritance

Plato's Model encourages the use of Node's standard functional inheritance pattern:

var Employee = Platos.create("Employee");

Employee.prototype.fire = function () {
	console.log("Oh no!")
};

var Manager = Platos.create("Manager");
util.inherits(Manager, Employee);

var frank = new Manager();
frank.fire();	// > "Oh no!"

This works as expected but as an added bonus, Plato's Model will internally store child classes in the same Mongo collection and handle mapping to your models automatically:

(new Employee()).save();
(new Manager()).save();
(new Employee()).save();

Employee.find(function (employees) {
	//employees = [ Employee, Manager, Employee ];
});

//Coming soon (**not yet implemented**):
Manager.find(function (managers) {
	//managers = [ Manager ];
});

And Much More...

The documentation is lacking at the moment so explore the codebase and look at the tests to get a feeling for what else is possible!

Tests

Run tests using Make or npm:

$ npm test
$ make test-unit
$ make test-integration

Contributing

All contributions are welcome! I'm happy to accept pull requests as long as they conform to the following guidelines:

  • Keep the API clean, we prefer ease-of-use over extra features
  • Don't break the build and add tests where necessary
  • Keep the coding style consistent, we follow JSHint's Coding Style

Otherwise, please open an issue if you have any suggestions or find a bug.

License

The MIT License (MIT) - Copyright (c) 2013 Clear Learning Systems

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Packages

No packages published