https://github.com/rotorlab/server-node

Server cluster for JSON changes management allowing real-time data with Redis
https://github.com/rotorlab/server-node

Last synced: about 1 month ago
JSON representation

Server cluster for JSON changes management allowing real-time data with Redis

• Host: GitHub
• URL: https://github.com/rotorlab/server-node
• Owner: rotorlab
• License: apache-2.0
• Created: 2017-06-06T06:32:46.000Z (over 7 years ago)
• Default Branch: master
• Last Pushed: 2018-08-26T12:26:03.000Z (over 6 years ago)
• Last Synced: 2024-11-08T00:23:52.483Z (2 months ago)
• Language: JavaScript
• Homepage:
• Size: 3.42 MB
• Stars: 1
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
[ ![rotorlab/server-node](https://d25lcipzij17d.cloudfront.net/badge.svg?id=js&type=6&v=0.0.4&x2=0)](https://www.npmjs.com/package/rotor-server)



# Rotor Server for Node

Rotor is a communication framework for work with remote objects from different devices. It makes the API development task easier removing all getter/setter requests. Client data changes are replicated in all devices listening the same object.

[1. Redis](https://github.com/rotorlab/server-node/wiki/Redis)

[2. Implementation and start](https://github.com/rotorlab/server-node/wiki/Implementation-and-start)

[3. Paths and models](https://github.com/rotorlab/server-node/wiki/Paths-and-models)

[4. Libraries](https://github.com/rotorlab/server-node/wiki/Libraries)

[5. Configuration](https://github.com/rotorlab/server-node/wiki/Configuration)

[6. Turbine](https://github.com/efraespada/turbine/wiki)

Here you can find all info about how to build a simple API with few lines.

**Rotor philosophy** states that the only needed requests are those that change data on remote database. 

![schema](https://github.com/rotorlab/server-node/raw/develop/images/shema_rotor.png)

Rotor libraries are connected to Rotor and Redis servers. The first one controls object sharing queues, devices waiting for changes and all data edition on remote database. The second gives us Pub/Sub messaging pattern for data changes replication.

When devices make changes in objects, client libraries send generated differences to Rotor server. This differences are applied in the database and replicated on the rest of devices which are listening the same object.

Check [paths page](https://github.com/rotorlab/server-node/wiki/Paths-and-models) for more info.

License

-------

    Copyright 2018 RotorLab Organization

    Licensed under the Apache License, Version 2.0 (the "License");

    you may not use this file except in compliance with the License.

    You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

    Unless required by applicable law or agreed to in writing, software

    distributed under the License is distributed on an "AS IS" BASIS,

    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.

    See the License for the specific language governing permissions and

    limitations under the License.