When comparing Kinto vs Couchbase, the Slant community recommends Couchbase for most people. In the question“What are the best alternatives to Firebase?” Couchbase is ranked 4th while Kinto is ranked 11th. The most important reason people chose Couchbase is:
Couchbase and Couchbase Mobile are open source and released under the Apache License.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Open Source
Kinto is released under Apache v2, which is one of the most flexible licenses.
Pro Good for sensitive data
Since Kinto is a self-hosted solution, it can be used to store sensitive data (emails, financial data etc...) safely, since only the developer has access to the backend.
Pro Fined-grained permissions
Allows to share individual or collection of records for read or write operations.
Pro Push notification support
Pro File attachments on records
Using the kinto-attachment plugin, the server can attach files to records (hosted by server or Amazon S3)
Pro Backed by Mozilla
Mozilla uses it in production to synchronize security settings for Firefox. This means that the product should have adequate support for an extended period of time due to Mozillas use of it.
Pro Open source
Couchbase and Couchbase Mobile are open source and released under the Apache License.
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 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.
Cons
Con No hosted version
In order to use kinto you have to download it and host it on your own server infrastructure. While it does help you avoid outsourcing your data to a third-party, it also adds the overhead of having to maintain a backend for your app.
Con Not as usable as Parse
Parse had several SDKs available which made it a breeze to integrate it with any platform that you wanted.
Con Vendor lock-in
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 Not Compatible with couchdb
Since version 2 the sync-protocol is no longer compatible with couchdb. This makes couchbase nearly worthless
