Compatibility
Description — Couchbase Lite framework and Sync Gateway compatibility
Abstract — This content identifies the compatibility of Couchbase Lite on C with Sync Gateway, together with the operating systems upon which it is supported.
Related Content — What’s New | Release Notes | Supported Platforms
Couchbase Lite/Sync Gateway Matrix
The table below summarizes the compatible versions of Couchbase Lite with Sync Gateway.
Sync Gateway Versions ↓ |
Couchbase Lite → |
||||
1.4 [1]] |
2.0 |
2.1 |
2.5 - 2.8 |
3.0.0 |
|
|
|
|
|
|
|
2.0 and 2.1 |
|
|
|
|
|
2.5 to 2.8 |
|
|
|
|
|
2.5 to 2.8 |
|
|
|
|
|
3.0.0 |
|
|
|
|
|
Operating System SDK Support
The table below summarizes the Operating System SDK versions supported by Couchbase Lite.
2.0 |
2.1 |
2.5 |
2.6 |
2.7 |
2.8 |
3.0 |
|
|---|---|---|---|---|---|---|---|
Android |
|||||||
C |
|||||||
iOS |
|||||||
Java |
- |
- |
- |
- |
|||
Javascript |
- |
- |
- |
||||
.NET |
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.