Couchbase's team writes about its NoSQL database, covering distributed transactions, comparisons with other databases, and microservice patterns.
HN commenters link it for Couchbase's consistency model compared with CockroachDB, Couchbase Lite tutorials, and server release announcements.
It is most likely in the "Additional Use Grant" which is tricky - because this additional use grant is distinct to each product licensed under the BSL. This additional use grant is also not that easy to find, since some licenses display it prominently, and others hide it under some additional legal fineprint[1,2].
From mariadb site:
https://mariadb.com/bsl-faq-adopting/#limits
"Q: What are the usage limitations under BSL?
A: The usage is limited to non-production use, or production use within the limits of the “Additional Use Grant” defined by the vendor using BSL and specific to each BSL product."
[1] obvious Additional Use Grant for Couchbase, included clearly in https://blog.couchbase.com/couchbase-adopts-bsl-license/
[2] it is extremely difficult to find the Additional Use Grant for Mariadb products themselves. For MaxScale, which is their proxy product, it is buried in a file within the source code (which on the surface level might be a good place for it, but it's not very easy to find and I had to go through lots of legal print to get to it) : https://github.com/mariadb-corporation/MaxScale/blob/2.5/LICENSE25.TXT or https://github.com/mariadb-corporation/MaxScale/blob/6.3/LICENSE6.TXT depending on which version you are trying to use, etc.
Not just a local db but an eventually consistent cache of remote whose data can be mutated offline and synced back into remote with some kind of conflict resolution. Examples here: http://offlinefirst.org/sync/
In the context of GraphQL I'm talking about a GraphQL client that has offline caching and supports syncing offline mutations. But I could also use something like pouch+couch: https://blog.couchbase.com/introduction-offline-data-storage-sync-pouchdb-couchbase/
this is a recommended setting even on Oracle [1] [2] and Couchbase [3]
the doc recommends adding "transparent_hugepage=never" to the kernel boot line in the "/etc/grub.conf" file.
[1] http://oracle-base.com/articles/linux/configuring-huge-pages-for-oracle-on-linux-64.php#disabling-transparent-hugepages
[2] https://support.oracle.com/epmos/faces/DocContentDisplay?id=1557478.1
[3] http://blog.couchbase.com/often-overlooked-linux-os-tweaks
Our perf team and our technical marketing team wrote a post about this specific benchmark. Hopefully Datastax will clarify. (I work at Couchbase but wasn't involved in this work.)
My personal opinion is that using a vendor benchmark to choose your data stack is like hiring a bodyguard based on their record in professional wrestling.
http://blog.couchbase.com/leading-nosql-database-vendors-couchbase-mongodb-and-datastax-lock-horns
Saga Pattern.
https://blog.couchbase.com/saga-pattern-implement-business-transactions-using-microservices-part/
https://microservices.io/patterns/data/saga.html
https://developers.redhat.com/blog/2018/10/01/patterns-for-distributed-transactions-within-a-microservices-architecture/
https://www.enterpriseintegrationpatterns.com/patterns/conversation/CompensatingAction.html
https://en.wikipedia.org/wiki/Compensating_transaction
The FAQ [1] tells me that Couchasebase Server 2.0 is open source. But, the link to source tarballs and git repos is conspicuously absent from all the pages i've looked through on couchbase.com/org.
[1]http://blog.couchbase.com/couchbase-server-20-most-common-questions-and-answers