we are considering to utilize CouchBase Mobile as a reliable messaging layer for connecting edge devices/apps. There are some questions that I couldn’t find the solution in the docs though.
- What is the main use case for the Public REST API of Sync Gateway since moving to a websocket/BLIP-based replication protocol in v2.0? My understanding is that the REST API was modeled after the CouchDB API which used to be the foundation for replication which isn’t the case anymore.
- The webhook documentation states that document changes made through the REST API can trigger events for downstream processing. I assume that this also applies to doc changes made through the new replication protocol. Can anyone confirm this?.
- Under “Running replications”, there seems to be some unclear documentation.
3.1. Assuming we are running two couchbase server clusters (separated by an unreliable network) that need to be synchronized, what is the preferred approach (with pro’s and con’s) ? It seems, both SG_Replicate (between SG instances) or XDCR can be used, but it is not clear when to use what.
3.2. The same page states that replication between two SG instances actually uses the REST API. I was of the impression that everything had been moved to the new replication protocol based on websockets. It seems this is only valid between CouchBase Lite and SG though.
- Regarding Admin vs Public REST API, there seems to be significant overlap. The Admin REST API contains 10 endpoints, 7 of which are also covered by the Public REST API. When to use what ?
Sorry if any of my questions have already been addressed somewhere.
Thanks in advance, Nick