Cloud SQL for MySQL

These terms describe the origin API served by the adapter, not direct calls to the target service. Management-request latency covers accepting and handling the API call; it does not promise that a cloud resource finishes provisioning within that time.

​

Service level agreements

Listed terms cover requests sent through this service adapter. They do not cover direct connections to the target service or replace the cloud provider’s own SLA. Each origin-to-target pair has its own terms or an explicit pending status. See the SLA tables, measurement rules, and scaling conditions.

​

Cloud SQL for MySQL to RDS MySQL

Deployment availability. These targets describe this adapter design. Confirm that your deployment supports the listed operations; a numerical target does not establish runtime availability. What Tensor9 covers. These service levels cover the adapter between the origin API and target API. They do not replace the target provider’s SLA. How latency is counted. Adapter work, including metadata and coordination, counts. Only separately measured permitted target waits are excluded. Which terms apply. Your signed agreement names the covered operations, workload limits, remedies, and final service levels for your deployment.

​

What this adapter does

For aws::1.0.0::rds::mysql, the management adapter translates Cloud SQL instance settings and user changes, while Google’s connector/Auth Proxy handshake requires its own credential path. Applications subsequently speak PostgreSQL or MySQL directly to the selected engine. The 20 ms handshake target is not a promise that an arbitrary SQL query completes in 20 ms, and the 30 ms instance target measures accepted work rather than database startup. These targets describe this adapter design; confirm that your deployment supports the listed operations. A numerical target does not establish runtime availability.

​

How the latency targets were chosen

Cloud SQL instance changes: 30 ms monthly p99. sql.instances.delete, sql.instances.insert, sql.instances.patch. Validate the origin request, retain its resource identity and requested configuration, and construct the target change. Adapter-owned metadata and coordination waits remain included. Database user changes: 20 ms monthly p99. sql.users.delete, sql.users.insert. Bounded configuration validation, durable adapter metadata and response encoding; native provisioning completion and propagation are separate. Connector certificate handshake: 20 ms monthly p99. sql.connect.generateEphemeral. Resolve the target instance, validate the request and issue/map connection credentials. Adapter-owned identity and certificate work remains timed. Your signed agreement sets the terms for your deployment. A target does not add an operation or option that the compatibility tables mark unavailable.

​

What counts toward latency

For a request-response row, measure from the agreed ingress boundary to dispatch of the complete response. A row that explicitly names a first response chunk ends at that chunk; its number does not cover the rest of the stream. A long-poll row names the intentional wait and when adapter delay starts. Include parsing, authorization, admission, translation, serialization, adapter-owned storage and coordination, retries and response handling. Subtract only separately measured target-workload waits and external network segments allowed by the measurement rules. The adapter’s own response handling and dispatch remain covered. A database used for adapter metadata is still adapter work, even if a cloud provider hosts it. For concurrent calls, exclude the union of permitted wait intervals, not the sum of overlapping spans. Calculate each request’s adapter duration first, then the monthly p99. Do not subtract one service’s p99 from another’s. Known adapter timeouts are over-budget samples; failed or incomplete requests cannot disappear to improve the percentile. Missing measurements do not become zero latency. An SDK call span alone does not prove how much of its duration can be excluded.

​

Availability and failures

The 99.9% request target measures correct adapter handling, not the percentage of application calls that return success. Correctly forwarding a target quota or permission error is different from producing that error because the adapter sent the wrong request. Adapter-caused failures count even when the target is healthy. With 1,000,000 eligible calls in a month, a 99.9% target permits at most 1,000 adapter-attributable failures. Endpoint probes have their own denominator. Correctness defects remain actionable even when the monthly availability percentage is met.

​

Scaling and target-service capacity

Scale API handlers and background workers separately. The agreement bounds resource count, concurrent changes, status polling, configuration size and burst growth. More replicas do not remove a shared metadata-store bottleneck or a target API quota. Tensor9 is responsible for adapter capacity within that envelope; the customer supplies target capacity and permissions. Native resource readiness is monitored separately from request acceptance. Connector renewal storms and user changes also consume identity and certificate capacity; agree their concurrency separately from instance polling. Native database connections, CPU, storage and lock contention remain customer-managed target capacity. Tell Tensor9 the expected steady rate, bursts, concurrency, payload sizes and operation mix. Tensor9 sizes and scales the adapter for the agreed load; you choose and monitor the target service’s capacity with Tensor9’s help. A latency budget is not a requests-per-second rating. Larger requests and higher rates need explicit terms, not silent inheritance of a small-request SLA.

​

Data and behavior guarantees

Preserve the selected engine, supported flags and user identity without claiming unavailable extensions or authentication modes. Never acknowledge an invalid certificate or unsupported setting as successfully applied. Creating an instance does not migrate data, users or backup history. Database durability, SQL isolation and native failover duration do not become adapter promises through the control API.

​

Example and diagnosis

Create orders-db, wait for the reported ready state and connect using the actual Google connector library. Measure instance acceptance, connector certificate exchange and the application’s SELECT separately. A fast management response cannot establish successful authentication or prove that required extensions exist on the target. Use tensor9 explain and the documented explain headers to understand the selected adapter and its behavior. Correlate available request diagnostics with the target provider’s latency, throttling and capacity metrics. An explain report helps diagnose a request; it is not by itself a qualified SLA timing measurement. Share the operation, request shape, timestamps and request identifiers with support, with credentials and customer payloads removed.

