Cloud Spanner is the only enterprise-grade, globally-distributed, and strongly consistent database service built for the cloud specifically to combine the benefits of relational database structure with non-relational horizontal scale. This combination delivers high-performance transactions and strong consistency across rows, regions, and continents with an industry-leading 99.999% availability SLA, no planned downtime, and enterprise-grade security. Cloud Spanner revolutionizes database administration and management and makes application development more efficient.
This repository contains the implementation of the Cloud Spanner C++ client library.
This library supports Cloud Spanner at the Beta quality level. This library should perform well for production workloads and we expect to make minimal API changes. Please note that, as is often the case with C++ libraries, we do not follow semantic versioning in the Cloud C++ client libraries. We make every effort to document backwards-incompatible API changes in the release notes below.
Core Builds
Install Instructions
Build with the latest bazel release
The reference documentation for this client library is available online. Please consult the Cloud Spanner website for general documentation on Cloud Spanner features, APIs, other client libraries, etc.
See CONTRIBUTING.md for details on how to contribute to
this project, including how to build and test your changes as well as how to
properly format your code.
Apache 2.0; see LICENSE for details.
Please note that the Google Cloud C++ client libraries do not follow Semantic Versioning.
GA: Libraries defined at a GA quality level are expected to be stable and any backwards-incompatible changes will be noted in the documentation. Major changes to the API will signaled by changing major version number (e.g. 1.x.y -> 2.0.0).
Beta: Libraries defined at a Beta quality level are expected to be mostly stable and we're working towards their release candidate. We will address issues and requests with a higher priority.
Alpha: Libraries defined at an Alpha quality level are still a work-in-progress and are more likely to get backwards-incompatible updates. Additionally, it's possible for Alpha libraries to get deprecated and deleted before ever being promoted to Beta or GA.