Ahead of the opening today of the Couchbase Connect.Online event, Kay Ewbank asked Couchbase about some of its latest products and services.
The answers come from Jeff Morris, VP of Product, Solutions & Customer Marketing at Couchbase.
Q: What can you tell us about support for Couchbase Server 6.6, and plans for multicloud and self-services versions?
A: These are some of the features customers can expect in upcoming versions of Couchbase Cloud. First, Couchbase Cloud has been adding features over the summer, including our turning on the Full Text Search service. And as you know, Couchbase Server 6.6 was shipped in August, and Couchbase Cloud will be upgraded to that version shortly after the Conference. When we do that, it will inherit these latest features.
Q: You’ve some interesting looking SDKs with the addition of the native Scala SDK and the Ruby SDK. Can you tell us more about what these offer, and what has changed with the new Java SDK 3?
A: All of our SDKs are based on an sdk-rfc, moderated and signed off by subject matter experts. These RFCs define the mechanics and semantics on how our API should be built. We’ve got support for 10 languages now: Java, Scala, C, C++, C# (.NET), Python, Go, PHP, Scala and Ruby.
We introduced the Scala SDK in Summer of 2019 and Ruby SDK in Summer of 2020. At a high level both provide APIs for cluster management, data access and index management, error handling and diagnostics, user management, security and compression.
Our Java SDK added distributed, multi-document ACID transactions in Couchbase 6.5, which we feel is the tipping-point feature for customers to see Couchbase as a transactional system of record. Also, the Java SDK 3.0 is written to provide support for Scopes and Collections at large, which is a feature that’s currently available in Couchbase Server as Developer Preview and allows grouping of documents into “table-esque” collections.
Q: What other languages do you plan on supporting via SDKs, and what languages developers would like to see supported?
A: We’re working on a cross platform command line REPL, an object document mapper built for Couchbase and Node.js, and a collection of extensions for the Couchbase .Net SDK designed to simplify working with Couchbase within .Net Core applications..
Another initiative is Linq2Couchbase, the official Language Integrated Query (LINQ) provider for querying Couchbase Server with N1QLusing the Couchbase .NET SDK. We’re also working on Couchbase Rust SDK.
Q;. You’ve introduced a new API for indexing and searching in Go. Why have you introduced Bluge, and how does it differ from Bleve?
A: Bulge is the evolution of Bleve and written by the same developer, who originally wrote Bleve while working for us. He evolved the API into Bluge in order to offer greater portability across databases. Although Bluge is an offshoot of Bleve, Bluge is an independent project from the community.
or email your comment to: email@example.com