Sails.js is a classic mvc client-server web application framework, mainly its ruby ββon rails, implemented for node.js + webscockets, so basically everything you need to get it to work with any backend database contributes changes in ORM.
A meteor is a completely different beast, it is a very stubborn real-time web infrastructure in real time, including a client server and a database, since it is very self-confident, it solves many common problems in a real-time application, where you need to implement mechanisms for very fast Update all your clients actions from each other and take care of such things as compensation for delays, resolution of data conflicts and real-time version control of client versions. This is implemented using web sockets, and mongoDB writes records to triggers for data updates, making the meteor somewhat related to mongo.
But you can make orientdb work very well with the meteorite using the new orientIDB liveID request. This is a pubsub implementation for query results and can be used for efficient updates pushed from db through the server directly to the client with very little server overhead. This is far from ready for production and is only currently working on orient db 2.1 rc5.
I used the small meteor demo application as an example https://github.com/imdark/meteor-orientdb-demo
source share