--- title: Compatibility description: Platform compatibility, and features available in different SDK versions, and compatibility between Enterprise Analytics and the SDK. pubDate: 2026-08-17T09:53:44.266Z antora: editUrl: https://github.com/couchbase/docs-analytics-sdk-go/edit/release/1.1/modules/project-docs/pages/compatibility.adoc xref: xref:go-analytics-sdk:project-docs:compatibility.adoc[] --- [Consult the llms.txt file for a full list of contents](/llms.txt) [View original HTML](/go-analytics-sdk/current/project-docs/compatibility.html) # Compatibility > Platform compatibility, and features available in different SDK versions, and compatibility between Enterprise Analytics and the SDK. In line with the [Golang project](https://golang.org/doc/devel/release.html#policy), Go Analytics SDK supports both the current, and the previous, versions of Go. Earlier versions may work, but are not supported. ## [](#platform-compatibility)Platform Compatibility ### [](#os-compatibility)OS Compatibility In general, the JVM eliminates concerns about underlying OS compatibility, and Couchbase JVM SDKs can be expected to run on all of the Operating Systems supported by [Couchbase Server](../../../server/current/install/install-platforms.md). The Go Analytics SDK has been tested on a representative subset of the platforms listed below. ### GNU/Linux * Amazon Linux 2 & AL2023. * Red Hat Enterprise Linux 8, 9, & 10. * Oracle Linux 8, 9, & 10. * Ubuntu (LTS) 22.04 (_Jammy_) & 24.04 (_Noble_). * Debian 11 (_Bullseye_), Debian 12 (_Bookworm_), & Debian 13 (_Trixie_). * SUSE Enterprise Linux 12 & 15. * Alpine Linux 3.21 - 3.23. ### Microsoft Windows * Microsoft Windows 10 & 11; * Windows Server 2019, 2022, & 2025. ### Mac OS X The current and previous two releases of OS X. At time of writing (June 2026): 26 (Tahoe), 15 (Sequoia), and 14 (Sonoma). The JVM Analytics SDKs should also be expected to run on other commonly-available GNU/Linux distributions which support an appropriate JDK, but not all combinations can be tested. ### [](#network-requirements)Network Requirements Couchbase Analytics SDKs are developed to be run in an environment with local area network (LAN) like throughput and latencies. While there is no technical issue that prevents the use across a wide area network (WAN), SDKs have certain thresholds around timeouts and behaviors to recover that will not be the same once the higher latency and possible bandwidth constraints and congestion of a WAN is introduced. Couchbase tests for correctness under LAN like conditions. For this reason, only LAN-like network environments are officially supported. Couchbase does document, for purposes of convenience when developing and performing basic operational work, what may need to be tuned when network throughputs and latencies are higher. If you encounter issues, even with these tunables, you should attempt the same workload from a supported, LAN-like environment. ## [](#enterprise-analytics-compatibility)Enterprise Analytics Compatibility The 1.1 releases of the Analytics SDK are fully compatible with all currently supported releases of Enterprise Analytics. The 1.1 Go SDK also supports the poll-based Server Asynchronous Request API introduced in self-managed Enterprise Analytics Server 2.2. ### [](#api-version)API Version __Analytics SDK API Versions__ | | API 1.0 | API 1.1 | | ------------------------------------------------------------------------------------------- | ------- | ------- | | [.NET Analytics SDK Docs](../../../dotnet-analytics-sdk/current/hello-world/overview.md) | 1.0 | 1.1 | | [Go Analytics SDK Docs](../hello-world/overview.md) | 1.0 | 1.1 | | [Java Analytics SDK Docs](../../../java-analytics-sdk/current/hello-world/overview.md) | 1.0 | 1.1 | | [Node.js Analytics SDK Docs](../../../nodejs-analytics-sdk/current/hello-world/overview.md) | 1.0 | 1.1 | | [Python Analytcis SDK Docs](../../../python-analytics-sdk/current/hello-world/overview.md) | 1.0 | 1.1 | ## [](#sdk-api-stability)SDK API Stability ### [](#interface-stability)Interface Stability Couchbase SDKs indicate the stability of an API through documentation. Since there are different meanings when developers mention stability, we mean **interface stability**: how likely the interface is to change or be removed entirely. A stable interface is one that is guaranteed not to change between versions, meaning that you may use an API of a given SDK version and be assured that the given API will retain the same parameters and behavior in subsequent versions. An unstable interface is one which may appear to work or behave in a specific way within a given SDK version, but may change in its behavior or arguments in future SDK versions, causing odd application behavior or compiler/API usage errors. **Implementation stability** is implied to be more reliable at higher levels, but all are tested to the level that is appropriate for their stability. Couchbase uses three interface stability classifiers. You may find these classifiers appended as annotations or comments within documentation for each API: * **Committed**: This stability level is used to indicate the most stable interfaces that are guaranteed to be supported and remain stable between SDK versions. This is the default — unless otherwise stated in the documentation, each API has **Committed** status. * **Uncommitted**: This level is used to indicate APIs that are _unlikely_ to change, but _may_ still change as final consensus on their behavior has not yet been reached. _Uncommitted_ APIs usually end up becoming stable APIs. * **Volatile**: This level is used to indicate experimental APIs that are still in flux and may likely be changed. It may also be used to indicate inherently private APIs that may be exposed, but "YMMV" (your mileage may vary) principles apply. _Volatile_ APIs typically end up being promoted to _Uncommitted_ after undergoing some modifications. APIs that are marked as _Committed_ have a stable implementation. _Uncommitted_ and _Volatile_ APIs should be stable within the bounds of any known and often documented issues, but Couchbase has not made a commitment to these APIs and may not respond to reported defects with the same priority. Additionally, take note of the following interface labels: * **Deprecated**: Any API marked deprecated may be removed in the next major version released. Couchbase recommends migrating from the deprecated API to the replacement as soon as possible. In rare instances, deprecated API may be rendered non-functional in a dot-minor release when the API cannot continue to be supported. * **Internal**: This level is used to indicate you should not rely on this API as it is not intended for use outside the module, even to other Couchbase components.