Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariOrchestrate vs Redis
When comparing Orchestrate vs Redis, the Slant community recommends Redis for most people. In the question“What are the best databases to use for Node.js applications?” Redis is ranked 4th while Orchestrate is ranked 12th.
Question Ranking
Pros
Pro Effortless/Automatic Scaling
Orchestrate was built for scale. Orchestrate is a full-fledged distributed data system, provided as a multi-tenant service. There is no need to manage finite server resources like disk space, CPU, or memory
Pro Already set up for you
Orchestrate is a Database-as-a-Service, so there is no downloading, installation, or any other administration. It also makes configuration management and deployment easy.
Pro Great Node.js support
Orchestrate.js is a first class client for Node.js applications
Pro Fault Tolerance Baked In
As a DBaaS, Orchestrate manages replicas and sharding across multiple machines. Additionally, daily backups are managed by the company.
Pro Multiple Query types at Low Latencies
No other database provides Full-Text-Search, Time-Series, Graph, and Key/Value APIs. Moreover, as a DBaaS, the queries are pre-optimized for low latencies. Consistently under 10ms for any query.
Pro Redis is written in ANSI C and therefore doesn't have a VM
Pro Good support
Redis has great docs, an active mailing list, and a github community.
Pro Redis uses the BSD license
This means that it is able to be used in a commercial product if one wants.
Pro There are numerous client libraries and frameworks to make redis more powerful
For Node.JS for example you can get something similar to what Parse.com was offering by using Node ORM.
Cons
Con Data are not on your server
Since it's a DBaaS, your data are completely on their server. It cannot be run on your server. Backup is handled by them as well, which may be good or not depending on your needs.
Con Not Open Source
Orchestrate is not an open source solution.