​

Cloud SQL for MySQL to MySQL Flexible Server

Deployment availability. These targets describe this adapter design. Confirm that your deployment supports the listed operations; a numerical target does not establish runtime availability. What Tensor9 covers. These service levels cover the adapter between the origin API and target API. They do not replace the target provider’s SLA. How latency is counted. Adapter work, including metadata and coordination, counts. Only separately measured permitted target waits are excluded. Which terms apply. Your signed agreement names the covered operations, workload limits, remedies, and final service levels for your deployment.

​

What this adapter does

For azure::1.0.0::mysql::flexible, the management adapter translates Cloud SQL instance settings and user changes, while Google’s connector/Auth Proxy handshake requires its own credential path. Applications subsequently speak PostgreSQL or MySQL directly to the selected engine. The 20 ms handshake target is not a promise that an arbitrary SQL query completes in 20 ms, and the 30 ms instance target measures accepted work rather than database startup. These targets describe this adapter design; confirm that your deployment supports the listed operations. A numerical target does not establish runtime availability.

​

How the latency targets were chosen

Cloud SQL instance changes: 30 ms monthly p99. sql.instances.delete, sql.instances.insert, sql.instances.patch. Validate the origin request, retain its resource identity and requested configuration, and construct the target change. Adapter-owned metadata and coordination waits remain included. Database user changes: 20 ms monthly p99. sql.users.delete, sql.users.insert. Bounded configuration validation, durable adapter metadata and response encoding; native provisioning completion and propagation are separate. Connector certificate handshake: 20 ms monthly p99. sql.connect.generateEphemeral. Resolve the target instance, validate the request and issue/map connection credentials. Adapter-owned identity and certificate work remains timed. Your signed agreement sets the terms for your deployment. A target does not add an operation or option that the compatibility tables mark unavailable.

​

What counts toward latency

For a request-response row, measure from the agreed ingress boundary to dispatch of the complete response. A row that explicitly names a first response chunk ends at that chunk; its number does not cover the rest of the stream. A long-poll row names the intentional wait and when adapter delay starts. Include parsing, authorization, admission, translation, serialization, adapter-owned storage and coordination, retries and response handling. Subtract only separately measured target-workload waits and external network segments allowed by the measurement rules. The adapter’s own response handling and dispatch remain covered. A database used for adapter metadata is still adapter work, even if a cloud provider hosts it. For concurrent calls, exclude the union of permitted wait intervals, not the sum of overlapping spans. Calculate each request’s adapter duration first, then the monthly p99. Do not subtract one service’s p99 from another’s. Known adapter timeouts are over-budget samples; failed or incomplete requests cannot disappear to improve the percentile. Missing measurements do not become zero latency. An SDK call span alone does not prove how much of its duration can be excluded.

​

Availability and failures

The 99.9% request target measures correct adapter handling, not the percentage of application calls that return success. Correctly forwarding a target quota or permission error is different from producing that error because the adapter sent the wrong request. Adapter-caused failures count even when the target is healthy. With 1,000,000 eligible calls in a month, a 99.9% target permits at most 1,000 adapter-attributable failures. Endpoint probes have their own denominator. Correctness defects remain actionable even when the monthly availability percentage is met.

​

Scaling and target-service capacity

Scale API handlers and background workers separately. The agreement bounds resource count, concurrent changes, status polling, configuration size and burst growth. More replicas do not remove a shared metadata-store bottleneck or a target API quota. Tensor9 is responsible for adapter capacity within that envelope; the customer supplies target capacity and permissions. Native resource readiness is monitored separately from request acceptance. Connector renewal storms and user changes also consume identity and certificate capacity; agree their concurrency separately from instance polling. Native database connections, CPU, storage and lock contention remain customer-managed target capacity. Tell Tensor9 the expected steady rate, bursts, concurrency, payload sizes and operation mix. Tensor9 sizes and scales the adapter for the agreed load; you choose and monitor the target service’s capacity with Tensor9’s help. A latency budget is not a requests-per-second rating. Larger requests and higher rates need explicit terms, not silent inheritance of a small-request SLA.

​

Data and behavior guarantees

Preserve the selected engine, supported flags and user identity without claiming unavailable extensions or authentication modes. Never acknowledge an invalid certificate or unsupported setting as successfully applied. Creating an instance does not migrate data, users or backup history. Database durability, SQL isolation and native failover duration do not become adapter promises through the control API.

​

Example and diagnosis

Create orders-db, wait for the reported ready state and connect using the actual Google connector library. Measure instance acceptance, connector certificate exchange and the application’s SELECT separately. A fast management response cannot establish successful authentication or prove that required extensions exist on the target. Use tensor9 explain and the documented explain headers to understand the selected adapter and its behavior. Correlate available request diagnostics with the target provider’s latency, throttling and capacity metrics. An explain report helps diagnose a request; it is not by itself a qualified SLA timing measurement. Share the operation, request shape, timestamps and request identifiers with support, with credentials and customer payloads removed.

​

Debug this service

For requests through a service adapter, use Explain and request diagnostics to investigate the selected mapping. Follow the BYOC service-adapter debugging runbook to capture and interpret the diagnostic evidence. Service Catalog.