When comparing Couchbase vs Para, the Slant community recommends Couchbase for most people. In the question“What are the best self-hosted BaaS (backend-as-a-service) providers?” Couchbase is ranked 3rd while Para is ranked 9th.
Ranked in these QuestionsQuestion Ranking
Pro Easy to implement N1QL queries
Pro Ability to run ad-hoc SQL like queries on realtime big data
Couchbase N1QL allows native SQL processing over JSON data with high performance indexing for low latency queries at scale.
Pro Easy sync protocol to mobile devices
The minimal code needed to pull data down to a device
Pro Available on Windows, Linux & macOS
Pro Open source
Couchbase and Couchbase Mobile are open source and released under the Apache License.
Pro Ability to make predefined fast queries
With Couchbase you can make "Views" of data, which are practically predefined queries which are fetched with an O(1) algorithm.
Pro Full-text search
Powered by Elasticsearch or Lucene.
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.
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.
Con No model mapper for Android
Couchbase does not have a model mapper for Android built-in and out of the box, instead you will have to write your own from scratch.
Con Vendor lock-in
Con Not Compatible with couchdb
Since version 2 the sync-protocol is no longer compatible with couchdb. This makes couchbase nearly worthless
Con No implementation of locking