Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Kuzzle vs Para, the Slant community recommends Kuzzle for most people. In the question“What are the best self-hosted BaaS (backend-as-a-service) providers?” Kuzzle is ranked 3rd while Para is ranked 11th. The most important reason people chose Kuzzle is:
Supports REST, WebSockets and MQ protocols.
Question Ranking
Pros
Pro Multiprotocol
Supports REST, WebSockets and MQ protocols.
Pro Realtime through filters
You do not connect to classic rooms but to search filters and can be warned of changes on permanent storage or volatile one.
Pro Open Source
Kuzzle is open source and it's released under the Apache 2 License.
Pro Javascript SDK
A fully documented javascript SDK exists.
Pro Full-text search
Powered by Elasticsearch or Lucene.
Pro Modular
Para offers interfaces for persistence, search and caching. Easy to write your own plugins to implement any of these interfaces.
Pro Open source
Licensed under Apache 2.0.
Pro REST API
Exposes a REST API secured by AWS Signature Version 4.
Pro Multi-tenant
Each tenant has its own database table, search index, and cache.
Pro Integrated metrics
Each tenant receives its own complete metrics for all CRUD and REST operations.
Pro Resource permissions with 3rd party security integrations
Object-level permissions with authentication through LDAP and 3rd party providers such as Google, Facebook, etc.
Pro Easy to use
By far the easiest to use BaaS platform.
Cons
Con May have issues since it's stil la relatively young project
Kuzzle is (as of February 2nd, 2015) in alpha version and approaching beta.
Con No implementation of locking
Last-write-wins.
Con No support for Transaction Management
