> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tensor9.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Amazon SQS costs

> Compare Amazon SQS service-adapter costs across backend choices and scale points.

Tensor9 BYOC reference cost models for Amazon SQS. Compare message traffic, batching, payload size and resident backlog with estimated database allocations. Cloud SQL CPU, memory and disk grow under an explicit planning policy; zonal and high-availability choices change its price.

Read [how Tensor9 estimates service-adapter costs](/byoc/costs/overview.md) for billing scope, fixed versus variable charges, capacity qualification and a worked example. The comparisons below appear without calculator input.

## SQS FIFO → Azure Cosmos DB (queue)

Origin API: `aws::1.0.0::sqs::fifo`. Target backend: `azure::1.0.0::cosmosdb::queue`.

### SQS FIFO · SQS request billing units

Estimated monthly service charges by SQS request billing units. Adapter hosting and Tensor9 fees are excluded. Source: us-east-1; target: East US; currency: USD.

![SQS FIFO · SQS request billing units: monthly service charges by SQS request billing units. Exact values are in the following table.](/images/diagrams/service-cost/d73b72c29c2da3b567602cfdda70b6c97b2f1e6e67eccc7406ce7bf5e9645eff-light.svg)

![SQS FIFO · SQS request billing units: monthly service charges by SQS request billing units. Exact values are in the following table.](/images/diagrams/service-cost/c8833afd60078ff4fc597e775b914119cc9b9823b26f0a2d4b56d5460a503705-dark.svg)

Comparison pills describe all sampled scale points; card amounts show the named workload. Costs The Same means within 20% at every point. Costs Depend includes mixed results and unpriced samples.

Exact sampled model outputs in USD/month. Difference means target minus origin; a positive difference means the target costs more.

| SQS request billing units (per second) | SQS (Simple Queue Service, FIFO queues) | Target scenario | Azure Cosmos DB (queue) | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Azure Cosmos DB (queue) | 23.36 | 23.36 |
| 1 | 1.314 | Azure Cosmos DB (queue) | 23.36000476837158203125 | 22.04600476837158203125 |
| 10 | 13.14 | Azure Cosmos DB (queue) | 23.3600476837158203125 | 10.2200476837158203125 |
| 100 | 131.4 | Azure Cosmos DB (queue) | 140.160476837158203125 | 8.760476837158203125 |
| 1000 | 1314 | Azure Cosmos DB (queue) | 1366.56476837158203125 | 52.56476837158203125 |
| 10000 | 13140 | Azure Cosmos DB (queue) | 13630.6076837158203125 | 490.6076837158203125 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Azure Cosmos DB (queue) | Origin list price · SQS billing units | 0.0000005 | USD/64-KiB request units |
| Azure Cosmos DB (queue) | Representative message size | 1024 | bytes |
| Azure Cosmos DB (queue) | Origin send batch fill | 1 | messages/request |
| Azure Cosmos DB (queue) | Origin receive batch fill | 1 | messages/request |
| Azure Cosmos DB (queue) | Origin delete batch fill | 1 | messages/request |
| Azure Cosmos DB (queue) | Deliveries per message | 1 | attempts |
| Azure Cosmos DB (queue) | Empty receive calls per message | 0 | requests |
| Azure Cosmos DB (queue) | Queue residence window | 60 | seconds |
| Azure Cosmos DB (queue) | Ordering and dedup work multiplier | 2 | multiplier |
| Azure Cosmos DB (queue) | Target price guess · read | 0 | USD/read |
| Azure Cosmos DB (queue) | Target price guess · write | 0 | USD/write |
| Azure Cosmos DB (queue) | Target price guess · provider operation | 0 | USD/provider operation |
| Azure Cosmos DB (queue) | Target list price · GiB-month | 0.25 | USD/GiB-month |
| Azure Cosmos DB (queue) | Target price guess · published GiB | 0 | USD/published GiB |
| Azure Cosmos DB (queue) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Azure Cosmos DB (queue) | Target price guess · network GiB | 0 | USD/network GiB |
| Azure Cosmos DB (queue) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Azure Cosmos DB (queue) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Azure Cosmos DB (queue) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Azure Cosmos DB (queue) | Target list price · resource-hour | 0.008 | USD/resource-hour |
| Azure Cosmos DB (queue) | Target price guess · resource-month | 0 | USD/resource-month |
| Azure Cosmos DB (queue) | Target price guess · input token | 0 | USD/input token |
| Azure Cosmos DB (queue) | Target price guess · output token | 0 | USD/output token |
| Azure Cosmos DB (queue) | Target monthly base charge | 0 | USD/month |
| Azure Cosmos DB (queue) | Approximate target service minimum | 0 | USD/month |
| Azure Cosmos DB (queue) | Minimum primary CPU | 2 | vCPU |
| Azure Cosmos DB (queue) | Minimum primary RAM | 8 | GiB |
| Azure Cosmos DB (queue) | Minimum primary disk | 100 | GiB |
| Azure Cosmos DB (queue) | Additional full-price standby copy | 0 | 0 or 1 |
| Azure Cosmos DB (queue) | Allocated share of provisioned cost | 1 | fraction |
| Azure Cosmos DB (queue) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Azure Cosmos DB (queue) | Planning peak / mean work | 2 | multiplier |
| Azure Cosmos DB (queue) | Planning primary CPU utilization | 0.7 | fraction |
| Azure Cosmos DB (queue) | Resident state reserved in RAM | 0.1 | fraction |
| Azure Cosmos DB (queue) | Planning disk utilization | 0.8 | fraction |
| Azure Cosmos DB (queue) | Maintenance and log disk reserve | 20 | GiB |
| Azure Cosmos DB (queue) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Azure Cosmos DB (queue) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Azure Cosmos DB (queue) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Azure Cosmos DB (queue) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Azure Cosmos DB (queue) | Dependent object sink write price guess | 0.000005 | USD/write |

* 1-KiB messages, unbatched send/receive/delete; actual batch and delivery assumptions stay visible. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → East US, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Explicit tariff samples are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* Authored planning assumptions, not measured adapter capacity. Origin rates are cited first-tier list prices, before free allowances and discounts.
* A cost scenario does not establish backend availability, protocol fidelity or production readiness. Registry serving status remains independent.
* Storage follows resident original messages, not every monthly message. Broker delivery bytes include redeliveries.
* FIFO estimates do not qualify dedup support, group throughput or single-group latency; backend limitations remain applicable.
* Azure Cosmos DB provisioned throughput bills 100-RU/s blocks per hour and stored GB-months; operations within the provisioned RU/s have no separate charge. Blocks are sized from the family's reads at 1 RU and writes at 5.5 RU (1 KB items, no extra indexing) at full utilization after the planning peak factor, with the 400 RU/s smallest manual allocation as the floor (USD 23.36/month). Larger messages, indexing and query-based receives raise the RU charge; autoscale (USD 0.012 per 100 RU/s-hour) and serverless (USD 0.25 per million RUs) are not selected.
* AWS Price List API, AWSQueueService offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSQueueService/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSQueueService/current/us-east-1/index.json)
* Azure Retail Prices API: [https://prices.azure.com/api/retail/prices](https://prices.azure.com/api/retail/prices)

Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied.

Excluded costs and workload features:

* Additional network transfer, backups, KMS, one-time migration and operational labor unless an explicit meter includes them.
* Destination application execution and separately billed downstream services; supply those allocations separately.
* Taxes, discounts, credits and free-tier allowances unless explicitly reflected in edited rates.
* Unmodeled dependent services, task execution and operations outside the selected workload family.

List prices read: 2026-10-22. Model: `plan-4f4f008a52eb766d518aa4f34d3302fdb02b1a67` / `2026-10-22.planning.2`. Curve: `workload-1`.

Sources: [AWS Price List API, AWSQueueService offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSQueueService/current/us-east-1/index.json), [Azure Retail Prices API](https://prices.azure.com/api/retail/prices).

## SQS FIFO → Azure Service Bus

Origin API: `aws::1.0.0::sqs::fifo`. Target backend: `azure::1.0.0::servicebus`.

### SQS FIFO · SQS request billing units

Estimated monthly service charges by SQS request billing units. Adapter hosting and Tensor9 fees are excluded. Source: us-east-1; target: East US; currency: USD.

![SQS FIFO · SQS request billing units: monthly service charges by SQS request billing units. Exact values are in the following table.](/images/diagrams/service-cost/a993d49857720b187af58243ea169c342360f1d5668995366fc94325511d70bc-light.svg)

![SQS FIFO · SQS request billing units: monthly service charges by SQS request billing units. Exact values are in the following table.](/images/diagrams/service-cost/1627867864464c0e0147cf0e67ca9b267879df285a161ea182e9003b50c43a82-dark.svg)

Comparison pills describe all sampled scale points; card amounts show the named workload. Costs The Same means within 20% at every point. Costs Depend includes mixed results and unpriced samples.

Exact sampled model outputs in USD/month. Difference means target minus origin; a positive difference means the target costs more.

| SQS request billing units (per second) | SQS (Simple Queue Service, FIFO queues) | Target scenario | Azure Service Bus | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Azure Service Bus | 9.81193 | 9.81193 |
| 1 | 1.314 | Azure Service Bus | 9.81193 | 8.49793 |
| 10 | 13.14 | Azure Service Bus | 20.43593 | 7.29593 |
| 100 | 131.4 | Azure Service Bus | 160.81193 | 29.41193 |
| 1000 | 1314 | Azure Service Bus | 1305.01193 | -8.98807 |
| 10000 | 13140 | Azure Service Bus | 6035.41193 | -7104.58807 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Azure Service Bus | Origin list price · SQS billing units | 0.0000005 | USD/64-KiB request units |
| Azure Service Bus | Representative message size | 1024 | bytes |
| Azure Service Bus | Origin send batch fill | 1 | messages/request |
| Azure Service Bus | Origin receive batch fill | 1 | messages/request |
| Azure Service Bus | Origin delete batch fill | 1 | messages/request |
| Azure Service Bus | Deliveries per message | 1 | attempts |
| Azure Service Bus | Empty receive calls per message | 0 | requests |
| Azure Service Bus | Queue residence window | 60 | seconds |
| Azure Service Bus | Ordering and dedup work multiplier | 2 | multiplier |
| Azure Service Bus | Target price guess · read | 0 | USD/read |
| Azure Service Bus | Target price guess · write | 0 | USD/write |
| Azure Service Bus | Target list price · provider operation | 0.0000008 | USD/provider operation |
| Azure Service Bus | Target price guess · GiB-month | 0 | USD/GiB-month |
| Azure Service Bus | Target price guess · published GiB | 0 | USD/published GiB |
| Azure Service Bus | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Azure Service Bus | Target price guess · network GiB | 0 | USD/network GiB |
| Azure Service Bus | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Azure Service Bus | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Azure Service Bus | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Azure Service Bus | Target price guess · resource-hour | 0 | USD/resource-hour |
| Azure Service Bus | Target price guess · resource-month | 0 | USD/resource-month |
| Azure Service Bus | Target price guess · input token | 0 | USD/input token |
| Azure Service Bus | Target price guess · output token | 0 | USD/output token |
| Azure Service Bus | Included before billing · provider operation | 13000000 | provider operation |
| Azure Service Bus | Target monthly base charge · list price | 9.81193 | USD/month |
| Azure Service Bus | Approximate target service minimum | 0 | USD/month |
| Azure Service Bus | Minimum primary CPU | 2 | vCPU |
| Azure Service Bus | Minimum primary RAM | 8 | GiB |
| Azure Service Bus | Minimum primary disk | 100 | GiB |
| Azure Service Bus | Additional full-price standby copy | 0 | 0 or 1 |
| Azure Service Bus | Allocated share of provisioned cost | 1 | fraction |
| Azure Service Bus | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Azure Service Bus | Planning peak / mean work | 2 | multiplier |
| Azure Service Bus | Planning primary CPU utilization | 0.7 | fraction |
| Azure Service Bus | Resident state reserved in RAM | 0.1 | fraction |
| Azure Service Bus | Planning disk utilization | 0.8 | fraction |
| Azure Service Bus | Maintenance and log disk reserve | 20 | GiB |
| Azure Service Bus | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Azure Service Bus | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Azure Service Bus | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Azure Service Bus | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Azure Service Bus | Dependent object sink write price guess | 0.000005 | USD/write |

* 1-KiB messages, unbatched send/receive/delete; actual batch and delivery assumptions stay visible. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → East US, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Explicit tariff samples are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* Authored planning assumptions, not measured adapter capacity. Origin rates are cited first-tier list prices, before free allowances and discounts.
* A cost scenario does not establish backend availability, protocol fidelity or production readiness. Registry serving status remains independent.
* Storage follows resident original messages, not every monthly message. Broker delivery bytes include redeliveries.
* FIFO estimates do not qualify dedup support, group throughput or single-group latency; backend limitations remain applicable.
* Azure Service Bus Standard bills a namespace base charge that includes 13 million operations a month, then graduated per-operation prices: USD 0.80 per million to 100 million, 0.50 to 2,500 million and 0.20 beyond. An operation is any API call (send, receive, complete) per 64 KB of message; the family's managed operations count calls, not 64 KB units. Standard has no storage charge (queue size quota up to 5 GB is included). More than 1,000 brokered connections bill USD 0.03 per connection-month, which this profile does not model.
* AWS Price List API, AWSQueueService offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSQueueService/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSQueueService/current/us-east-1/index.json)
* Azure Retail Prices API: [https://prices.azure.com/api/retail/prices](https://prices.azure.com/api/retail/prices)

Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied.

Excluded costs and workload features:

* Additional network transfer, backups, KMS, one-time migration and operational labor unless an explicit meter includes them.
* Destination application execution and separately billed downstream services; supply those allocations separately.
* Taxes, discounts, credits and free-tier allowances unless explicitly reflected in edited rates.
* Unmodeled dependent services, task execution and operations outside the selected workload family.

List prices read: 2026-10-22. Model: `plan-41a96e9bd678520a179bd0f5bb232496011160b0` / `2026-10-22.planning.2`. Curve: `workload-1`.

Sources: [AWS Price List API, AWSQueueService offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSQueueService/current/us-east-1/index.json), [Azure Retail Prices API](https://prices.azure.com/api/retail/prices).

## SQS FIFO → Cloud SQL for PostgreSQL

Origin API: `aws::1.0.0::sqs::fifo`. Target backend: `google::1.0.0::cloudsql::postgresql`.

### SQS FIFO · SQS request billing units

Estimated monthly service charges by SQS request billing units. Adapter hosting and Tensor9 fees are excluded. Source: us-east-1; target: us-central1; currency: USD.

![SQS FIFO · SQS request billing units: monthly service charges by SQS request billing units. Exact values are in the following table.](/images/diagrams/service-cost/4b0e0b4e521b266c7f4e092b653b78d013e99b2484f92279733fef5b5c2fe01d-light.svg)

![SQS FIFO · SQS request billing units: monthly service charges by SQS request billing units. Exact values are in the following table.](/images/diagrams/service-cost/5626b9a9609d2a7bf16a15c38c737d623e2108d261c48ca07ac10e6ad9c98a84-dark.svg)

Comparison pills describe all sampled scale points; card amounts show the named workload. Costs The Same means within 20% at every point. Costs Depend includes mixed results and unpriced samples.

Exact sampled model outputs in USD/month. Difference means target minus origin; a positive difference means the target costs more.
Estimated allocation from planning assumptions; not benchmark calibrated. Lines connect evaluated samples; intermediate capacity and prices are not inferred. Unpriced means no target quote or cost difference is available within the sizing policy.

| SQS request billing units (per second) | SQS (Simple Queue Service, FIFO queues) | Target scenario | Cloud SQL for PostgreSQL | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Cloud SQL for PostgreSQL (one copy) | 118.178 | 118.178 |
| 0 | 0 | Cloud SQL for PostgreSQL (two copies) | 236.356 | 236.356 |
| 1 | 1.314 | Cloud SQL for PostgreSQL (one copy) | 118.178 | 116.864 |
| 1 | 1.314 | Cloud SQL for PostgreSQL (two copies) | 236.356 | 235.042 |
| 10 | 13.14 | Cloud SQL for PostgreSQL (one copy) | 118.178 | 105.038 |
| 10 | 13.14 | Cloud SQL for PostgreSQL (two copies) | 236.356 | 223.216 |
| 100 | 131.4 | Cloud SQL for PostgreSQL (one copy) | 118.178 | -13.222 |
| 100 | 131.4 | Cloud SQL for PostgreSQL (two copies) | 236.356 | 104.956 |
| 1000 | 1314 | Cloud SQL for PostgreSQL (one copy) | 421.712 | -892.288 |
| 1000 | 1314 | Cloud SQL for PostgreSQL (two copies) | 843.424 | -470.576 |
| 10000 | 13140 | Cloud SQL for PostgreSQL (one copy) | 3254.696 | -9885.304 |
| 10000 | 13140 | Cloud SQL for PostgreSQL (two copies) | 6509.392 | -6630.608 |

**Estimated allocation from planning assumptions; not benchmark calibrated.**

The sizing policy grows compute with translated work and peak headroom, memory with compute and working set, and disk with resident working state and reserve. Monthly usage is distinct from resident data; each workload's assumptions define the translation. HA changes pricing, not this policy's throughput estimate. Unpriced workloads exceed the policy's configuration range; no silent vertical cap or automatic sharding is assumed.

| Sample / scenario | Basis | Mean / peak work/s | Required vCPU | Allocated vCPU | Memory GiB | SSD GiB | Resident GiB | Policy | Constraints |
| - | - | -: | -: | -: | -: | -: | -: | - | - |
| 0 per second / Cloud SQL for PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 0 per second / Cloud SQL for PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1 per second / Cloud SQL for PostgreSQL (one copy) | PlanningAssumption | 2.666666666666666666666666666666667 / 5.333333333333333333333333333333334 | 0.00507936507936507936507936507936508 | 2 | 8 | 100 | 0.000019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1 per second / Cloud SQL for PostgreSQL (two copies) | PlanningAssumption | 2.666666666666666666666666666666667 / 5.333333333333333333333333333333334 | 0.00507936507936507936507936507936508 | 2 | 8 | 100 | 0.000019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 per second / Cloud SQL for PostgreSQL (one copy) | PlanningAssumption | 26.66666666666666666666666666666667 / 53.33333333333333333333333333333334 | 0.0507936507936507936507936507936508 | 2 | 8 | 100 | 0.00019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 per second / Cloud SQL for PostgreSQL (two copies) | PlanningAssumption | 26.66666666666666666666666666666667 / 53.33333333333333333333333333333334 | 0.0507936507936507936507936507936508 | 2 | 8 | 100 | 0.00019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 per second / Cloud SQL for PostgreSQL (one copy) | PlanningAssumption | 266.6666666666666666666666666666667 / 533.3333333333333333333333333333334 | 0.507936507936507936507936507936508 | 2 | 8 | 100 | 0.0019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 per second / Cloud SQL for PostgreSQL (two copies) | PlanningAssumption | 266.6666666666666666666666666666667 / 533.3333333333333333333333333333334 | 0.507936507936507936507936507936508 | 2 | 8 | 100 | 0.0019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 per second / Cloud SQL for PostgreSQL (one copy) | PlanningAssumption | 2666.666666666666666666666666666667 / 5333.333333333333333333333333333334 | 5.07936507936507936507936507936508 | 8 | 32 | 100 | 0.019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 per second / Cloud SQL for PostgreSQL (two copies) | PlanningAssumption | 2666.666666666666666666666666666667 / 5333.333333333333333333333333333334 | 5.07936507936507936507936507936508 | 8 | 32 | 100 | 0.019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 per second / Cloud SQL for PostgreSQL (one copy) | PlanningAssumption | 26666.66666666666666666666666666667 / 53333.33333333333333333333333333334 | 50.7936507936507936507936507936508 | 64 | 256 | 100 | 0.19073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 per second / Cloud SQL for PostgreSQL (two copies) | PlanningAssumption | 26666.66666666666666666666666666667 / 53333.33333333333333333333333333334 | 50.7936507936507936507936507936508 | 64 | 256 | 100 | 0.19073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |

* Row-store throughput (capacityOpsPerVcpuSecond, default 1500) is measured-by-tensor9 as a lower bound: the DynamoDB adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) served 2,974 ops/s of YCSB-A at 16 threads without recorded saturation (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlPostgresqlYcsbAT16GoYcsbV1\_0\_0.kt). Published CPU-bound pgbench reaches 3,101 read-write transactions and 20,289 point reads per vCPU-second (AWS z1d.2xlarge, PostgreSQL 14.5), so actual capacity is likely higher. Reads and writes share one coefficient: at the same adapter version, read-only YCSB-C was not faster than 50%-update YCSB-A.
* Log-broker throughput (capacityStreamMiBPerVcpuSecond 20 at 0.5 utilization, 4 GiB RAM per vCPU) is provider-documented by Google Managed Service for Apache Kafka sizing ([https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size](https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size)): write-equivalent bytes are replicated writes plus a quarter of reads. Producer batches below 10 KB lower per-CPU throughput; that penalty is not modeled.
* Disk utilization 0.8 is provider-documented headroom below Cloud SQL automatic storage increase, which triggers near 91-95% full ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)). The 20 GiB reserve exceeds PostgreSQL's 1 GB default max\_wal\_size; the remainder of that reserve is unmeasured.
* CPU tiers, 4 GiB per vCPU, at most 6.5 GiB per vCPU, 96 vCPU and 65,536 GiB disk follow Cloud SQL Enterprise custom machine limits (provider-documented, same page); 624 GiB is 96 × 6.5. Targets billed per node, unit or throughput unit are sized by their backend instead.
* No public evidence: peak/mean work (2) and the RAM working-set fraction (0.1). Proposed measurements: the p99 one-minute rate over the monthly mean from customer CloudWatch metrics; the buffer hit ratio while stepping RAM under a fixed YCSB-B load.
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Cloud SQL for PostgreSQL (one copy) | Origin list price · SQS billing units | 0.0000005 | USD/64-KiB request units |
| Cloud SQL for PostgreSQL (one copy) | Representative message size | 1024 | bytes |
| Cloud SQL for PostgreSQL (one copy) | Origin send batch fill | 1 | messages/request |
| Cloud SQL for PostgreSQL (one copy) | Origin receive batch fill | 1 | messages/request |
| Cloud SQL for PostgreSQL (one copy) | Origin delete batch fill | 1 | messages/request |
| Cloud SQL for PostgreSQL (one copy) | Deliveries per message | 1 | attempts |
| Cloud SQL for PostgreSQL (one copy) | Empty receive calls per message | 0 | requests |
| Cloud SQL for PostgreSQL (one copy) | Queue residence window | 60 | seconds |
| Cloud SQL for PostgreSQL (one copy) | Ordering and dedup work multiplier | 2 | multiplier |
| Cloud SQL for PostgreSQL (one copy) | Target price guess · read | 0 | USD/read |
| Cloud SQL for PostgreSQL (one copy) | Target price guess · write | 0 | USD/write |
| Cloud SQL for PostgreSQL (one copy) | Target price guess · provider operation | 0 | USD/provider operation |
| Cloud SQL for PostgreSQL (one copy) | Target list price · GiB-month | 0.17 | USD/GiB-month |
| Cloud SQL for PostgreSQL (one copy) | Target price guess · published GiB | 0 | USD/published GiB |
| Cloud SQL for PostgreSQL (one copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Cloud SQL for PostgreSQL (one copy) | Target list price · network GiB | 0.19 | USD/network GiB |
| Cloud SQL for PostgreSQL (one copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Cloud SQL for PostgreSQL (one copy) | Target list price · vCPU-hour | 0.0413 | USD/vCPU-hour |
| Cloud SQL for PostgreSQL (one copy) | Target list price · GiB-hour | 0.007 | USD/GiB-hour |
| Cloud SQL for PostgreSQL (one copy) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Cloud SQL for PostgreSQL (one copy) | Target price guess · resource-month | 0 | USD/resource-month |
| Cloud SQL for PostgreSQL (one copy) | Target price guess · input token | 0 | USD/input token |
| Cloud SQL for PostgreSQL (one copy) | Target price guess · output token | 0 | USD/output token |
| Cloud SQL for PostgreSQL (one copy) | Target monthly base charge | 0 | USD/month |
| Cloud SQL for PostgreSQL (one copy) | Target service minimum | 9.365 | USD/month |
| Cloud SQL for PostgreSQL (one copy) | Minimum primary CPU | 2 | vCPU |
| Cloud SQL for PostgreSQL (one copy) | Minimum primary RAM | 8 | GiB |
| Cloud SQL for PostgreSQL (one copy) | Minimum primary disk | 100 | GiB |
| Cloud SQL for PostgreSQL (one copy) | Additional full-price standby copy | 0 | 0 or 1 |
| Cloud SQL for PostgreSQL (one copy) | Allocated share of provisioned cost | 1 | fraction |
| Cloud SQL for PostgreSQL (one copy) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Cloud SQL for PostgreSQL (one copy) | Planning peak / mean work | 2 | multiplier |
| Cloud SQL for PostgreSQL (one copy) | Planning primary CPU utilization | 0.7 | fraction |
| Cloud SQL for PostgreSQL (one copy) | Resident state reserved in RAM | 0.1 | fraction |
| Cloud SQL for PostgreSQL (one copy) | Planning disk utilization | 0.8 | fraction |
| Cloud SQL for PostgreSQL (one copy) | Maintenance and log disk reserve | 20 | GiB |
| Cloud SQL for PostgreSQL (one copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Cloud SQL for PostgreSQL (one copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Cloud SQL for PostgreSQL (one copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Cloud SQL for PostgreSQL (one copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Cloud SQL for PostgreSQL (one copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| Cloud SQL for PostgreSQL (two copies) | Origin list price · SQS billing units | 0.0000005 | USD/64-KiB request units |
| Cloud SQL for PostgreSQL (two copies) | Representative message size | 1024 | bytes |
| Cloud SQL for PostgreSQL (two copies) | Origin send batch fill | 1 | messages/request |
| Cloud SQL for PostgreSQL (two copies) | Origin receive batch fill | 1 | messages/request |
| Cloud SQL for PostgreSQL (two copies) | Origin delete batch fill | 1 | messages/request |
| Cloud SQL for PostgreSQL (two copies) | Deliveries per message | 1 | attempts |
| Cloud SQL for PostgreSQL (two copies) | Empty receive calls per message | 0 | requests |
| Cloud SQL for PostgreSQL (two copies) | Queue residence window | 60 | seconds |
| Cloud SQL for PostgreSQL (two copies) | Ordering and dedup work multiplier | 2 | multiplier |
| Cloud SQL for PostgreSQL (two copies) | Target price guess · read | 0 | USD/read |
| Cloud SQL for PostgreSQL (two copies) | Target price guess · write | 0 | USD/write |
| Cloud SQL for PostgreSQL (two copies) | Target price guess · provider operation | 0 | USD/provider operation |
| Cloud SQL for PostgreSQL (two copies) | Target list price · GiB-month | 0.17 | USD/GiB-month |
| Cloud SQL for PostgreSQL (two copies) | Target price guess · published GiB | 0 | USD/published GiB |
| Cloud SQL for PostgreSQL (two copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Cloud SQL for PostgreSQL (two copies) | Target list price · network GiB | 0.19 | USD/network GiB |
| Cloud SQL for PostgreSQL (two copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Cloud SQL for PostgreSQL (two copies) | Target list price · vCPU-hour | 0.0413 | USD/vCPU-hour |
| Cloud SQL for PostgreSQL (two copies) | Target list price · GiB-hour | 0.007 | USD/GiB-hour |
| Cloud SQL for PostgreSQL (two copies) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Cloud SQL for PostgreSQL (two copies) | Target price guess · resource-month | 0 | USD/resource-month |
| Cloud SQL for PostgreSQL (two copies) | Target price guess · input token | 0 | USD/input token |
| Cloud SQL for PostgreSQL (two copies) | Target price guess · output token | 0 | USD/output token |
| Cloud SQL for PostgreSQL (two copies) | Target monthly base charge | 0 | USD/month |
| Cloud SQL for PostgreSQL (two copies) | Target service minimum | 9.365 | USD/month |
| Cloud SQL for PostgreSQL (two copies) | Minimum primary CPU | 2 | vCPU |
| Cloud SQL for PostgreSQL (two copies) | Minimum primary RAM | 8 | GiB |
| Cloud SQL for PostgreSQL (two copies) | Minimum primary disk | 100 | GiB |
| Cloud SQL for PostgreSQL (two copies) | Additional full-price standby copy | 1 | 0 or 1 |
| Cloud SQL for PostgreSQL (two copies) | Allocated share of provisioned cost | 1 | fraction |
| Cloud SQL for PostgreSQL (two copies) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Cloud SQL for PostgreSQL (two copies) | Planning peak / mean work | 2 | multiplier |
| Cloud SQL for PostgreSQL (two copies) | Planning primary CPU utilization | 0.7 | fraction |
| Cloud SQL for PostgreSQL (two copies) | Resident state reserved in RAM | 0.1 | fraction |
| Cloud SQL for PostgreSQL (two copies) | Planning disk utilization | 0.8 | fraction |
| Cloud SQL for PostgreSQL (two copies) | Maintenance and log disk reserve | 20 | GiB |
| Cloud SQL for PostgreSQL (two copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Cloud SQL for PostgreSQL (two copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Cloud SQL for PostgreSQL (two copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Cloud SQL for PostgreSQL (two copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Cloud SQL for PostgreSQL (two copies) | Dependent object sink write price guess | 0.000005 | USD/write |

* 1-KiB messages, unbatched send/receive/delete; actual batch and delivery assumptions stay visible. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → us-central1, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Explicit tariff samples are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* Authored planning assumptions, not measured adapter capacity. Origin rates are cited first-tier list prices, before free allowances and discounts.
* A cost scenario does not establish backend availability, protocol fidelity or production readiness. Registry serving status remains independent.
* Storage follows resident original messages, not every monthly message. Broker delivery bytes include redeliveries.
* FIFO estimates do not qualify dedup support, group throughput or single-group latency; backend limitations remain applicable.
* Cloud SQL Enterprise edition (PostgreSQL) publishes separate vCPU, memory and SSD prices for zonal instances; a high-availability (regional) instance bills exactly twice each, which the standby copy reproduces. Enterprise Plus, committed-use discounts, backups (USD 0.08 per GiB-month) and idle IPv4 addresses (0.01 per hour) are not selected.
* Row-store throughput (capacityOpsPerVcpuSecond, default 1500) is measured-by-tensor9 as a lower bound: the DynamoDB adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) served 2,974 ops/s of YCSB-A at 16 threads without recorded saturation (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlPostgresqlYcsbAT16GoYcsbV1\_0\_0.kt). Published CPU-bound pgbench reaches 3,101 read-write transactions and 20,289 point reads per vCPU-second (AWS z1d.2xlarge, PostgreSQL 14.5), so actual capacity is likely higher. Reads and writes share one coefficient: at the same adapter version, read-only YCSB-C was not faster than 50%-update YCSB-A.
* Log-broker throughput (capacityStreamMiBPerVcpuSecond 20 at 0.5 utilization, 4 GiB RAM per vCPU) is provider-documented by Google Managed Service for Apache Kafka sizing ([https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size](https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size)): write-equivalent bytes are replicated writes plus a quarter of reads. Producer batches below 10 KB lower per-CPU throughput; that penalty is not modeled.
* Disk utilization 0.8 is provider-documented headroom below Cloud SQL automatic storage increase, which triggers near 91-95% full ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)). The 20 GiB reserve exceeds PostgreSQL's 1 GB default max\_wal\_size; the remainder of that reserve is unmeasured.
* CPU tiers, 4 GiB per vCPU, at most 6.5 GiB per vCPU, 96 vCPU and 65,536 GiB disk follow Cloud SQL Enterprise custom machine limits (provider-documented, same page); 624 GiB is 96 × 6.5. Targets billed per node, unit or throughput unit are sized by their backend instead.
* No public evidence: peak/mean work (2) and the RAM working-set fraction (0.1). Proposed measurements: the p99 one-minute rate over the monthly mean from customer CloudWatch metrics; the buffer hit ratio while stepping RAM under a fixed YCSB-B load.
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* AWS Price List API, AWSQueueService offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSQueueService/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSQueueService/current/us-east-1/index.json)
* Cloud SQL pricing: [https://cloud.google.com/sql/pricing](https://cloud.google.com/sql/pricing)

Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied.

Excluded costs and workload features:

* Additional network transfer, backups, KMS, one-time migration and operational labor unless an explicit meter includes them.
* Destination application execution and separately billed downstream services; supply those allocations separately.
* Taxes, discounts, credits and free-tier allowances unless explicitly reflected in edited rates.
* Unmodeled dependent services, task execution and operations outside the selected workload family.

List prices read: 2026-10-22. Model: `plan-c35b94f39c83dfc6e65b2063cdc3c7857cb28524` / `2026-10-22.planning.2`. Curve: `workload-1`.

Sources: [AWS Price List API, AWSQueueService offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSQueueService/current/us-east-1/index.json), [Cloud SQL pricing](https://cloud.google.com/sql/pricing).

## SQS FIFO → PostgreSQL

Origin API: `aws::1.0.0::sqs::fifo`. Target backend: `postgres::1.0.0::database`.

### SQS FIFO · SQS request billing units

Estimated monthly service charges by SQS request billing units. Adapter hosting and Tensor9 fees are excluded. Source: us-east-1; target: us-central1; currency: USD.

![SQS FIFO · SQS request billing units: monthly service charges by SQS request billing units. Exact values are in the following table.](/images/diagrams/service-cost/d98cc265ce80bbf2b13164cf5684e49b981ebff4e69709aee8c3a8494ebbbdc7-light.svg)

![SQS FIFO · SQS request billing units: monthly service charges by SQS request billing units. Exact values are in the following table.](/images/diagrams/service-cost/ddb6f365fd924a445edfa88edae60fae44a2ffd5915591a980ba3e4d9e2760b8-dark.svg)

Comparison pills describe all sampled scale points; card amounts show the named workload. Costs The Same means within 20% at every point. Costs Depend includes mixed results and unpriced samples.

Exact sampled model outputs in USD/month. Difference means target minus origin; a positive difference means the target costs more.
Estimated allocation from planning assumptions; not benchmark calibrated. Lines connect evaluated samples; intermediate capacity and prices are not inferred. Unpriced means no target quote or cost difference is available within the sizing policy.

| SQS request billing units (per second) | SQS (Simple Queue Service, FIFO queues) | Target scenario | PostgreSQL | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | PostgreSQL (one copy) | 80.89614 | 80.89614 |
| 0 | 0 | PostgreSQL (two copies) | 161.79228 | 161.79228 |
| 1 | 1.314 | PostgreSQL (one copy) | 80.89614 | 79.58214 |
| 1 | 1.314 | PostgreSQL (two copies) | 161.79228 | 160.47828 |
| 10 | 13.14 | PostgreSQL (one copy) | 80.89614 | 67.75614 |
| 10 | 13.14 | PostgreSQL (two copies) | 161.79228 | 148.65228 |
| 100 | 131.4 | PostgreSQL (one copy) | 80.89614 | -50.50386 |
| 100 | 131.4 | PostgreSQL (two copies) | 161.79228 | 30.39228 |
| 1000 | 1314 | PostgreSQL (one copy) | 293.58456 | -1020.41544 |
| 1000 | 1314 | PostgreSQL (two copies) | 587.16912 | -726.83088 |
| 10000 | 13140 | PostgreSQL (one copy) | 2278.67648 | -10861.32352 |
| 10000 | 13140 | PostgreSQL (two copies) | 4557.35296 | -8582.64704 |

**Estimated allocation from planning assumptions; not benchmark calibrated.**

The sizing policy grows compute with translated work and peak headroom, memory with compute and working set, and disk with resident working state and reserve. Monthly usage is distinct from resident data; each workload's assumptions define the translation. HA changes pricing, not this policy's throughput estimate. Unpriced workloads exceed the policy's configuration range; no silent vertical cap or automatic sharding is assumed.

| Sample / scenario | Basis | Mean / peak work/s | Required vCPU | Allocated vCPU | Memory GiB | SSD GiB | Resident GiB | Policy | Constraints |
| - | - | -: | -: | -: | -: | -: | -: | - | - |
| 0 per second / PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 0 per second / PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1 per second / PostgreSQL (one copy) | PlanningAssumption | 2.666666666666666666666666666666667 / 5.333333333333333333333333333333334 | 0.00507936507936507936507936507936508 | 2 | 8 | 100 | 0.000019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1 per second / PostgreSQL (two copies) | PlanningAssumption | 2.666666666666666666666666666666667 / 5.333333333333333333333333333333334 | 0.00507936507936507936507936507936508 | 2 | 8 | 100 | 0.000019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 per second / PostgreSQL (one copy) | PlanningAssumption | 26.66666666666666666666666666666667 / 53.33333333333333333333333333333334 | 0.0507936507936507936507936507936508 | 2 | 8 | 100 | 0.00019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 per second / PostgreSQL (two copies) | PlanningAssumption | 26.66666666666666666666666666666667 / 53.33333333333333333333333333333334 | 0.0507936507936507936507936507936508 | 2 | 8 | 100 | 0.00019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 per second / PostgreSQL (one copy) | PlanningAssumption | 266.6666666666666666666666666666667 / 533.3333333333333333333333333333334 | 0.507936507936507936507936507936508 | 2 | 8 | 100 | 0.0019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 per second / PostgreSQL (two copies) | PlanningAssumption | 266.6666666666666666666666666666667 / 533.3333333333333333333333333333334 | 0.507936507936507936507936507936508 | 2 | 8 | 100 | 0.0019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 per second / PostgreSQL (one copy) | PlanningAssumption | 2666.666666666666666666666666666667 / 5333.333333333333333333333333333334 | 5.07936507936507936507936507936508 | 8 | 32 | 100 | 0.019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 per second / PostgreSQL (two copies) | PlanningAssumption | 2666.666666666666666666666666666667 / 5333.333333333333333333333333333334 | 5.07936507936507936507936507936508 | 8 | 32 | 100 | 0.019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 per second / PostgreSQL (one copy) | PlanningAssumption | 26666.66666666666666666666666666667 / 53333.33333333333333333333333333334 | 50.7936507936507936507936507936508 | 64 | 256 | 100 | 0.19073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 per second / PostgreSQL (two copies) | PlanningAssumption | 26666.66666666666666666666666666667 / 53333.33333333333333333333333333334 | 50.7936507936507936507936507936508 | 64 | 256 | 100 | 0.19073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |

* Row-store throughput (capacityOpsPerVcpuSecond, default 1500) is measured-by-tensor9 as a lower bound: the DynamoDB adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) served 2,974 ops/s of YCSB-A at 16 threads without recorded saturation (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlPostgresqlYcsbAT16GoYcsbV1\_0\_0.kt). Published CPU-bound pgbench reaches 3,101 read-write transactions and 20,289 point reads per vCPU-second (AWS z1d.2xlarge, PostgreSQL 14.5), so actual capacity is likely higher. Reads and writes share one coefficient: at the same adapter version, read-only YCSB-C was not faster than 50%-update YCSB-A.
* Log-broker throughput (capacityStreamMiBPerVcpuSecond 20 at 0.5 utilization, 4 GiB RAM per vCPU) is provider-documented by Google Managed Service for Apache Kafka sizing ([https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size](https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size)): write-equivalent bytes are replicated writes plus a quarter of reads. Producer batches below 10 KB lower per-CPU throughput; that penalty is not modeled.
* Disk utilization 0.8 is provider-documented headroom below Cloud SQL automatic storage increase, which triggers near 91-95% full ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)). The 20 GiB reserve exceeds PostgreSQL's 1 GB default max\_wal\_size; the remainder of that reserve is unmeasured.
* CPU tiers, 4 GiB per vCPU, at most 6.5 GiB per vCPU, 96 vCPU and 65,536 GiB disk follow Cloud SQL Enterprise custom machine limits (provider-documented, same page); 624 GiB is 96 × 6.5. Targets billed per node, unit or throughput unit are sized by their backend instead.
* No public evidence: peak/mean work (2) and the RAM working-set fraction (0.1). Proposed measurements: the p99 one-minute rate over the monthly mean from customer CloudWatch metrics; the buffer hit ratio while stepping RAM under a fixed YCSB-B load.
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| PostgreSQL (one copy) | Origin list price · SQS billing units | 0.0000005 | USD/64-KiB request units |
| PostgreSQL (one copy) | Representative message size | 1024 | bytes |
| PostgreSQL (one copy) | Origin send batch fill | 1 | messages/request |
| PostgreSQL (one copy) | Origin receive batch fill | 1 | messages/request |
| PostgreSQL (one copy) | Origin delete batch fill | 1 | messages/request |
| PostgreSQL (one copy) | Deliveries per message | 1 | attempts |
| PostgreSQL (one copy) | Empty receive calls per message | 0 | requests |
| PostgreSQL (one copy) | Queue residence window | 60 | seconds |
| PostgreSQL (one copy) | Ordering and dedup work multiplier | 2 | multiplier |
| PostgreSQL (one copy) | Target price guess · read | 0 | USD/read |
| PostgreSQL (one copy) | Target price guess · write | 0 | USD/write |
| PostgreSQL (one copy) | Target price guess · provider operation | 0 | USD/provider operation |
| PostgreSQL (one copy) | Target list price · GiB-month | 0.1 | USD/GiB-month |
| PostgreSQL (one copy) | Target price guess · published GiB | 0 | USD/published GiB |
| PostgreSQL (one copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| PostgreSQL (one copy) | Target list price · network GiB | 0.12 | USD/network GiB |
| PostgreSQL (one copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| PostgreSQL (one copy) | Target list price · vCPU-hour | 0.031611 | USD/vCPU-hour |
| PostgreSQL (one copy) | Target list price · GiB-hour | 0.004237 | USD/GiB-hour |
| PostgreSQL (one copy) | Target price guess · resource-hour | 0 | USD/resource-hour |
| PostgreSQL (one copy) | Target price guess · resource-month | 0 | USD/resource-month |
| PostgreSQL (one copy) | Target price guess · input token | 0 | USD/input token |
| PostgreSQL (one copy) | Target price guess · output token | 0 | USD/output token |
| PostgreSQL (one copy) | Target monthly base charge | 0 | USD/month |
| PostgreSQL (one copy) | Approximate target service minimum | 0 | USD/month |
| PostgreSQL (one copy) | Minimum primary CPU | 2 | vCPU |
| PostgreSQL (one copy) | Minimum primary RAM | 8 | GiB |
| PostgreSQL (one copy) | Minimum primary disk | 100 | GiB |
| PostgreSQL (one copy) | Additional full-price standby copy | 0 | 0 or 1 |
| PostgreSQL (one copy) | Allocated share of provisioned cost | 1 | fraction |
| PostgreSQL (one copy) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| PostgreSQL (one copy) | Planning peak / mean work | 2 | multiplier |
| PostgreSQL (one copy) | Planning primary CPU utilization | 0.7 | fraction |
| PostgreSQL (one copy) | Resident state reserved in RAM | 0.1 | fraction |
| PostgreSQL (one copy) | Planning disk utilization | 0.8 | fraction |
| PostgreSQL (one copy) | Maintenance and log disk reserve | 20 | GiB |
| PostgreSQL (one copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| PostgreSQL (one copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| PostgreSQL (one copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| PostgreSQL (one copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| PostgreSQL (one copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| PostgreSQL (two copies) | Origin list price · SQS billing units | 0.0000005 | USD/64-KiB request units |
| PostgreSQL (two copies) | Representative message size | 1024 | bytes |
| PostgreSQL (two copies) | Origin send batch fill | 1 | messages/request |
| PostgreSQL (two copies) | Origin receive batch fill | 1 | messages/request |
| PostgreSQL (two copies) | Origin delete batch fill | 1 | messages/request |
| PostgreSQL (two copies) | Deliveries per message | 1 | attempts |
| PostgreSQL (two copies) | Empty receive calls per message | 0 | requests |
| PostgreSQL (two copies) | Queue residence window | 60 | seconds |
| PostgreSQL (two copies) | Ordering and dedup work multiplier | 2 | multiplier |
| PostgreSQL (two copies) | Target price guess · read | 0 | USD/read |
| PostgreSQL (two copies) | Target price guess · write | 0 | USD/write |
| PostgreSQL (two copies) | Target price guess · provider operation | 0 | USD/provider operation |
| PostgreSQL (two copies) | Target list price · GiB-month | 0.1 | USD/GiB-month |
| PostgreSQL (two copies) | Target price guess · published GiB | 0 | USD/published GiB |
| PostgreSQL (two copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| PostgreSQL (two copies) | Target list price · network GiB | 0.12 | USD/network GiB |
| PostgreSQL (two copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| PostgreSQL (two copies) | Target list price · vCPU-hour | 0.031611 | USD/vCPU-hour |
| PostgreSQL (two copies) | Target list price · GiB-hour | 0.004237 | USD/GiB-hour |
| PostgreSQL (two copies) | Target price guess · resource-hour | 0 | USD/resource-hour |
| PostgreSQL (two copies) | Target price guess · resource-month | 0 | USD/resource-month |
| PostgreSQL (two copies) | Target price guess · input token | 0 | USD/input token |
| PostgreSQL (two copies) | Target price guess · output token | 0 | USD/output token |
| PostgreSQL (two copies) | Target monthly base charge | 0 | USD/month |
| PostgreSQL (two copies) | Approximate target service minimum | 0 | USD/month |
| PostgreSQL (two copies) | Minimum primary CPU | 2 | vCPU |
| PostgreSQL (two copies) | Minimum primary RAM | 8 | GiB |
| PostgreSQL (two copies) | Minimum primary disk | 100 | GiB |
| PostgreSQL (two copies) | Additional full-price standby copy | 1 | 0 or 1 |
| PostgreSQL (two copies) | Allocated share of provisioned cost | 1 | fraction |
| PostgreSQL (two copies) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| PostgreSQL (two copies) | Planning peak / mean work | 2 | multiplier |
| PostgreSQL (two copies) | Planning primary CPU utilization | 0.7 | fraction |
| PostgreSQL (two copies) | Resident state reserved in RAM | 0.1 | fraction |
| PostgreSQL (two copies) | Planning disk utilization | 0.8 | fraction |
| PostgreSQL (two copies) | Maintenance and log disk reserve | 20 | GiB |
| PostgreSQL (two copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| PostgreSQL (two copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| PostgreSQL (two copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| PostgreSQL (two copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| PostgreSQL (two copies) | Dependent object sink write price guess | 0.000005 | USD/write |

* 1-KiB messages, unbatched send/receive/delete; actual batch and delivery assumptions stay visible. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → us-central1, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Explicit tariff samples are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* Authored planning assumptions, not measured adapter capacity. Origin rates are cited first-tier list prices, before free allowances and discounts.
* A cost scenario does not establish backend availability, protocol fidelity or production readiness. Registry serving status remains independent.
* Storage follows resident original messages, not every monthly message. Broker delivery bytes include redeliveries.
* FIFO estimates do not qualify dedup support, group throughput or single-group latency; backend limitations remain applicable.
* Self-hosted target: PostgreSQL (PostgreSQL License, [https://www.postgresql.org/about/licence/](https://www.postgresql.org/about/licence/)). Selected CPU, RAM and physical disk allocation grow with workload; no per-operation price is assumed. No vendor tariff: the target runs on the customer's Kubernetes nodes, so CPU, RAM and disk bill at the Kubernetes node reference rates, Compute Engine N2 in us-central1 (USD 0.031611/vCPU-hour, 0.004237/GiB-hour) with pd-balanced disk (0.10/GiB-month) and Premium Tier egress. The cost-optimized E2 series lists 0.02181159/vCPU-hour and 0.00292353/GiB-hour; AWS m6i/r6i and Azure D2s v5/E2s v5 both decompose to 0.033/vCPU-hour and 0.00375/GiB-hour. Requested CPU and RAM are billed; node bin-packing waste, system reservations and the cluster control-plane fee are not.
* Row-store throughput (capacityOpsPerVcpuSecond, default 1500) is measured-by-tensor9 as a lower bound: the DynamoDB adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) served 2,974 ops/s of YCSB-A at 16 threads without recorded saturation (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlPostgresqlYcsbAT16GoYcsbV1\_0\_0.kt). Published CPU-bound pgbench reaches 3,101 read-write transactions and 20,289 point reads per vCPU-second (AWS z1d.2xlarge, PostgreSQL 14.5), so actual capacity is likely higher. Reads and writes share one coefficient: at the same adapter version, read-only YCSB-C was not faster than 50%-update YCSB-A.
* Log-broker throughput (capacityStreamMiBPerVcpuSecond 20 at 0.5 utilization, 4 GiB RAM per vCPU) is provider-documented by Google Managed Service for Apache Kafka sizing ([https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size](https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size)): write-equivalent bytes are replicated writes plus a quarter of reads. Producer batches below 10 KB lower per-CPU throughput; that penalty is not modeled.
* Disk utilization 0.8 is provider-documented headroom below Cloud SQL automatic storage increase, which triggers near 91-95% full ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)). The 20 GiB reserve exceeds PostgreSQL's 1 GB default max\_wal\_size; the remainder of that reserve is unmeasured.
* CPU tiers, 4 GiB per vCPU, at most 6.5 GiB per vCPU, 96 vCPU and 65,536 GiB disk follow Cloud SQL Enterprise custom machine limits (provider-documented, same page); 624 GiB is 96 × 6.5. Targets billed per node, unit or throughput unit are sized by their backend instead.
* No public evidence: peak/mean work (2) and the RAM working-set fraction (0.1). Proposed measurements: the p99 one-minute rate over the monthly mean from customer CloudWatch metrics; the buffer hit ratio while stepping RAM under a fixed YCSB-B load.
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* AWS Price List API, AWSQueueService offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSQueueService/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSQueueService/current/us-east-1/index.json)
* Compute Engine general-purpose machine pricing: [https://cloud.google.com/products/compute/pricing/general-purpose](https://cloud.google.com/products/compute/pricing/general-purpose)
* Disk and image pricing: [https://cloud.google.com/compute/disks-image-pricing](https://cloud.google.com/compute/disks-image-pricing)
* Network pricing: [https://cloud.google.com/vpc/network-pricing](https://cloud.google.com/vpc/network-pricing)

Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied.

Excluded costs and workload features:

* Additional network transfer, backups, KMS, one-time migration and operational labor unless an explicit meter includes them.
* Destination application execution and separately billed downstream services; supply those allocations separately.
* Taxes, discounts, credits and free-tier allowances unless explicitly reflected in edited rates.
* Unmodeled dependent services, task execution and operations outside the selected workload family.

List prices read: 2026-10-22. Model: `plan-2205b0bb4fecd035329ea8f524e1a885b9bdcdab` / `2026-10-22.planning.2`. Curve: `workload-1`.

Sources: [AWS Price List API, AWSQueueService offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSQueueService/current/us-east-1/index.json), [Compute Engine general-purpose machine pricing](https://cloud.google.com/products/compute/pricing/general-purpose), [Disk and image pricing](https://cloud.google.com/compute/disks-image-pricing), [Network pricing](https://cloud.google.com/vpc/network-pricing).

## SQS FIFO → PostgreSQL Flexible Server

Origin API: `aws::1.0.0::sqs::fifo`. Target backend: `azure::1.0.0::postgresql::flexible`.

### SQS FIFO · SQS request billing units

Estimated monthly service charges by SQS request billing units. Adapter hosting and Tensor9 fees are excluded. Source: us-east-1; target: eastus; currency: USD.

![SQS FIFO · SQS request billing units: monthly service charges by SQS request billing units. Exact values are in the following table.](/images/diagrams/service-cost/7083d5874d7e3ad525fec4e1e0ce5f605795e103fdf6dcbbbcb34a76169d2856-light.svg)

![SQS FIFO · SQS request billing units: monthly service charges by SQS request billing units. Exact values are in the following table.](/images/diagrams/service-cost/75714652646985aefddedb8879a3fdea63413802f78eab1006ba3aeb569b1ddc-dark.svg)

Comparison pills describe all sampled scale points; card amounts show the named workload. Costs The Same means within 20% at every point. Costs Depend includes mixed results and unpriced samples.

Exact sampled model outputs in USD/month. Difference means target minus origin; a positive difference means the target costs more.
Estimated allocation from planning assumptions; not benchmark calibrated. Lines connect evaluated samples; intermediate capacity and prices are not inferred. Unpriced means no target quote or cost difference is available within the sizing policy.

| SQS request billing units (per second) | SQS (Simple Queue Service, FIFO queues) | Target scenario | PostgreSQL Flexible Server | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | PostgreSQL Flexible Server (one copy) | 141.44 | 141.44 |
| 0 | 0 | PostgreSQL Flexible Server (two copies) | 282.88 | 282.88 |
| 1 | 1.314 | PostgreSQL Flexible Server (one copy) | 141.44 | 140.126 |
| 1 | 1.314 | PostgreSQL Flexible Server (two copies) | 282.88 | 281.566 |
| 10 | 13.14 | PostgreSQL Flexible Server (one copy) | 141.44 | 128.3 |
| 10 | 13.14 | PostgreSQL Flexible Server (two copies) | 282.88 | 269.74 |
| 100 | 131.4 | PostgreSQL Flexible Server (one copy) | 141.44 | 10.04 |
| 100 | 131.4 | PostgreSQL Flexible Server (two copies) | 282.88 | 151.48 |
| 1000 | 1314 | PostgreSQL Flexible Server (one copy) | 531.26 | -782.74 |
| 1000 | 1314 | PostgreSQL Flexible Server (two copies) | 1062.52 | -251.48 |
| 10000 | 13140 | PostgreSQL Flexible Server (one copy) | 4169.58 | -8970.42 |
| 10000 | 13140 | PostgreSQL Flexible Server (two copies) | 8339.16 | -4800.84 |

**Estimated allocation from planning assumptions; not benchmark calibrated.**

The sizing policy grows compute with translated work and peak headroom, memory with compute and working set, and disk with resident working state and reserve. Monthly usage is distinct from resident data; each workload's assumptions define the translation. HA changes pricing, not this policy's throughput estimate. Unpriced workloads exceed the policy's configuration range; no silent vertical cap or automatic sharding is assumed.

| Sample / scenario | Basis | Mean / peak work/s | Required vCPU | Allocated vCPU | Memory GiB | SSD GiB | Resident GiB | Policy | Constraints |
| - | - | -: | -: | -: | -: | -: | -: | - | - |
| 0 per second / PostgreSQL Flexible Server (one copy) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 0 per second / PostgreSQL Flexible Server (two copies) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1 per second / PostgreSQL Flexible Server (one copy) | PlanningAssumption | 2.666666666666666666666666666666667 / 5.333333333333333333333333333333334 | 0.00507936507936507936507936507936508 | 2 | 8 | 100 | 0.000019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1 per second / PostgreSQL Flexible Server (two copies) | PlanningAssumption | 2.666666666666666666666666666666667 / 5.333333333333333333333333333333334 | 0.00507936507936507936507936507936508 | 2 | 8 | 100 | 0.000019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 per second / PostgreSQL Flexible Server (one copy) | PlanningAssumption | 26.66666666666666666666666666666667 / 53.33333333333333333333333333333334 | 0.0507936507936507936507936507936508 | 2 | 8 | 100 | 0.00019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 per second / PostgreSQL Flexible Server (two copies) | PlanningAssumption | 26.66666666666666666666666666666667 / 53.33333333333333333333333333333334 | 0.0507936507936507936507936507936508 | 2 | 8 | 100 | 0.00019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 per second / PostgreSQL Flexible Server (one copy) | PlanningAssumption | 266.6666666666666666666666666666667 / 533.3333333333333333333333333333334 | 0.507936507936507936507936507936508 | 2 | 8 | 100 | 0.0019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 per second / PostgreSQL Flexible Server (two copies) | PlanningAssumption | 266.6666666666666666666666666666667 / 533.3333333333333333333333333333334 | 0.507936507936507936507936507936508 | 2 | 8 | 100 | 0.0019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 per second / PostgreSQL Flexible Server (one copy) | PlanningAssumption | 2666.666666666666666666666666666667 / 5333.333333333333333333333333333334 | 5.07936507936507936507936507936508 | 8 | 32 | 100 | 0.019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 per second / PostgreSQL Flexible Server (two copies) | PlanningAssumption | 2666.666666666666666666666666666667 / 5333.333333333333333333333333333334 | 5.07936507936507936507936507936508 | 8 | 32 | 100 | 0.019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 per second / PostgreSQL Flexible Server (one copy) | PlanningAssumption | 26666.66666666666666666666666666667 / 53333.33333333333333333333333333334 | 50.7936507936507936507936507936508 | 64 | 256 | 100 | 0.19073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 per second / PostgreSQL Flexible Server (two copies) | PlanningAssumption | 26666.66666666666666666666666666667 / 53333.33333333333333333333333333334 | 50.7936507936507936507936507936508 | 64 | 256 | 100 | 0.19073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |

* Row-store throughput (capacityOpsPerVcpuSecond, default 1500) is measured-by-tensor9 as a lower bound: the DynamoDB adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) served 2,974 ops/s of YCSB-A at 16 threads without recorded saturation (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlPostgresqlYcsbAT16GoYcsbV1\_0\_0.kt). Published CPU-bound pgbench reaches 3,101 read-write transactions and 20,289 point reads per vCPU-second (AWS z1d.2xlarge, PostgreSQL 14.5), so actual capacity is likely higher. Reads and writes share one coefficient: at the same adapter version, read-only YCSB-C was not faster than 50%-update YCSB-A.
* Log-broker throughput (capacityStreamMiBPerVcpuSecond 20 at 0.5 utilization, 4 GiB RAM per vCPU) is provider-documented by Google Managed Service for Apache Kafka sizing ([https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size](https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size)): write-equivalent bytes are replicated writes plus a quarter of reads. Producer batches below 10 KB lower per-CPU throughput; that penalty is not modeled.
* Disk utilization 0.8 is provider-documented headroom below Cloud SQL automatic storage increase, which triggers near 91-95% full ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)). The 20 GiB reserve exceeds PostgreSQL's 1 GB default max\_wal\_size; the remainder of that reserve is unmeasured.
* CPU tiers, 4 GiB per vCPU, at most 6.5 GiB per vCPU, 96 vCPU and 65,536 GiB disk follow Cloud SQL Enterprise custom machine limits (provider-documented, same page); 624 GiB is 96 × 6.5. Targets billed per node, unit or throughput unit are sized by their backend instead.
* No public evidence: peak/mean work (2) and the RAM working-set fraction (0.1). Proposed measurements: the p99 one-minute rate over the monthly mean from customer CloudWatch metrics; the buffer hit ratio while stepping RAM under a fixed YCSB-B load.
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| PostgreSQL Flexible Server (one copy) | Origin list price · SQS billing units | 0.0000005 | USD/64-KiB request units |
| PostgreSQL Flexible Server (one copy) | Representative message size | 1024 | bytes |
| PostgreSQL Flexible Server (one copy) | Origin send batch fill | 1 | messages/request |
| PostgreSQL Flexible Server (one copy) | Origin receive batch fill | 1 | messages/request |
| PostgreSQL Flexible Server (one copy) | Origin delete batch fill | 1 | messages/request |
| PostgreSQL Flexible Server (one copy) | Deliveries per message | 1 | attempts |
| PostgreSQL Flexible Server (one copy) | Empty receive calls per message | 0 | requests |
| PostgreSQL Flexible Server (one copy) | Queue residence window | 60 | seconds |
| PostgreSQL Flexible Server (one copy) | Ordering and dedup work multiplier | 2 | multiplier |
| PostgreSQL Flexible Server (one copy) | Target price guess · read | 0 | USD/read |
| PostgreSQL Flexible Server (one copy) | Target price guess · write | 0 | USD/write |
| PostgreSQL Flexible Server (one copy) | Target price guess · provider operation | 0 | USD/provider operation |
| PostgreSQL Flexible Server (one copy) | Target list price · GiB-month | 0.115 | USD/GiB-month |
| PostgreSQL Flexible Server (one copy) | Target price guess · published GiB | 0 | USD/published GiB |
| PostgreSQL Flexible Server (one copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| PostgreSQL Flexible Server (one copy) | Target list price · network GiB | 0.087 | USD/network GiB |
| PostgreSQL Flexible Server (one copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| PostgreSQL Flexible Server (one copy) | Target list price · vCPU-hour | 0.053 | USD/vCPU-hour |
| PostgreSQL Flexible Server (one copy) | Target list price · GiB-hour | 0.009 | USD/GiB-hour |
| PostgreSQL Flexible Server (one copy) | Target price guess · resource-hour | 0 | USD/resource-hour |
| PostgreSQL Flexible Server (one copy) | Target price guess · resource-month | 0 | USD/resource-month |
| PostgreSQL Flexible Server (one copy) | Target price guess · input token | 0 | USD/input token |
| PostgreSQL Flexible Server (one copy) | Target price guess · output token | 0 | USD/output token |
| PostgreSQL Flexible Server (one copy) | Target monthly base charge | 0 | USD/month |
| PostgreSQL Flexible Server (one copy) | Target service minimum | 16.09 | USD/month |
| PostgreSQL Flexible Server (one copy) | Minimum primary CPU | 2 | vCPU |
| PostgreSQL Flexible Server (one copy) | Minimum primary RAM | 8 | GiB |
| PostgreSQL Flexible Server (one copy) | Minimum primary disk | 100 | GiB |
| PostgreSQL Flexible Server (one copy) | Additional full-price standby copy | 0 | 0 or 1 |
| PostgreSQL Flexible Server (one copy) | Allocated share of provisioned cost | 1 | fraction |
| PostgreSQL Flexible Server (one copy) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| PostgreSQL Flexible Server (one copy) | Planning peak / mean work | 2 | multiplier |
| PostgreSQL Flexible Server (one copy) | Planning primary CPU utilization | 0.7 | fraction |
| PostgreSQL Flexible Server (one copy) | Resident state reserved in RAM | 0.1 | fraction |
| PostgreSQL Flexible Server (one copy) | Planning disk utilization | 0.8 | fraction |
| PostgreSQL Flexible Server (one copy) | Maintenance and log disk reserve | 20 | GiB |
| PostgreSQL Flexible Server (one copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| PostgreSQL Flexible Server (one copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| PostgreSQL Flexible Server (one copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| PostgreSQL Flexible Server (one copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| PostgreSQL Flexible Server (one copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| PostgreSQL Flexible Server (two copies) | Origin list price · SQS billing units | 0.0000005 | USD/64-KiB request units |
| PostgreSQL Flexible Server (two copies) | Representative message size | 1024 | bytes |
| PostgreSQL Flexible Server (two copies) | Origin send batch fill | 1 | messages/request |
| PostgreSQL Flexible Server (two copies) | Origin receive batch fill | 1 | messages/request |
| PostgreSQL Flexible Server (two copies) | Origin delete batch fill | 1 | messages/request |
| PostgreSQL Flexible Server (two copies) | Deliveries per message | 1 | attempts |
| PostgreSQL Flexible Server (two copies) | Empty receive calls per message | 0 | requests |
| PostgreSQL Flexible Server (two copies) | Queue residence window | 60 | seconds |
| PostgreSQL Flexible Server (two copies) | Ordering and dedup work multiplier | 2 | multiplier |
| PostgreSQL Flexible Server (two copies) | Target price guess · read | 0 | USD/read |
| PostgreSQL Flexible Server (two copies) | Target price guess · write | 0 | USD/write |
| PostgreSQL Flexible Server (two copies) | Target price guess · provider operation | 0 | USD/provider operation |
| PostgreSQL Flexible Server (two copies) | Target list price · GiB-month | 0.115 | USD/GiB-month |
| PostgreSQL Flexible Server (two copies) | Target price guess · published GiB | 0 | USD/published GiB |
| PostgreSQL Flexible Server (two copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| PostgreSQL Flexible Server (two copies) | Target list price · network GiB | 0.087 | USD/network GiB |
| PostgreSQL Flexible Server (two copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| PostgreSQL Flexible Server (two copies) | Target list price · vCPU-hour | 0.053 | USD/vCPU-hour |
| PostgreSQL Flexible Server (two copies) | Target list price · GiB-hour | 0.009 | USD/GiB-hour |
| PostgreSQL Flexible Server (two copies) | Target price guess · resource-hour | 0 | USD/resource-hour |
| PostgreSQL Flexible Server (two copies) | Target price guess · resource-month | 0 | USD/resource-month |
| PostgreSQL Flexible Server (two copies) | Target price guess · input token | 0 | USD/input token |
| PostgreSQL Flexible Server (two copies) | Target price guess · output token | 0 | USD/output token |
| PostgreSQL Flexible Server (two copies) | Target monthly base charge | 0 | USD/month |
| PostgreSQL Flexible Server (two copies) | Target service minimum | 16.09 | USD/month |
| PostgreSQL Flexible Server (two copies) | Minimum primary CPU | 2 | vCPU |
| PostgreSQL Flexible Server (two copies) | Minimum primary RAM | 8 | GiB |
| PostgreSQL Flexible Server (two copies) | Minimum primary disk | 100 | GiB |
| PostgreSQL Flexible Server (two copies) | Additional full-price standby copy | 1 | 0 or 1 |
| PostgreSQL Flexible Server (two copies) | Allocated share of provisioned cost | 1 | fraction |
| PostgreSQL Flexible Server (two copies) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| PostgreSQL Flexible Server (two copies) | Planning peak / mean work | 2 | multiplier |
| PostgreSQL Flexible Server (two copies) | Planning primary CPU utilization | 0.7 | fraction |
| PostgreSQL Flexible Server (two copies) | Resident state reserved in RAM | 0.1 | fraction |
| PostgreSQL Flexible Server (two copies) | Planning disk utilization | 0.8 | fraction |
| PostgreSQL Flexible Server (two copies) | Maintenance and log disk reserve | 20 | GiB |
| PostgreSQL Flexible Server (two copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| PostgreSQL Flexible Server (two copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| PostgreSQL Flexible Server (two copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| PostgreSQL Flexible Server (two copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| PostgreSQL Flexible Server (two copies) | Dependent object sink write price guess | 0.000005 | USD/write |

* 1-KiB messages, unbatched send/receive/delete; actual batch and delivery assumptions stay visible. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → eastus, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Explicit tariff samples are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* Authored planning assumptions, not measured adapter capacity. Origin rates are cited first-tier list prices, before free allowances and discounts.
* A cost scenario does not establish backend availability, protocol fidelity or production readiness. Registry serving status remains independent.
* Storage follows resident original messages, not every monthly message. Broker delivery bytes include redeliveries.
* FIFO estimates do not qualify dedup support, group throughput or single-group latency; backend limitations remain applicable.
* Azure Database for PostgreSQL Flexible Server bills vCores with a fixed memory ratio per series; the vCPU and memory rates decompose the General Purpose and Memory Optimized v5 prices. High availability bills the standby's compute and storage as a second copy. The minimum is the smallest Burstable server, which does not support high availability; the smallest General Purpose server (2 vCores) costs USD 133.62 per month. Additional IOPS, backup storage and reserved capacity are not selected.
* Row-store throughput (capacityOpsPerVcpuSecond, default 1500) is measured-by-tensor9 as a lower bound: the DynamoDB adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) served 2,974 ops/s of YCSB-A at 16 threads without recorded saturation (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlPostgresqlYcsbAT16GoYcsbV1\_0\_0.kt). Published CPU-bound pgbench reaches 3,101 read-write transactions and 20,289 point reads per vCPU-second (AWS z1d.2xlarge, PostgreSQL 14.5), so actual capacity is likely higher. Reads and writes share one coefficient: at the same adapter version, read-only YCSB-C was not faster than 50%-update YCSB-A.
* Log-broker throughput (capacityStreamMiBPerVcpuSecond 20 at 0.5 utilization, 4 GiB RAM per vCPU) is provider-documented by Google Managed Service for Apache Kafka sizing ([https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size](https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size)): write-equivalent bytes are replicated writes plus a quarter of reads. Producer batches below 10 KB lower per-CPU throughput; that penalty is not modeled.
* Disk utilization 0.8 is provider-documented headroom below Cloud SQL automatic storage increase, which triggers near 91-95% full ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)). The 20 GiB reserve exceeds PostgreSQL's 1 GB default max\_wal\_size; the remainder of that reserve is unmeasured.
* CPU tiers, 4 GiB per vCPU, at most 6.5 GiB per vCPU, 96 vCPU and 65,536 GiB disk follow Cloud SQL Enterprise custom machine limits (provider-documented, same page); 624 GiB is 96 × 6.5. Targets billed per node, unit or throughput unit are sized by their backend instead.
* No public evidence: peak/mean work (2) and the RAM working-set fraction (0.1). Proposed measurements: the p99 one-minute rate over the monthly mean from customer CloudWatch metrics; the buffer hit ratio while stepping RAM under a fixed YCSB-B load.
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* AWS Price List API, AWSQueueService offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSQueueService/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSQueueService/current/us-east-1/index.json)
* Azure Retail Prices API: [https://prices.azure.com/api/retail/prices](https://prices.azure.com/api/retail/prices)

Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied.

Excluded costs and workload features:

* Additional network transfer, backups, KMS, one-time migration and operational labor unless an explicit meter includes them.
* Destination application execution and separately billed downstream services; supply those allocations separately.
* Taxes, discounts, credits and free-tier allowances unless explicitly reflected in edited rates.
* Unmodeled dependent services, task execution and operations outside the selected workload family.

List prices read: 2026-10-22. Model: `plan-d6e6756733e57b05fe1084c81427de33e78217f0` / `2026-10-22.planning.2`. Curve: `workload-1`.

Sources: [AWS Price List API, AWSQueueService offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSQueueService/current/us-east-1/index.json), [Azure Retail Prices API](https://prices.azure.com/api/retail/prices).

## SQS FIFO → Scaleway Managed Database for PostgreSQL

Origin API: `aws::1.0.0::sqs::fifo`. Target backend: `scaleway::1.0.0::rdb::postgresql`.

### SQS FIFO · SQS request billing units

Estimated monthly service charges by SQS request billing units. Adapter hosting and Tensor9 fees are excluded. Source: us-east-1; target: fr-par; currency: USD.

![SQS FIFO · SQS request billing units: monthly service charges by SQS request billing units. Exact values are in the following table.](/images/diagrams/service-cost/a998543cd9003b8b3eedce77059bac314d620ab3d0ecb4876828eeb0dd61b5e0-light.svg)

![SQS FIFO · SQS request billing units: monthly service charges by SQS request billing units. Exact values are in the following table.](/images/diagrams/service-cost/3c99361639a8e93c72e1571b8872057f1d2aa9b352841233fedaa9915ab762ca-dark.svg)

Comparison pills describe all sampled scale points; card amounts show the named workload. Costs The Same means within 20% at every point. Costs Depend includes mixed results and unpriced samples.

Exact sampled model outputs in USD/month. Difference means target minus origin; a positive difference means the target costs more.
Estimated allocation from planning assumptions; not benchmark calibrated. Lines connect evaluated samples; intermediate capacity and prices are not inferred. Unpriced means no target quote or cost difference is available within the sizing policy.

| SQS request billing units (per second) | SQS (Simple Queue Service, FIFO queues) | Target scenario | Scaleway Managed Database for PostgreSQL | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Scaleway Managed Database for PostgreSQL (one copy) | 101.102715 | 101.102715 |
| 0 | 0 | Scaleway Managed Database for PostgreSQL (two copies) | 154.68715395 | 154.68715395 |
| 1 | 1.314 | Scaleway Managed Database for PostgreSQL (one copy) | 101.102715 | 99.788715 |
| 1 | 1.314 | Scaleway Managed Database for PostgreSQL (two copies) | 154.68715395 | 153.37315395 |
| 10 | 13.14 | Scaleway Managed Database for PostgreSQL (one copy) | 101.102715 | 87.962715 |
| 10 | 13.14 | Scaleway Managed Database for PostgreSQL (two copies) | 154.68715395 | 141.54715395 |
| 100 | 131.4 | Scaleway Managed Database for PostgreSQL (one copy) | 101.102715 | -30.297285 |
| 100 | 131.4 | Scaleway Managed Database for PostgreSQL (two copies) | 154.68715395 | 23.28715395 |
| 1000 | 1314 | Scaleway Managed Database for PostgreSQL (one copy) | 371.031165 | -942.968835 |
| 1000 | 1314 | Scaleway Managed Database for PostgreSQL (two copies) | 567.67768245 | -746.32231755 |
| 10000 | 13140 | Scaleway Managed Database for PostgreSQL (one copy) | 2890.363365 | -10249.636635 |
| 10000 | 13140 | Scaleway Managed Database for PostgreSQL (two copies) | 4422.25594845 | -8717.74405155 |

**Estimated allocation from planning assumptions; not benchmark calibrated.**

The sizing policy grows compute with translated work and peak headroom, memory with compute and working set, and disk with resident working state and reserve. Monthly usage is distinct from resident data; each workload's assumptions define the translation. HA changes pricing, not this policy's throughput estimate. Unpriced workloads exceed the policy's configuration range; no silent vertical cap or automatic sharding is assumed.

| Sample / scenario | Basis | Mean / peak work/s | Required vCPU | Allocated vCPU | Memory GiB | SSD GiB | Resident GiB | Policy | Constraints |
| - | - | -: | -: | -: | -: | -: | -: | - | - |
| 0 per second / Scaleway Managed Database for PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 0 per second / Scaleway Managed Database for PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1 per second / Scaleway Managed Database for PostgreSQL (one copy) | PlanningAssumption | 2.666666666666666666666666666666667 / 5.333333333333333333333333333333334 | 0.00507936507936507936507936507936508 | 2 | 8 | 100 | 0.000019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1 per second / Scaleway Managed Database for PostgreSQL (two copies) | PlanningAssumption | 2.666666666666666666666666666666667 / 5.333333333333333333333333333333334 | 0.00507936507936507936507936507936508 | 2 | 8 | 100 | 0.000019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 per second / Scaleway Managed Database for PostgreSQL (one copy) | PlanningAssumption | 26.66666666666666666666666666666667 / 53.33333333333333333333333333333334 | 0.0507936507936507936507936507936508 | 2 | 8 | 100 | 0.00019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 per second / Scaleway Managed Database for PostgreSQL (two copies) | PlanningAssumption | 26.66666666666666666666666666666667 / 53.33333333333333333333333333333334 | 0.0507936507936507936507936507936508 | 2 | 8 | 100 | 0.00019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 per second / Scaleway Managed Database for PostgreSQL (one copy) | PlanningAssumption | 266.6666666666666666666666666666667 / 533.3333333333333333333333333333334 | 0.507936507936507936507936507936508 | 2 | 8 | 100 | 0.0019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 per second / Scaleway Managed Database for PostgreSQL (two copies) | PlanningAssumption | 266.6666666666666666666666666666667 / 533.3333333333333333333333333333334 | 0.507936507936507936507936507936508 | 2 | 8 | 100 | 0.0019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 per second / Scaleway Managed Database for PostgreSQL (one copy) | PlanningAssumption | 2666.666666666666666666666666666667 / 5333.333333333333333333333333333334 | 5.07936507936507936507936507936508 | 8 | 32 | 100 | 0.019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 per second / Scaleway Managed Database for PostgreSQL (two copies) | PlanningAssumption | 2666.666666666666666666666666666667 / 5333.333333333333333333333333333334 | 5.07936507936507936507936507936508 | 8 | 32 | 100 | 0.019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 per second / Scaleway Managed Database for PostgreSQL (one copy) | PlanningAssumption | 26666.66666666666666666666666666667 / 53333.33333333333333333333333333334 | 50.7936507936507936507936507936508 | 64 | 256 | 100 | 0.19073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 per second / Scaleway Managed Database for PostgreSQL (two copies) | PlanningAssumption | 26666.66666666666666666666666666667 / 53333.33333333333333333333333333334 | 50.7936507936507936507936507936508 | 64 | 256 | 100 | 0.19073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |

* Row-store throughput (capacityOpsPerVcpuSecond, default 1500) is measured-by-tensor9 as a lower bound: the DynamoDB adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) served 2,974 ops/s of YCSB-A at 16 threads without recorded saturation (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlPostgresqlYcsbAT16GoYcsbV1\_0\_0.kt). Published CPU-bound pgbench reaches 3,101 read-write transactions and 20,289 point reads per vCPU-second (AWS z1d.2xlarge, PostgreSQL 14.5), so actual capacity is likely higher. Reads and writes share one coefficient: at the same adapter version, read-only YCSB-C was not faster than 50%-update YCSB-A.
* Log-broker throughput (capacityStreamMiBPerVcpuSecond 20 at 0.5 utilization, 4 GiB RAM per vCPU) is provider-documented by Google Managed Service for Apache Kafka sizing ([https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size](https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size)): write-equivalent bytes are replicated writes plus a quarter of reads. Producer batches below 10 KB lower per-CPU throughput; that penalty is not modeled.
* Disk utilization 0.8 is provider-documented headroom below Cloud SQL automatic storage increase, which triggers near 91-95% full ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)). The 20 GiB reserve exceeds PostgreSQL's 1 GB default max\_wal\_size; the remainder of that reserve is unmeasured.
* CPU tiers, 4 GiB per vCPU, at most 6.5 GiB per vCPU, 96 vCPU and 65,536 GiB disk follow Cloud SQL Enterprise custom machine limits (provider-documented, same page); 624 GiB is 96 × 6.5. Targets billed per node, unit or throughput unit are sized by their backend instead.
* No public evidence: peak/mean work (2) and the RAM working-set fraction (0.1). Proposed measurements: the p99 one-minute rate over the monthly mean from customer CloudWatch metrics; the buffer hit ratio while stepping RAM under a fixed YCSB-B load.
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Scaleway Managed Database for PostgreSQL (one copy) | Origin list price · SQS billing units | 0.0000005 | USD/64-KiB request units |
| Scaleway Managed Database for PostgreSQL (one copy) | Representative message size | 1024 | bytes |
| Scaleway Managed Database for PostgreSQL (one copy) | Origin send batch fill | 1 | messages/request |
| Scaleway Managed Database for PostgreSQL (one copy) | Origin receive batch fill | 1 | messages/request |
| Scaleway Managed Database for PostgreSQL (one copy) | Origin delete batch fill | 1 | messages/request |
| Scaleway Managed Database for PostgreSQL (one copy) | Deliveries per message | 1 | attempts |
| Scaleway Managed Database for PostgreSQL (one copy) | Empty receive calls per message | 0 | requests |
| Scaleway Managed Database for PostgreSQL (one copy) | Queue residence window | 60 | seconds |
| Scaleway Managed Database for PostgreSQL (one copy) | Ordering and dedup work multiplier | 2 | multiplier |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · read | 0 | USD/read |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · write | 0 | USD/write |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · provider operation | 0 | USD/provider operation |
| Scaleway Managed Database for PostgreSQL (one copy) | Target list price · GiB-month | 0.11126565 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · published GiB | 0 | USD/published GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · network GiB | 0 | USD/network GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Target list price · vCPU-hour | 0.0367275 | USD/vCPU-hour |
| Scaleway Managed Database for PostgreSQL (one copy) | Target list price · GiB-hour | 0.006225 | USD/GiB-hour |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · resource-month | 0 | USD/resource-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · input token | 0 | USD/input token |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · output token | 0 | USD/output token |
| Scaleway Managed Database for PostgreSQL (one copy) | Target monthly base charge | 0 | USD/month |
| Scaleway Managed Database for PostgreSQL (one copy) | Target service minimum | 89.97615 | USD/month |
| Scaleway Managed Database for PostgreSQL (one copy) | Minimum primary CPU | 2 | vCPU |
| Scaleway Managed Database for PostgreSQL (one copy) | Minimum primary RAM | 8 | GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Minimum primary disk | 100 | GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Additional full-price standby copy | 0 | 0 or 1 |
| Scaleway Managed Database for PostgreSQL (one copy) | Allocated share of provisioned cost | 1 | fraction |
| Scaleway Managed Database for PostgreSQL (one copy) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Scaleway Managed Database for PostgreSQL (one copy) | Planning peak / mean work | 2 | multiplier |
| Scaleway Managed Database for PostgreSQL (one copy) | Planning primary CPU utilization | 0.7 | fraction |
| Scaleway Managed Database for PostgreSQL (one copy) | Resident state reserved in RAM | 0.1 | fraction |
| Scaleway Managed Database for PostgreSQL (one copy) | Planning disk utilization | 0.8 | fraction |
| Scaleway Managed Database for PostgreSQL (one copy) | Maintenance and log disk reserve | 20 | GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Scaleway Managed Database for PostgreSQL (one copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Scaleway Managed Database for PostgreSQL (one copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| Scaleway Managed Database for PostgreSQL (two copies) | Origin list price · SQS billing units | 0.0000005 | USD/64-KiB request units |
| Scaleway Managed Database for PostgreSQL (two copies) | Representative message size | 1024 | bytes |
| Scaleway Managed Database for PostgreSQL (two copies) | Origin send batch fill | 1 | messages/request |
| Scaleway Managed Database for PostgreSQL (two copies) | Origin receive batch fill | 1 | messages/request |
| Scaleway Managed Database for PostgreSQL (two copies) | Origin delete batch fill | 1 | messages/request |
| Scaleway Managed Database for PostgreSQL (two copies) | Deliveries per message | 1 | attempts |
| Scaleway Managed Database for PostgreSQL (two copies) | Empty receive calls per message | 0 | requests |
| Scaleway Managed Database for PostgreSQL (two copies) | Queue residence window | 60 | seconds |
| Scaleway Managed Database for PostgreSQL (two copies) | Ordering and dedup work multiplier | 2 | multiplier |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · read | 0 | USD/read |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · write | 0 | USD/write |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · provider operation | 0 | USD/provider operation |
| Scaleway Managed Database for PostgreSQL (two copies) | Target list price · GiB-month | 0.11126565 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · published GiB | 0 | USD/published GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · network GiB | 0 | USD/network GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Scaleway Managed Database for PostgreSQL (two copies) | Target list price · vCPU-hour | 0.0367275 | USD/vCPU-hour |
| Scaleway Managed Database for PostgreSQL (two copies) | Target list price · GiB-hour | 0.006225 | USD/GiB-hour |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · resource-month | 0 | USD/resource-month |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · input token | 0 | USD/input token |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · output token | 0 | USD/output token |
| Scaleway Managed Database for PostgreSQL (two copies) | Target monthly base charge | 0 | USD/month |
| Scaleway Managed Database for PostgreSQL (two copies) | Target service minimum | 89.97615 | USD/month |
| Scaleway Managed Database for PostgreSQL (two copies) | Minimum primary CPU | 2 | vCPU |
| Scaleway Managed Database for PostgreSQL (two copies) | Minimum primary RAM | 8 | GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Minimum primary disk | 100 | GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Additional full-price standby copy | 1 | 0 or 1 |
| Scaleway Managed Database for PostgreSQL (two copies) | Allocated share of provisioned cost | 1 | fraction |
| Scaleway Managed Database for PostgreSQL (two copies) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Scaleway Managed Database for PostgreSQL (two copies) | Planning peak / mean work | 2 | multiplier |
| Scaleway Managed Database for PostgreSQL (two copies) | Planning primary CPU utilization | 0.7 | fraction |
| Scaleway Managed Database for PostgreSQL (two copies) | Resident state reserved in RAM | 0.1 | fraction |
| Scaleway Managed Database for PostgreSQL (two copies) | Planning disk utilization | 0.8 | fraction |
| Scaleway Managed Database for PostgreSQL (two copies) | Maintenance and log disk reserve | 20 | GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Scaleway Managed Database for PostgreSQL (two copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Scaleway Managed Database for PostgreSQL (two copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (two copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (two copies) | Dependent object sink write price guess | 0.000005 | USD/write |

* 1-KiB messages, unbatched send/receive/delete; actual batch and delivery assumptions stay visible. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → fr-par, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Explicit tariff samples are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* Authored planning assumptions, not measured adapter capacity. Origin rates are cited first-tier list prices, before free allowances and discounts.
* A cost scenario does not establish backend availability, protocol fidelity or production readiness. Registry serving status remains independent.
* Storage follows resident original messages, not every monthly message. Broker delivery bytes include redeliveries.
* FIFO estimates do not qualify dedup support, group throughput or single-group latency; backend limitations remain applicable.
* Scaleway Managed Database for PostgreSQL at Production Optimized (PRO2) prices in EUR converted at the ECB reference rate. A high-availability or replica node bills Scaleway's 'Additional nodes' price, EUR 0.0583 per hour for PRO2-XXS, 53% of the main node. Scaleway lists no egress charge for Managed Databases, so selected network is not charged. Cost Optimized ranges (DB-DEV-S from EUR 0.0156 per hour), Block Storage 15K and backups (EUR 0.03 per GB-month) are not selected.
* Row-store throughput (capacityOpsPerVcpuSecond, default 1500) is measured-by-tensor9 as a lower bound: the DynamoDB adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) served 2,974 ops/s of YCSB-A at 16 threads without recorded saturation (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlPostgresqlYcsbAT16GoYcsbV1\_0\_0.kt). Published CPU-bound pgbench reaches 3,101 read-write transactions and 20,289 point reads per vCPU-second (AWS z1d.2xlarge, PostgreSQL 14.5), so actual capacity is likely higher. Reads and writes share one coefficient: at the same adapter version, read-only YCSB-C was not faster than 50%-update YCSB-A.
* Log-broker throughput (capacityStreamMiBPerVcpuSecond 20 at 0.5 utilization, 4 GiB RAM per vCPU) is provider-documented by Google Managed Service for Apache Kafka sizing ([https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size](https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size)): write-equivalent bytes are replicated writes plus a quarter of reads. Producer batches below 10 KB lower per-CPU throughput; that penalty is not modeled.
* Disk utilization 0.8 is provider-documented headroom below Cloud SQL automatic storage increase, which triggers near 91-95% full ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)). The 20 GiB reserve exceeds PostgreSQL's 1 GB default max\_wal\_size; the remainder of that reserve is unmeasured.
* CPU tiers, 4 GiB per vCPU, at most 6.5 GiB per vCPU, 96 vCPU and 65,536 GiB disk follow Cloud SQL Enterprise custom machine limits (provider-documented, same page); 624 GiB is 96 × 6.5. Targets billed per node, unit or throughput unit are sized by their backend instead.
* No public evidence: peak/mean work (2) and the RAM working-set fraction (0.1). Proposed measurements: the p99 one-minute rate over the monthly mean from customer CloudWatch metrics; the buffer hit ratio while stepping RAM under a fixed YCSB-B load.
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* AWS Price List API, AWSQueueService offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSQueueService/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSQueueService/current/us-east-1/index.json)
* Scaleway Managed Databases pricing: [https://www.scaleway.com/en/pricing/managed-databases/](https://www.scaleway.com/en/pricing/managed-databases/)

Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied.

Excluded costs and workload features:

* Additional network transfer, backups, KMS, one-time migration and operational labor unless an explicit meter includes them.
* Destination application execution and separately billed downstream services; supply those allocations separately.
* Taxes, discounts, credits and free-tier allowances unless explicitly reflected in edited rates.
* Unmodeled dependent services, task execution and operations outside the selected workload family.

List prices read: 2026-10-22. Model: `plan-587f83be80f7d547d383d9abce0fac6d8798d699` / `2026-10-22.planning.2`. Curve: `workload-1`.

Sources: [AWS Price List API, AWSQueueService offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSQueueService/current/us-east-1/index.json), [Scaleway Managed Databases pricing](https://www.scaleway.com/en/pricing/managed-databases/).

## SQS Standard → Azure Cosmos DB (queue)

Origin API: `aws::1.0.0::sqs::classic`. Target backend: `azure::1.0.0::cosmosdb::queue`.

### SQS Standard · SQS request billing units

Estimated monthly service charges by SQS request billing units. Adapter hosting and Tensor9 fees are excluded. Source: us-east-1; target: East US; currency: USD.

![SQS Standard · SQS request billing units: monthly service charges by SQS request billing units. Exact values are in the following table.](/images/diagrams/service-cost/0ce4bb561f1a4f0d0a30654a20af1a8deff931fe6ee2b582cdaa53c6a75ccad0-light.svg)

![SQS Standard · SQS request billing units: monthly service charges by SQS request billing units. Exact values are in the following table.](/images/diagrams/service-cost/efc4758ddc1f7d9cc2fbd85b21613ecb406d34e977965dca7043eea1198ab81d-dark.svg)

Comparison pills describe all sampled scale points; card amounts show the named workload. Costs The Same means within 20% at every point. Costs Depend includes mixed results and unpriced samples.

Exact sampled model outputs in USD/month. Difference means target minus origin; a positive difference means the target costs more.

| SQS request billing units (per second) | SQS (Simple Queue Service, standard queues) | Target scenario | Azure Cosmos DB (queue) | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Azure Cosmos DB (queue) | 23.36 | 23.36 |
| 1 | 1.0512 | Azure Cosmos DB (queue) | 23.36000476837158203125 | 22.30880476837158203125 |
| 10 | 10.512 | Azure Cosmos DB (queue) | 23.3600476837158203125 | 12.8480476837158203125 |
| 100 | 105.12 | Azure Cosmos DB (queue) | 70.080476837158203125 | -35.039523162841796875 |
| 1000 | 1051.2 | Azure Cosmos DB (queue) | 683.28476837158203125 | -367.91523162841796875 |
| 10000 | 10512 | Azure Cosmos DB (queue) | 6815.3276837158203125 | -3696.6723162841796875 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Azure Cosmos DB (queue) | Origin list price · SQS billing units | 0.0000004 | USD/64-KiB request units |
| Azure Cosmos DB (queue) | Representative message size | 1024 | bytes |
| Azure Cosmos DB (queue) | Origin send batch fill | 1 | messages/request |
| Azure Cosmos DB (queue) | Origin receive batch fill | 1 | messages/request |
| Azure Cosmos DB (queue) | Origin delete batch fill | 1 | messages/request |
| Azure Cosmos DB (queue) | Deliveries per message | 1 | attempts |
| Azure Cosmos DB (queue) | Empty receive calls per message | 0 | requests |
| Azure Cosmos DB (queue) | Queue residence window | 60 | seconds |
| Azure Cosmos DB (queue) | Ordering and dedup work multiplier | 1 | multiplier |
| Azure Cosmos DB (queue) | Target price guess · read | 0 | USD/read |
| Azure Cosmos DB (queue) | Target price guess · write | 0 | USD/write |
| Azure Cosmos DB (queue) | Target price guess · provider operation | 0 | USD/provider operation |
| Azure Cosmos DB (queue) | Target list price · GiB-month | 0.25 | USD/GiB-month |
| Azure Cosmos DB (queue) | Target price guess · published GiB | 0 | USD/published GiB |
| Azure Cosmos DB (queue) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Azure Cosmos DB (queue) | Target price guess · network GiB | 0 | USD/network GiB |
| Azure Cosmos DB (queue) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Azure Cosmos DB (queue) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Azure Cosmos DB (queue) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Azure Cosmos DB (queue) | Target list price · resource-hour | 0.008 | USD/resource-hour |
| Azure Cosmos DB (queue) | Target price guess · resource-month | 0 | USD/resource-month |
| Azure Cosmos DB (queue) | Target price guess · input token | 0 | USD/input token |
| Azure Cosmos DB (queue) | Target price guess · output token | 0 | USD/output token |
| Azure Cosmos DB (queue) | Target monthly base charge | 0 | USD/month |
| Azure Cosmos DB (queue) | Approximate target service minimum | 0 | USD/month |
| Azure Cosmos DB (queue) | Minimum primary CPU | 2 | vCPU |
| Azure Cosmos DB (queue) | Minimum primary RAM | 8 | GiB |
| Azure Cosmos DB (queue) | Minimum primary disk | 100 | GiB |
| Azure Cosmos DB (queue) | Additional full-price standby copy | 0 | 0 or 1 |
| Azure Cosmos DB (queue) | Allocated share of provisioned cost | 1 | fraction |
| Azure Cosmos DB (queue) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Azure Cosmos DB (queue) | Planning peak / mean work | 2 | multiplier |
| Azure Cosmos DB (queue) | Planning primary CPU utilization | 0.7 | fraction |
| Azure Cosmos DB (queue) | Resident state reserved in RAM | 0.1 | fraction |
| Azure Cosmos DB (queue) | Planning disk utilization | 0.8 | fraction |
| Azure Cosmos DB (queue) | Maintenance and log disk reserve | 20 | GiB |
| Azure Cosmos DB (queue) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Azure Cosmos DB (queue) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Azure Cosmos DB (queue) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Azure Cosmos DB (queue) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Azure Cosmos DB (queue) | Dependent object sink write price guess | 0.000005 | USD/write |

* 1-KiB messages, unbatched send/receive/delete; actual batch and delivery assumptions stay visible. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → East US, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Explicit tariff samples are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* Authored planning assumptions, not measured adapter capacity. Origin rates are cited first-tier list prices, before free allowances and discounts.
* A cost scenario does not establish backend availability, protocol fidelity or production readiness. Registry serving status remains independent.
* Storage follows resident original messages, not every monthly message. Broker delivery bytes include redeliveries.
* FIFO estimates do not qualify dedup support, group throughput or single-group latency; backend limitations remain applicable.
* Azure Cosmos DB provisioned throughput bills 100-RU/s blocks per hour and stored GB-months; operations within the provisioned RU/s have no separate charge. Blocks are sized from the family's reads at 1 RU and writes at 5.5 RU (1 KB items, no extra indexing) at full utilization after the planning peak factor, with the 400 RU/s smallest manual allocation as the floor (USD 23.36/month). Larger messages, indexing and query-based receives raise the RU charge; autoscale (USD 0.012 per 100 RU/s-hour) and serverless (USD 0.25 per million RUs) are not selected.
* AWS Price List API, AWSQueueService offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSQueueService/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSQueueService/current/us-east-1/index.json)
* Azure Retail Prices API: [https://prices.azure.com/api/retail/prices](https://prices.azure.com/api/retail/prices)

Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied.

Excluded costs and workload features:

* Additional network transfer, backups, KMS, one-time migration and operational labor unless an explicit meter includes them.
* Destination application execution and separately billed downstream services; supply those allocations separately.
* Taxes, discounts, credits and free-tier allowances unless explicitly reflected in edited rates.
* Unmodeled dependent services, task execution and operations outside the selected workload family.

List prices read: 2026-10-22. Model: `plan-dad0c8f973de92af6643c3cb9f65340d91c718a5` / `2026-10-22.planning.2`. Curve: `workload-1`.

Sources: [AWS Price List API, AWSQueueService offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSQueueService/current/us-east-1/index.json), [Azure Retail Prices API](https://prices.azure.com/api/retail/prices).

## SQS Standard → Azure Queue Storage

Origin API: `aws::1.0.0::sqs::classic`. Target backend: `azure::1.0.0::queue-storage`.

### SQS Standard · SQS request billing units

Estimated monthly service charges by SQS request billing units. Adapter hosting and Tensor9 fees are excluded. Source: us-east-1; target: East US; currency: USD.

![SQS Standard · SQS request billing units: monthly service charges by SQS request billing units. Exact values are in the following table.](/images/diagrams/service-cost/6c0b4eb40869d03efe41c6de2c497cda96d4f721629bbb5d1099849c17dcb483-light.svg)

![SQS Standard · SQS request billing units: monthly service charges by SQS request billing units. Exact values are in the following table.](/images/diagrams/service-cost/ef15c82e1ab5930872cf232b1b50841445453cbc341d8822c06498e2297d80a5-dark.svg)

Comparison pills describe all sampled scale points; card amounts show the named workload. Costs The Same means within 20% at every point. Costs Depend includes mixed results and unpriced samples.

Exact sampled model outputs in USD/month. Difference means target minus origin; a positive difference means the target costs more.

| SQS request billing units (per second) | SQS (Simple Queue Service, standard queues) | Target scenario | Azure Queue Storage | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Azure Queue Storage | 0 | 0 |
| 1 | 1.0512 | Azure Queue Storage | 1.051200858306884765625 | 0.000000858306884765625 |
| 10 | 10.512 | Azure Queue Storage | 10.51200858306884765625 | 0.00000858306884765625 |
| 100 | 105.12 | Azure Queue Storage | 105.1200858306884765625 | 0.0000858306884765625 |
| 1000 | 1051.2 | Azure Queue Storage | 1051.200858306884765625 | 0.000858306884765625 |
| 10000 | 10512 | Azure Queue Storage | 10512.00858306884765625 | 0.00858306884765625 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Azure Queue Storage | Origin list price · SQS billing units | 0.0000004 | USD/64-KiB request units |
| Azure Queue Storage | Representative message size | 1024 | bytes |
| Azure Queue Storage | Origin send batch fill | 1 | messages/request |
| Azure Queue Storage | Origin receive batch fill | 1 | messages/request |
| Azure Queue Storage | Origin delete batch fill | 1 | messages/request |
| Azure Queue Storage | Deliveries per message | 1 | attempts |
| Azure Queue Storage | Empty receive calls per message | 0 | requests |
| Azure Queue Storage | Queue residence window | 60 | seconds |
| Azure Queue Storage | Ordering and dedup work multiplier | 1 | multiplier |
| Azure Queue Storage | Target price guess · read | 0 | USD/read |
| Azure Queue Storage | Target price guess · write | 0 | USD/write |
| Azure Queue Storage | Target list price · provider operation | 0.0000004 | USD/provider operation |
| Azure Queue Storage | Target list price · GiB-month | 0.045 | USD/GiB-month |
| Azure Queue Storage | Target price guess · published GiB | 0 | USD/published GiB |
| Azure Queue Storage | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Azure Queue Storage | Target price guess · network GiB | 0 | USD/network GiB |
| Azure Queue Storage | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Azure Queue Storage | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Azure Queue Storage | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Azure Queue Storage | Target price guess · resource-hour | 0 | USD/resource-hour |
| Azure Queue Storage | Target price guess · resource-month | 0 | USD/resource-month |
| Azure Queue Storage | Target price guess · input token | 0 | USD/input token |
| Azure Queue Storage | Target price guess · output token | 0 | USD/output token |
| Azure Queue Storage | Target monthly base charge | 0 | USD/month |
| Azure Queue Storage | Approximate target service minimum | 0 | USD/month |
| Azure Queue Storage | Minimum primary CPU | 2 | vCPU |
| Azure Queue Storage | Minimum primary RAM | 8 | GiB |
| Azure Queue Storage | Minimum primary disk | 100 | GiB |
| Azure Queue Storage | Additional full-price standby copy | 0 | 0 or 1 |
| Azure Queue Storage | Allocated share of provisioned cost | 1 | fraction |
| Azure Queue Storage | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Azure Queue Storage | Planning peak / mean work | 2 | multiplier |
| Azure Queue Storage | Planning primary CPU utilization | 0.7 | fraction |
| Azure Queue Storage | Resident state reserved in RAM | 0.1 | fraction |
| Azure Queue Storage | Planning disk utilization | 0.8 | fraction |
| Azure Queue Storage | Maintenance and log disk reserve | 20 | GiB |
| Azure Queue Storage | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Azure Queue Storage | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Azure Queue Storage | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Azure Queue Storage | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Azure Queue Storage | Dependent object sink write price guess | 0.000005 | USD/write |

* 1-KiB messages, unbatched send/receive/delete; actual batch and delivery assumptions stay visible. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → East US, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Explicit tariff samples are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* Authored planning assumptions, not measured adapter capacity. Origin rates are cited first-tier list prices, before free allowances and discounts.
* A cost scenario does not establish backend availability, protocol fidelity or production readiness. Registry serving status remains independent.
* Storage follows resident original messages, not every monthly message. Broker delivery bytes include redeliveries.
* FIFO estimates do not qualify dedup support, group throughput or single-group latency; backend limitations remain applicable.
* Azure Queue Storage (general-purpose v2, Standard LRS) bills every REST operation and stored GB-months. Each managed operation is one queue call; a queue message is at most 64 KiB, so no size multiplier applies. GRS, ZRS and the legacy general-purpose v1 account price differently. Internet egress is billed by Azure networking, not the queue, and the mapped families select none.
* AWS Price List API, AWSQueueService offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSQueueService/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSQueueService/current/us-east-1/index.json)
* Azure Retail Prices API: [https://prices.azure.com/api/retail/prices](https://prices.azure.com/api/retail/prices)

Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied.

Excluded costs and workload features:

* Additional network transfer, backups, KMS, one-time migration and operational labor unless an explicit meter includes them.
* Destination application execution and separately billed downstream services; supply those allocations separately.
* Taxes, discounts, credits and free-tier allowances unless explicitly reflected in edited rates.
* Unmodeled dependent services, task execution and operations outside the selected workload family.

List prices read: 2026-10-22. Model: `plan-d5bf5eea867ef509a6394c8ab16664bacb37eb07` / `2026-10-22.planning.2`. Curve: `workload-1`.

Sources: [AWS Price List API, AWSQueueService offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSQueueService/current/us-east-1/index.json), [Azure Retail Prices API](https://prices.azure.com/api/retail/prices).

## SQS Standard → Azure Service Bus

Origin API: `aws::1.0.0::sqs::classic`. Target backend: `azure::1.0.0::servicebus`.

### SQS Standard · SQS request billing units

Estimated monthly service charges by SQS request billing units. Adapter hosting and Tensor9 fees are excluded. Source: us-east-1; target: East US; currency: USD.

![SQS Standard · SQS request billing units: monthly service charges by SQS request billing units. Exact values are in the following table.](/images/diagrams/service-cost/59be6d995219fc6837f434b4fcea83f0360b38815381d609299fa84540f4a1c0-light.svg)

![SQS Standard · SQS request billing units: monthly service charges by SQS request billing units. Exact values are in the following table.](/images/diagrams/service-cost/968517d9463146d131de30a29783e659f9cc67f4e8fabdc94c44f8be8720252f-dark.svg)

Comparison pills describe all sampled scale points; card amounts show the named workload. Costs The Same means within 20% at every point. Costs Depend includes mixed results and unpriced samples.

Exact sampled model outputs in USD/month. Difference means target minus origin; a positive difference means the target costs more.

| SQS request billing units (per second) | SQS (Simple Queue Service, standard queues) | Target scenario | Azure Service Bus | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Azure Service Bus | 9.81193 | 9.81193 |
| 1 | 1.0512 | Azure Service Bus | 9.81193 | 8.76073 |
| 10 | 10.512 | Azure Service Bus | 20.43593 | 9.92393 |
| 100 | 105.12 | Azure Service Bus | 160.81193 | 55.69193 |
| 1000 | 1051.2 | Azure Service Bus | 1305.01193 | 253.81193 |
| 10000 | 10512 | Azure Service Bus | 6035.41193 | -4476.58807 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Azure Service Bus | Origin list price · SQS billing units | 0.0000004 | USD/64-KiB request units |
| Azure Service Bus | Representative message size | 1024 | bytes |
| Azure Service Bus | Origin send batch fill | 1 | messages/request |
| Azure Service Bus | Origin receive batch fill | 1 | messages/request |
| Azure Service Bus | Origin delete batch fill | 1 | messages/request |
| Azure Service Bus | Deliveries per message | 1 | attempts |
| Azure Service Bus | Empty receive calls per message | 0 | requests |
| Azure Service Bus | Queue residence window | 60 | seconds |
| Azure Service Bus | Ordering and dedup work multiplier | 1 | multiplier |
| Azure Service Bus | Target price guess · read | 0 | USD/read |
| Azure Service Bus | Target price guess · write | 0 | USD/write |
| Azure Service Bus | Target list price · provider operation | 0.0000008 | USD/provider operation |
| Azure Service Bus | Target price guess · GiB-month | 0 | USD/GiB-month |
| Azure Service Bus | Target price guess · published GiB | 0 | USD/published GiB |
| Azure Service Bus | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Azure Service Bus | Target price guess · network GiB | 0 | USD/network GiB |
| Azure Service Bus | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Azure Service Bus | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Azure Service Bus | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Azure Service Bus | Target price guess · resource-hour | 0 | USD/resource-hour |
| Azure Service Bus | Target price guess · resource-month | 0 | USD/resource-month |
| Azure Service Bus | Target price guess · input token | 0 | USD/input token |
| Azure Service Bus | Target price guess · output token | 0 | USD/output token |
| Azure Service Bus | Included before billing · provider operation | 13000000 | provider operation |
| Azure Service Bus | Target monthly base charge · list price | 9.81193 | USD/month |
| Azure Service Bus | Approximate target service minimum | 0 | USD/month |
| Azure Service Bus | Minimum primary CPU | 2 | vCPU |
| Azure Service Bus | Minimum primary RAM | 8 | GiB |
| Azure Service Bus | Minimum primary disk | 100 | GiB |
| Azure Service Bus | Additional full-price standby copy | 0 | 0 or 1 |
| Azure Service Bus | Allocated share of provisioned cost | 1 | fraction |
| Azure Service Bus | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Azure Service Bus | Planning peak / mean work | 2 | multiplier |
| Azure Service Bus | Planning primary CPU utilization | 0.7 | fraction |
| Azure Service Bus | Resident state reserved in RAM | 0.1 | fraction |
| Azure Service Bus | Planning disk utilization | 0.8 | fraction |
| Azure Service Bus | Maintenance and log disk reserve | 20 | GiB |
| Azure Service Bus | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Azure Service Bus | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Azure Service Bus | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Azure Service Bus | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Azure Service Bus | Dependent object sink write price guess | 0.000005 | USD/write |

* 1-KiB messages, unbatched send/receive/delete; actual batch and delivery assumptions stay visible. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → East US, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Explicit tariff samples are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* Authored planning assumptions, not measured adapter capacity. Origin rates are cited first-tier list prices, before free allowances and discounts.
* A cost scenario does not establish backend availability, protocol fidelity or production readiness. Registry serving status remains independent.
* Storage follows resident original messages, not every monthly message. Broker delivery bytes include redeliveries.
* FIFO estimates do not qualify dedup support, group throughput or single-group latency; backend limitations remain applicable.
* Azure Service Bus Standard bills a namespace base charge that includes 13 million operations a month, then graduated per-operation prices: USD 0.80 per million to 100 million, 0.50 to 2,500 million and 0.20 beyond. An operation is any API call (send, receive, complete) per 64 KB of message; the family's managed operations count calls, not 64 KB units. Standard has no storage charge (queue size quota up to 5 GB is included). More than 1,000 brokered connections bill USD 0.03 per connection-month, which this profile does not model.
* AWS Price List API, AWSQueueService offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSQueueService/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSQueueService/current/us-east-1/index.json)
* Azure Retail Prices API: [https://prices.azure.com/api/retail/prices](https://prices.azure.com/api/retail/prices)

Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied.

Excluded costs and workload features:

* Additional network transfer, backups, KMS, one-time migration and operational labor unless an explicit meter includes them.
* Destination application execution and separately billed downstream services; supply those allocations separately.
* Taxes, discounts, credits and free-tier allowances unless explicitly reflected in edited rates.
* Unmodeled dependent services, task execution and operations outside the selected workload family.

List prices read: 2026-10-22. Model: `plan-ca45f8cb19ce07ffe770050ff2faf4e2ac2dad0b` / `2026-10-22.planning.2`. Curve: `workload-1`.

Sources: [AWS Price List API, AWSQueueService offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSQueueService/current/us-east-1/index.json), [Azure Retail Prices API](https://prices.azure.com/api/retail/prices).

## SQS Standard → OCI Queue

Origin API: `aws::1.0.0::sqs::classic`. Target backend: `oci::1.0.0::queue`.

### SQS Standard · SQS request billing units

Estimated monthly service charges by SQS request billing units. Adapter hosting and Tensor9 fees are excluded. Source: us-east-1; target: us-ashburn-1 (OCI global price list); currency: USD.

![SQS Standard · SQS request billing units: monthly service charges by SQS request billing units. Exact values are in the following table.](/images/diagrams/service-cost/28610e928ffd67b5ad1c75d6e3a1834fea71cb74cd07da5914284e28a53a8135-light.svg)

![SQS Standard · SQS request billing units: monthly service charges by SQS request billing units. Exact values are in the following table.](/images/diagrams/service-cost/f7ac8a53aa215d09033f0b423ca24c8b33b951540ac8a8aee914be033ea0f196-dark.svg)

Comparison pills describe all sampled scale points; card amounts show the named workload. Costs The Same means within 20% at every point. Costs Depend includes mixed results and unpriced samples.

Exact sampled model outputs in USD/month. Difference means target minus origin; a positive difference means the target costs more.

| SQS request billing units (per second) | SQS (Simple Queue Service, standard queues) | Target scenario | OCI Queue | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | OCI Queue | 0 | 0 |
| 1 | 1.0512 | OCI Queue | 0.35816 | -0.69304 |
| 10 | 10.512 | OCI Queue | 5.5616 | -4.9504 |
| 100 | 105.12 | OCI Queue | 57.596 | -47.524 |
| 1000 | 1051.2 | OCI Queue | 577.94 | -473.26 |
| 10000 | 10512 | OCI Queue | 5781.38 | -4730.62 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| OCI Queue | Origin list price · SQS billing units | 0.0000004 | USD/64-KiB request units |
| OCI Queue | Representative message size | 1024 | bytes |
| OCI Queue | Origin send batch fill | 1 | messages/request |
| OCI Queue | Origin receive batch fill | 1 | messages/request |
| OCI Queue | Origin delete batch fill | 1 | messages/request |
| OCI Queue | Deliveries per message | 1 | attempts |
| OCI Queue | Empty receive calls per message | 0 | requests |
| OCI Queue | Queue residence window | 60 | seconds |
| OCI Queue | Ordering and dedup work multiplier | 1 | multiplier |
| OCI Queue | Target price guess · read | 0 | USD/read |
| OCI Queue | Target price guess · write | 0 | USD/write |
| OCI Queue | Target list price · provider operation | 0.00000022 | USD/provider operation |
| OCI Queue | Target price guess · GiB-month | 0 | USD/GiB-month |
| OCI Queue | Target price guess · published GiB | 0 | USD/published GiB |
| OCI Queue | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| OCI Queue | Target price guess · network GiB | 0 | USD/network GiB |
| OCI Queue | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| OCI Queue | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| OCI Queue | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| OCI Queue | Target price guess · resource-hour | 0 | USD/resource-hour |
| OCI Queue | Target price guess · resource-month | 0 | USD/resource-month |
| OCI Queue | Target price guess · input token | 0 | USD/input token |
| OCI Queue | Target price guess · output token | 0 | USD/output token |
| OCI Queue | Included before billing · provider operation | 1000000 | provider operation |
| OCI Queue | Target monthly base charge | 0 | USD/month |
| OCI Queue | Approximate target service minimum | 0 | USD/month |
| OCI Queue | Minimum primary CPU | 2 | vCPU |
| OCI Queue | Minimum primary RAM | 8 | GiB |
| OCI Queue | Minimum primary disk | 100 | GiB |
| OCI Queue | Additional full-price standby copy | 0 | 0 or 1 |
| OCI Queue | Allocated share of provisioned cost | 1 | fraction |
| OCI Queue | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| OCI Queue | Planning peak / mean work | 2 | multiplier |
| OCI Queue | Planning primary CPU utilization | 0.7 | fraction |
| OCI Queue | Resident state reserved in RAM | 0.1 | fraction |
| OCI Queue | Planning disk utilization | 0.8 | fraction |
| OCI Queue | Maintenance and log disk reserve | 20 | GiB |
| OCI Queue | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| OCI Queue | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| OCI Queue | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| OCI Queue | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| OCI Queue | Dependent object sink write price guess | 0.000005 | USD/write |

* 1-KiB messages, unbatched send/receive/delete; actual batch and delivery assumptions stay visible. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → us-ashburn-1 (OCI global price list), USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Explicit tariff samples are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* Authored planning assumptions, not measured adapter capacity. Origin rates are cited first-tier list prices, before free allowances and discounts.
* A cost scenario does not establish backend availability, protocol fidelity or production readiness. Registry serving status remains independent.
* Storage follows resident original messages, not every monthly message. Broker delivery bytes include redeliveries.
* FIFO estimates do not qualify dedup support, group throughput or single-group latency; backend limitations remain applicable.
* OCI Queue bills requests after the first million each month; the price list counts each request as 64 KB, so larger messages or batches count as several requests, which the family's call counts do not multiply. Queue has no storage or retention charge.
* AWS Price List API, AWSQueueService offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSQueueService/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSQueueService/current/us-east-1/index.json)
* OCI price list API: [https://apexapps.oracle.com/pls/apex/cetools/api/v1/products/](https://apexapps.oracle.com/pls/apex/cetools/api/v1/products/)

Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied.

Excluded costs and workload features:

* Additional network transfer, backups, KMS, one-time migration and operational labor unless an explicit meter includes them.
* Destination application execution and separately billed downstream services; supply those allocations separately.
* Taxes, discounts, credits and free-tier allowances unless explicitly reflected in edited rates.
* Unmodeled dependent services, task execution and operations outside the selected workload family.

List prices read: 2026-10-22. Model: `plan-15dc11b20607d1fce76620d26b1597e97614129d` / `2026-10-22.planning.2`. Curve: `workload-1`.

Sources: [AWS Price List API, AWSQueueService offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSQueueService/current/us-east-1/index.json), [OCI price list API](https://apexapps.oracle.com/pls/apex/cetools/api/v1/products/).

## SQS Standard → PostgreSQL

Origin API: `aws::1.0.0::sqs::classic`. Target backend: `postgres::1.0.0::database`.

### SQS Standard · SQS request billing units

Estimated monthly service charges by SQS request billing units. Adapter hosting and Tensor9 fees are excluded. Source: us-east-1; target: us-central1; currency: USD.

![SQS Standard · SQS request billing units: monthly service charges by SQS request billing units. Exact values are in the following table.](/images/diagrams/service-cost/261fdc013a25c34589f57b76ba7b5b7fe824fe5ef0fd45939f23929c89069531-light.svg)

![SQS Standard · SQS request billing units: monthly service charges by SQS request billing units. Exact values are in the following table.](/images/diagrams/service-cost/23c1e651bfebba782ad8d042d3b216823658fc57915dd4d26143a8f38b74f007-dark.svg)

Comparison pills describe all sampled scale points; card amounts show the named workload. Costs The Same means within 20% at every point. Costs Depend includes mixed results and unpriced samples.

Exact sampled model outputs in USD/month. Difference means target minus origin; a positive difference means the target costs more.
Estimated allocation from planning assumptions; not benchmark calibrated. Lines connect evaluated samples; intermediate capacity and prices are not inferred. Unpriced means no target quote or cost difference is available within the sizing policy.

| SQS request billing units (per second) | SQS (Simple Queue Service, standard queues) | Target scenario | PostgreSQL | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | PostgreSQL (one copy) | 80.89614 | 80.89614 |
| 0 | 0 | PostgreSQL (two copies) | 161.79228 | 161.79228 |
| 1 | 1.0512 | PostgreSQL (one copy) | 80.89614 | 79.84494 |
| 1 | 1.0512 | PostgreSQL (two copies) | 161.79228 | 160.74108 |
| 10 | 10.512 | PostgreSQL (one copy) | 80.89614 | 70.38414 |
| 10 | 10.512 | PostgreSQL (two copies) | 161.79228 | 151.28028 |
| 100 | 105.12 | PostgreSQL (one copy) | 80.89614 | -24.22386 |
| 100 | 105.12 | PostgreSQL (two copies) | 161.79228 | 56.67228 |
| 1000 | 1051.2 | PostgreSQL (one copy) | 151.79228 | -899.40772 |
| 1000 | 1051.2 | PostgreSQL (two copies) | 303.58456 | -747.61544 |
| 10000 | 10512 | PostgreSQL (one copy) | 1144.33824 | -9367.66176 |
| 10000 | 10512 | PostgreSQL (two copies) | 2288.67648 | -8223.32352 |

**Estimated allocation from planning assumptions; not benchmark calibrated.**

The sizing policy grows compute with translated work and peak headroom, memory with compute and working set, and disk with resident working state and reserve. Monthly usage is distinct from resident data; each workload's assumptions define the translation. HA changes pricing, not this policy's throughput estimate. Unpriced workloads exceed the policy's configuration range; no silent vertical cap or automatic sharding is assumed.

| Sample / scenario | Basis | Mean / peak work/s | Required vCPU | Allocated vCPU | Memory GiB | SSD GiB | Resident GiB | Policy | Constraints |
| - | - | -: | -: | -: | -: | -: | -: | - | - |
| 0 per second / PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 0 per second / PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1 per second / PostgreSQL (one copy) | PlanningAssumption | 1.333333333333333333333333333333333 / 2.666666666666666666666666666666666 | 0.002539682539682539682539682539682539 | 2 | 8 | 100 | 0.000019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1 per second / PostgreSQL (two copies) | PlanningAssumption | 1.333333333333333333333333333333333 / 2.666666666666666666666666666666666 | 0.002539682539682539682539682539682539 | 2 | 8 | 100 | 0.000019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 per second / PostgreSQL (one copy) | PlanningAssumption | 13.33333333333333333333333333333333 / 26.66666666666666666666666666666666 | 0.02539682539682539682539682539682539 | 2 | 8 | 100 | 0.00019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 per second / PostgreSQL (two copies) | PlanningAssumption | 13.33333333333333333333333333333333 / 26.66666666666666666666666666666666 | 0.02539682539682539682539682539682539 | 2 | 8 | 100 | 0.00019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 per second / PostgreSQL (one copy) | PlanningAssumption | 133.3333333333333333333333333333333 / 266.6666666666666666666666666666666 | 0.2539682539682539682539682539682539 | 2 | 8 | 100 | 0.0019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 per second / PostgreSQL (two copies) | PlanningAssumption | 133.3333333333333333333333333333333 / 266.6666666666666666666666666666666 | 0.2539682539682539682539682539682539 | 2 | 8 | 100 | 0.0019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 per second / PostgreSQL (one copy) | PlanningAssumption | 1333.333333333333333333333333333333 / 2666.666666666666666666666666666666 | 2.539682539682539682539682539682539 | 4 | 16 | 100 | 0.019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 per second / PostgreSQL (two copies) | PlanningAssumption | 1333.333333333333333333333333333333 / 2666.666666666666666666666666666666 | 2.539682539682539682539682539682539 | 4 | 16 | 100 | 0.019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 per second / PostgreSQL (one copy) | PlanningAssumption | 13333.33333333333333333333333333333 / 26666.66666666666666666666666666666 | 25.39682539682539682539682539682539 | 32 | 128 | 100 | 0.19073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 per second / PostgreSQL (two copies) | PlanningAssumption | 13333.33333333333333333333333333333 / 26666.66666666666666666666666666666 | 25.39682539682539682539682539682539 | 32 | 128 | 100 | 0.19073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |

* Row-store throughput (capacityOpsPerVcpuSecond, default 1500) is measured-by-tensor9 as a lower bound: the DynamoDB adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) served 2,974 ops/s of YCSB-A at 16 threads without recorded saturation (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlPostgresqlYcsbAT16GoYcsbV1\_0\_0.kt). Published CPU-bound pgbench reaches 3,101 read-write transactions and 20,289 point reads per vCPU-second (AWS z1d.2xlarge, PostgreSQL 14.5), so actual capacity is likely higher. Reads and writes share one coefficient: at the same adapter version, read-only YCSB-C was not faster than 50%-update YCSB-A.
* Log-broker throughput (capacityStreamMiBPerVcpuSecond 20 at 0.5 utilization, 4 GiB RAM per vCPU) is provider-documented by Google Managed Service for Apache Kafka sizing ([https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size](https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size)): write-equivalent bytes are replicated writes plus a quarter of reads. Producer batches below 10 KB lower per-CPU throughput; that penalty is not modeled.
* Disk utilization 0.8 is provider-documented headroom below Cloud SQL automatic storage increase, which triggers near 91-95% full ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)). The 20 GiB reserve exceeds PostgreSQL's 1 GB default max\_wal\_size; the remainder of that reserve is unmeasured.
* CPU tiers, 4 GiB per vCPU, at most 6.5 GiB per vCPU, 96 vCPU and 65,536 GiB disk follow Cloud SQL Enterprise custom machine limits (provider-documented, same page); 624 GiB is 96 × 6.5. Targets billed per node, unit or throughput unit are sized by their backend instead.
* No public evidence: peak/mean work (2) and the RAM working-set fraction (0.1). Proposed measurements: the p99 one-minute rate over the monthly mean from customer CloudWatch metrics; the buffer hit ratio while stepping RAM under a fixed YCSB-B load.
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| PostgreSQL (one copy) | Origin list price · SQS billing units | 0.0000004 | USD/64-KiB request units |
| PostgreSQL (one copy) | Representative message size | 1024 | bytes |
| PostgreSQL (one copy) | Origin send batch fill | 1 | messages/request |
| PostgreSQL (one copy) | Origin receive batch fill | 1 | messages/request |
| PostgreSQL (one copy) | Origin delete batch fill | 1 | messages/request |
| PostgreSQL (one copy) | Deliveries per message | 1 | attempts |
| PostgreSQL (one copy) | Empty receive calls per message | 0 | requests |
| PostgreSQL (one copy) | Queue residence window | 60 | seconds |
| PostgreSQL (one copy) | Ordering and dedup work multiplier | 1 | multiplier |
| PostgreSQL (one copy) | Target price guess · read | 0 | USD/read |
| PostgreSQL (one copy) | Target price guess · write | 0 | USD/write |
| PostgreSQL (one copy) | Target price guess · provider operation | 0 | USD/provider operation |
| PostgreSQL (one copy) | Target list price · GiB-month | 0.1 | USD/GiB-month |
| PostgreSQL (one copy) | Target price guess · published GiB | 0 | USD/published GiB |
| PostgreSQL (one copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| PostgreSQL (one copy) | Target list price · network GiB | 0.12 | USD/network GiB |
| PostgreSQL (one copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| PostgreSQL (one copy) | Target list price · vCPU-hour | 0.031611 | USD/vCPU-hour |
| PostgreSQL (one copy) | Target list price · GiB-hour | 0.004237 | USD/GiB-hour |
| PostgreSQL (one copy) | Target price guess · resource-hour | 0 | USD/resource-hour |
| PostgreSQL (one copy) | Target price guess · resource-month | 0 | USD/resource-month |
| PostgreSQL (one copy) | Target price guess · input token | 0 | USD/input token |
| PostgreSQL (one copy) | Target price guess · output token | 0 | USD/output token |
| PostgreSQL (one copy) | Target monthly base charge | 0 | USD/month |
| PostgreSQL (one copy) | Approximate target service minimum | 0 | USD/month |
| PostgreSQL (one copy) | Minimum primary CPU | 2 | vCPU |
| PostgreSQL (one copy) | Minimum primary RAM | 8 | GiB |
| PostgreSQL (one copy) | Minimum primary disk | 100 | GiB |
| PostgreSQL (one copy) | Additional full-price standby copy | 0 | 0 or 1 |
| PostgreSQL (one copy) | Allocated share of provisioned cost | 1 | fraction |
| PostgreSQL (one copy) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| PostgreSQL (one copy) | Planning peak / mean work | 2 | multiplier |
| PostgreSQL (one copy) | Planning primary CPU utilization | 0.7 | fraction |
| PostgreSQL (one copy) | Resident state reserved in RAM | 0.1 | fraction |
| PostgreSQL (one copy) | Planning disk utilization | 0.8 | fraction |
| PostgreSQL (one copy) | Maintenance and log disk reserve | 20 | GiB |
| PostgreSQL (one copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| PostgreSQL (one copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| PostgreSQL (one copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| PostgreSQL (one copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| PostgreSQL (one copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| PostgreSQL (two copies) | Origin list price · SQS billing units | 0.0000004 | USD/64-KiB request units |
| PostgreSQL (two copies) | Representative message size | 1024 | bytes |
| PostgreSQL (two copies) | Origin send batch fill | 1 | messages/request |
| PostgreSQL (two copies) | Origin receive batch fill | 1 | messages/request |
| PostgreSQL (two copies) | Origin delete batch fill | 1 | messages/request |
| PostgreSQL (two copies) | Deliveries per message | 1 | attempts |
| PostgreSQL (two copies) | Empty receive calls per message | 0 | requests |
| PostgreSQL (two copies) | Queue residence window | 60 | seconds |
| PostgreSQL (two copies) | Ordering and dedup work multiplier | 1 | multiplier |
| PostgreSQL (two copies) | Target price guess · read | 0 | USD/read |
| PostgreSQL (two copies) | Target price guess · write | 0 | USD/write |
| PostgreSQL (two copies) | Target price guess · provider operation | 0 | USD/provider operation |
| PostgreSQL (two copies) | Target list price · GiB-month | 0.1 | USD/GiB-month |
| PostgreSQL (two copies) | Target price guess · published GiB | 0 | USD/published GiB |
| PostgreSQL (two copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| PostgreSQL (two copies) | Target list price · network GiB | 0.12 | USD/network GiB |
| PostgreSQL (two copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| PostgreSQL (two copies) | Target list price · vCPU-hour | 0.031611 | USD/vCPU-hour |
| PostgreSQL (two copies) | Target list price · GiB-hour | 0.004237 | USD/GiB-hour |
| PostgreSQL (two copies) | Target price guess · resource-hour | 0 | USD/resource-hour |
| PostgreSQL (two copies) | Target price guess · resource-month | 0 | USD/resource-month |
| PostgreSQL (two copies) | Target price guess · input token | 0 | USD/input token |
| PostgreSQL (two copies) | Target price guess · output token | 0 | USD/output token |
| PostgreSQL (two copies) | Target monthly base charge | 0 | USD/month |
| PostgreSQL (two copies) | Approximate target service minimum | 0 | USD/month |
| PostgreSQL (two copies) | Minimum primary CPU | 2 | vCPU |
| PostgreSQL (two copies) | Minimum primary RAM | 8 | GiB |
| PostgreSQL (two copies) | Minimum primary disk | 100 | GiB |
| PostgreSQL (two copies) | Additional full-price standby copy | 1 | 0 or 1 |
| PostgreSQL (two copies) | Allocated share of provisioned cost | 1 | fraction |
| PostgreSQL (two copies) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| PostgreSQL (two copies) | Planning peak / mean work | 2 | multiplier |
| PostgreSQL (two copies) | Planning primary CPU utilization | 0.7 | fraction |
| PostgreSQL (two copies) | Resident state reserved in RAM | 0.1 | fraction |
| PostgreSQL (two copies) | Planning disk utilization | 0.8 | fraction |
| PostgreSQL (two copies) | Maintenance and log disk reserve | 20 | GiB |
| PostgreSQL (two copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| PostgreSQL (two copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| PostgreSQL (two copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| PostgreSQL (two copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| PostgreSQL (two copies) | Dependent object sink write price guess | 0.000005 | USD/write |

* 1-KiB messages, unbatched send/receive/delete; actual batch and delivery assumptions stay visible. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → us-central1, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Explicit tariff samples are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* Authored planning assumptions, not measured adapter capacity. Origin rates are cited first-tier list prices, before free allowances and discounts.
* A cost scenario does not establish backend availability, protocol fidelity or production readiness. Registry serving status remains independent.
* Storage follows resident original messages, not every monthly message. Broker delivery bytes include redeliveries.
* FIFO estimates do not qualify dedup support, group throughput or single-group latency; backend limitations remain applicable.
* Self-hosted target: PostgreSQL (PostgreSQL License, [https://www.postgresql.org/about/licence/](https://www.postgresql.org/about/licence/)). Selected CPU, RAM and physical disk allocation grow with workload; no per-operation price is assumed. No vendor tariff: the target runs on the customer's Kubernetes nodes, so CPU, RAM and disk bill at the Kubernetes node reference rates, Compute Engine N2 in us-central1 (USD 0.031611/vCPU-hour, 0.004237/GiB-hour) with pd-balanced disk (0.10/GiB-month) and Premium Tier egress. The cost-optimized E2 series lists 0.02181159/vCPU-hour and 0.00292353/GiB-hour; AWS m6i/r6i and Azure D2s v5/E2s v5 both decompose to 0.033/vCPU-hour and 0.00375/GiB-hour. Requested CPU and RAM are billed; node bin-packing waste, system reservations and the cluster control-plane fee are not.
* Row-store throughput (capacityOpsPerVcpuSecond, default 1500) is measured-by-tensor9 as a lower bound: the DynamoDB adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) served 2,974 ops/s of YCSB-A at 16 threads without recorded saturation (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlPostgresqlYcsbAT16GoYcsbV1\_0\_0.kt). Published CPU-bound pgbench reaches 3,101 read-write transactions and 20,289 point reads per vCPU-second (AWS z1d.2xlarge, PostgreSQL 14.5), so actual capacity is likely higher. Reads and writes share one coefficient: at the same adapter version, read-only YCSB-C was not faster than 50%-update YCSB-A.
* Log-broker throughput (capacityStreamMiBPerVcpuSecond 20 at 0.5 utilization, 4 GiB RAM per vCPU) is provider-documented by Google Managed Service for Apache Kafka sizing ([https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size](https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size)): write-equivalent bytes are replicated writes plus a quarter of reads. Producer batches below 10 KB lower per-CPU throughput; that penalty is not modeled.
* Disk utilization 0.8 is provider-documented headroom below Cloud SQL automatic storage increase, which triggers near 91-95% full ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)). The 20 GiB reserve exceeds PostgreSQL's 1 GB default max\_wal\_size; the remainder of that reserve is unmeasured.
* CPU tiers, 4 GiB per vCPU, at most 6.5 GiB per vCPU, 96 vCPU and 65,536 GiB disk follow Cloud SQL Enterprise custom machine limits (provider-documented, same page); 624 GiB is 96 × 6.5. Targets billed per node, unit or throughput unit are sized by their backend instead.
* No public evidence: peak/mean work (2) and the RAM working-set fraction (0.1). Proposed measurements: the p99 one-minute rate over the monthly mean from customer CloudWatch metrics; the buffer hit ratio while stepping RAM under a fixed YCSB-B load.
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* AWS Price List API, AWSQueueService offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSQueueService/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSQueueService/current/us-east-1/index.json)
* Compute Engine general-purpose machine pricing: [https://cloud.google.com/products/compute/pricing/general-purpose](https://cloud.google.com/products/compute/pricing/general-purpose)
* Disk and image pricing: [https://cloud.google.com/compute/disks-image-pricing](https://cloud.google.com/compute/disks-image-pricing)
* Network pricing: [https://cloud.google.com/vpc/network-pricing](https://cloud.google.com/vpc/network-pricing)

Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied.

Excluded costs and workload features:

* Additional network transfer, backups, KMS, one-time migration and operational labor unless an explicit meter includes them.
* Destination application execution and separately billed downstream services; supply those allocations separately.
* Taxes, discounts, credits and free-tier allowances unless explicitly reflected in edited rates.
* Unmodeled dependent services, task execution and operations outside the selected workload family.

List prices read: 2026-10-22. Model: `plan-a5003d6d1b075ed4d7688651bd5e72c32088cf9c` / `2026-10-22.planning.2`. Curve: `workload-1`.

Sources: [AWS Price List API, AWSQueueService offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSQueueService/current/us-east-1/index.json), [Compute Engine general-purpose machine pricing](https://cloud.google.com/products/compute/pricing/general-purpose), [Disk and image pricing](https://cloud.google.com/compute/disks-image-pricing), [Network pricing](https://cloud.google.com/vpc/network-pricing).

## SQS Standard → PostgreSQL Flexible Server

Origin API: `aws::1.0.0::sqs::classic`. Target backend: `azure::1.0.0::postgresql::flexible`.

### SQS Standard · SQS request billing units

Estimated monthly service charges by SQS request billing units. Adapter hosting and Tensor9 fees are excluded. Source: us-east-1; target: eastus; currency: USD.

![SQS Standard · SQS request billing units: monthly service charges by SQS request billing units. Exact values are in the following table.](/images/diagrams/service-cost/4824fadbfa929dc65cffbb72e922aa90d5a3466c3ac4bd644439e0baa60d23e9-light.svg)

![SQS Standard · SQS request billing units: monthly service charges by SQS request billing units. Exact values are in the following table.](/images/diagrams/service-cost/b6ed9b816e9f9caececd2e765c89e840bfbf134d9a0b11afcb94da77468a527b-dark.svg)

Comparison pills describe all sampled scale points; card amounts show the named workload. Costs The Same means within 20% at every point. Costs Depend includes mixed results and unpriced samples.

Exact sampled model outputs in USD/month. Difference means target minus origin; a positive difference means the target costs more.
Estimated allocation from planning assumptions; not benchmark calibrated. Lines connect evaluated samples; intermediate capacity and prices are not inferred. Unpriced means no target quote or cost difference is available within the sizing policy.

| SQS request billing units (per second) | SQS (Simple Queue Service, standard queues) | Target scenario | PostgreSQL Flexible Server | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | PostgreSQL Flexible Server (one copy) | 141.44 | 141.44 |
| 0 | 0 | PostgreSQL Flexible Server (two copies) | 282.88 | 282.88 |
| 1 | 1.0512 | PostgreSQL Flexible Server (one copy) | 141.44 | 140.3888 |
| 1 | 1.0512 | PostgreSQL Flexible Server (two copies) | 282.88 | 281.8288 |
| 10 | 10.512 | PostgreSQL Flexible Server (one copy) | 141.44 | 130.928 |
| 10 | 10.512 | PostgreSQL Flexible Server (two copies) | 282.88 | 272.368 |
| 100 | 105.12 | PostgreSQL Flexible Server (one copy) | 141.44 | 36.32 |
| 100 | 105.12 | PostgreSQL Flexible Server (two copies) | 282.88 | 177.76 |
| 1000 | 1051.2 | PostgreSQL Flexible Server (one copy) | 271.38 | -779.82 |
| 1000 | 1051.2 | PostgreSQL Flexible Server (two copies) | 542.76 | -508.44 |
| 10000 | 10512 | PostgreSQL Flexible Server (one copy) | 2090.54 | -8421.46 |
| 10000 | 10512 | PostgreSQL Flexible Server (two copies) | 4181.08 | -6330.92 |

**Estimated allocation from planning assumptions; not benchmark calibrated.**

The sizing policy grows compute with translated work and peak headroom, memory with compute and working set, and disk with resident working state and reserve. Monthly usage is distinct from resident data; each workload's assumptions define the translation. HA changes pricing, not this policy's throughput estimate. Unpriced workloads exceed the policy's configuration range; no silent vertical cap or automatic sharding is assumed.

| Sample / scenario | Basis | Mean / peak work/s | Required vCPU | Allocated vCPU | Memory GiB | SSD GiB | Resident GiB | Policy | Constraints |
| - | - | -: | -: | -: | -: | -: | -: | - | - |
| 0 per second / PostgreSQL Flexible Server (one copy) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 0 per second / PostgreSQL Flexible Server (two copies) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1 per second / PostgreSQL Flexible Server (one copy) | PlanningAssumption | 1.333333333333333333333333333333333 / 2.666666666666666666666666666666666 | 0.002539682539682539682539682539682539 | 2 | 8 | 100 | 0.000019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1 per second / PostgreSQL Flexible Server (two copies) | PlanningAssumption | 1.333333333333333333333333333333333 / 2.666666666666666666666666666666666 | 0.002539682539682539682539682539682539 | 2 | 8 | 100 | 0.000019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 per second / PostgreSQL Flexible Server (one copy) | PlanningAssumption | 13.33333333333333333333333333333333 / 26.66666666666666666666666666666666 | 0.02539682539682539682539682539682539 | 2 | 8 | 100 | 0.00019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 per second / PostgreSQL Flexible Server (two copies) | PlanningAssumption | 13.33333333333333333333333333333333 / 26.66666666666666666666666666666666 | 0.02539682539682539682539682539682539 | 2 | 8 | 100 | 0.00019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 per second / PostgreSQL Flexible Server (one copy) | PlanningAssumption | 133.3333333333333333333333333333333 / 266.6666666666666666666666666666666 | 0.2539682539682539682539682539682539 | 2 | 8 | 100 | 0.0019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 per second / PostgreSQL Flexible Server (two copies) | PlanningAssumption | 133.3333333333333333333333333333333 / 266.6666666666666666666666666666666 | 0.2539682539682539682539682539682539 | 2 | 8 | 100 | 0.0019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 per second / PostgreSQL Flexible Server (one copy) | PlanningAssumption | 1333.333333333333333333333333333333 / 2666.666666666666666666666666666666 | 2.539682539682539682539682539682539 | 4 | 16 | 100 | 0.019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 per second / PostgreSQL Flexible Server (two copies) | PlanningAssumption | 1333.333333333333333333333333333333 / 2666.666666666666666666666666666666 | 2.539682539682539682539682539682539 | 4 | 16 | 100 | 0.019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 per second / PostgreSQL Flexible Server (one copy) | PlanningAssumption | 13333.33333333333333333333333333333 / 26666.66666666666666666666666666666 | 25.39682539682539682539682539682539 | 32 | 128 | 100 | 0.19073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 per second / PostgreSQL Flexible Server (two copies) | PlanningAssumption | 13333.33333333333333333333333333333 / 26666.66666666666666666666666666666 | 25.39682539682539682539682539682539 | 32 | 128 | 100 | 0.19073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |

* Row-store throughput (capacityOpsPerVcpuSecond, default 1500) is measured-by-tensor9 as a lower bound: the DynamoDB adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) served 2,974 ops/s of YCSB-A at 16 threads without recorded saturation (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlPostgresqlYcsbAT16GoYcsbV1\_0\_0.kt). Published CPU-bound pgbench reaches 3,101 read-write transactions and 20,289 point reads per vCPU-second (AWS z1d.2xlarge, PostgreSQL 14.5), so actual capacity is likely higher. Reads and writes share one coefficient: at the same adapter version, read-only YCSB-C was not faster than 50%-update YCSB-A.
* Log-broker throughput (capacityStreamMiBPerVcpuSecond 20 at 0.5 utilization, 4 GiB RAM per vCPU) is provider-documented by Google Managed Service for Apache Kafka sizing ([https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size](https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size)): write-equivalent bytes are replicated writes plus a quarter of reads. Producer batches below 10 KB lower per-CPU throughput; that penalty is not modeled.
* Disk utilization 0.8 is provider-documented headroom below Cloud SQL automatic storage increase, which triggers near 91-95% full ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)). The 20 GiB reserve exceeds PostgreSQL's 1 GB default max\_wal\_size; the remainder of that reserve is unmeasured.
* CPU tiers, 4 GiB per vCPU, at most 6.5 GiB per vCPU, 96 vCPU and 65,536 GiB disk follow Cloud SQL Enterprise custom machine limits (provider-documented, same page); 624 GiB is 96 × 6.5. Targets billed per node, unit or throughput unit are sized by their backend instead.
* No public evidence: peak/mean work (2) and the RAM working-set fraction (0.1). Proposed measurements: the p99 one-minute rate over the monthly mean from customer CloudWatch metrics; the buffer hit ratio while stepping RAM under a fixed YCSB-B load.
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| PostgreSQL Flexible Server (one copy) | Origin list price · SQS billing units | 0.0000004 | USD/64-KiB request units |
| PostgreSQL Flexible Server (one copy) | Representative message size | 1024 | bytes |
| PostgreSQL Flexible Server (one copy) | Origin send batch fill | 1 | messages/request |
| PostgreSQL Flexible Server (one copy) | Origin receive batch fill | 1 | messages/request |
| PostgreSQL Flexible Server (one copy) | Origin delete batch fill | 1 | messages/request |
| PostgreSQL Flexible Server (one copy) | Deliveries per message | 1 | attempts |
| PostgreSQL Flexible Server (one copy) | Empty receive calls per message | 0 | requests |
| PostgreSQL Flexible Server (one copy) | Queue residence window | 60 | seconds |
| PostgreSQL Flexible Server (one copy) | Ordering and dedup work multiplier | 1 | multiplier |
| PostgreSQL Flexible Server (one copy) | Target price guess · read | 0 | USD/read |
| PostgreSQL Flexible Server (one copy) | Target price guess · write | 0 | USD/write |
| PostgreSQL Flexible Server (one copy) | Target price guess · provider operation | 0 | USD/provider operation |
| PostgreSQL Flexible Server (one copy) | Target list price · GiB-month | 0.115 | USD/GiB-month |
| PostgreSQL Flexible Server (one copy) | Target price guess · published GiB | 0 | USD/published GiB |
| PostgreSQL Flexible Server (one copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| PostgreSQL Flexible Server (one copy) | Target list price · network GiB | 0.087 | USD/network GiB |
| PostgreSQL Flexible Server (one copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| PostgreSQL Flexible Server (one copy) | Target list price · vCPU-hour | 0.053 | USD/vCPU-hour |
| PostgreSQL Flexible Server (one copy) | Target list price · GiB-hour | 0.009 | USD/GiB-hour |
| PostgreSQL Flexible Server (one copy) | Target price guess · resource-hour | 0 | USD/resource-hour |
| PostgreSQL Flexible Server (one copy) | Target price guess · resource-month | 0 | USD/resource-month |
| PostgreSQL Flexible Server (one copy) | Target price guess · input token | 0 | USD/input token |
| PostgreSQL Flexible Server (one copy) | Target price guess · output token | 0 | USD/output token |
| PostgreSQL Flexible Server (one copy) | Target monthly base charge | 0 | USD/month |
| PostgreSQL Flexible Server (one copy) | Target service minimum | 16.09 | USD/month |
| PostgreSQL Flexible Server (one copy) | Minimum primary CPU | 2 | vCPU |
| PostgreSQL Flexible Server (one copy) | Minimum primary RAM | 8 | GiB |
| PostgreSQL Flexible Server (one copy) | Minimum primary disk | 100 | GiB |
| PostgreSQL Flexible Server (one copy) | Additional full-price standby copy | 0 | 0 or 1 |
| PostgreSQL Flexible Server (one copy) | Allocated share of provisioned cost | 1 | fraction |
| PostgreSQL Flexible Server (one copy) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| PostgreSQL Flexible Server (one copy) | Planning peak / mean work | 2 | multiplier |
| PostgreSQL Flexible Server (one copy) | Planning primary CPU utilization | 0.7 | fraction |
| PostgreSQL Flexible Server (one copy) | Resident state reserved in RAM | 0.1 | fraction |
| PostgreSQL Flexible Server (one copy) | Planning disk utilization | 0.8 | fraction |
| PostgreSQL Flexible Server (one copy) | Maintenance and log disk reserve | 20 | GiB |
| PostgreSQL Flexible Server (one copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| PostgreSQL Flexible Server (one copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| PostgreSQL Flexible Server (one copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| PostgreSQL Flexible Server (one copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| PostgreSQL Flexible Server (one copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| PostgreSQL Flexible Server (two copies) | Origin list price · SQS billing units | 0.0000004 | USD/64-KiB request units |
| PostgreSQL Flexible Server (two copies) | Representative message size | 1024 | bytes |
| PostgreSQL Flexible Server (two copies) | Origin send batch fill | 1 | messages/request |
| PostgreSQL Flexible Server (two copies) | Origin receive batch fill | 1 | messages/request |
| PostgreSQL Flexible Server (two copies) | Origin delete batch fill | 1 | messages/request |
| PostgreSQL Flexible Server (two copies) | Deliveries per message | 1 | attempts |
| PostgreSQL Flexible Server (two copies) | Empty receive calls per message | 0 | requests |
| PostgreSQL Flexible Server (two copies) | Queue residence window | 60 | seconds |
| PostgreSQL Flexible Server (two copies) | Ordering and dedup work multiplier | 1 | multiplier |
| PostgreSQL Flexible Server (two copies) | Target price guess · read | 0 | USD/read |
| PostgreSQL Flexible Server (two copies) | Target price guess · write | 0 | USD/write |
| PostgreSQL Flexible Server (two copies) | Target price guess · provider operation | 0 | USD/provider operation |
| PostgreSQL Flexible Server (two copies) | Target list price · GiB-month | 0.115 | USD/GiB-month |
| PostgreSQL Flexible Server (two copies) | Target price guess · published GiB | 0 | USD/published GiB |
| PostgreSQL Flexible Server (two copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| PostgreSQL Flexible Server (two copies) | Target list price · network GiB | 0.087 | USD/network GiB |
| PostgreSQL Flexible Server (two copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| PostgreSQL Flexible Server (two copies) | Target list price · vCPU-hour | 0.053 | USD/vCPU-hour |
| PostgreSQL Flexible Server (two copies) | Target list price · GiB-hour | 0.009 | USD/GiB-hour |
| PostgreSQL Flexible Server (two copies) | Target price guess · resource-hour | 0 | USD/resource-hour |
| PostgreSQL Flexible Server (two copies) | Target price guess · resource-month | 0 | USD/resource-month |
| PostgreSQL Flexible Server (two copies) | Target price guess · input token | 0 | USD/input token |
| PostgreSQL Flexible Server (two copies) | Target price guess · output token | 0 | USD/output token |
| PostgreSQL Flexible Server (two copies) | Target monthly base charge | 0 | USD/month |
| PostgreSQL Flexible Server (two copies) | Target service minimum | 16.09 | USD/month |
| PostgreSQL Flexible Server (two copies) | Minimum primary CPU | 2 | vCPU |
| PostgreSQL Flexible Server (two copies) | Minimum primary RAM | 8 | GiB |
| PostgreSQL Flexible Server (two copies) | Minimum primary disk | 100 | GiB |
| PostgreSQL Flexible Server (two copies) | Additional full-price standby copy | 1 | 0 or 1 |
| PostgreSQL Flexible Server (two copies) | Allocated share of provisioned cost | 1 | fraction |
| PostgreSQL Flexible Server (two copies) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| PostgreSQL Flexible Server (two copies) | Planning peak / mean work | 2 | multiplier |
| PostgreSQL Flexible Server (two copies) | Planning primary CPU utilization | 0.7 | fraction |
| PostgreSQL Flexible Server (two copies) | Resident state reserved in RAM | 0.1 | fraction |
| PostgreSQL Flexible Server (two copies) | Planning disk utilization | 0.8 | fraction |
| PostgreSQL Flexible Server (two copies) | Maintenance and log disk reserve | 20 | GiB |
| PostgreSQL Flexible Server (two copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| PostgreSQL Flexible Server (two copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| PostgreSQL Flexible Server (two copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| PostgreSQL Flexible Server (two copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| PostgreSQL Flexible Server (two copies) | Dependent object sink write price guess | 0.000005 | USD/write |

* 1-KiB messages, unbatched send/receive/delete; actual batch and delivery assumptions stay visible. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → eastus, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Explicit tariff samples are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* Authored planning assumptions, not measured adapter capacity. Origin rates are cited first-tier list prices, before free allowances and discounts.
* A cost scenario does not establish backend availability, protocol fidelity or production readiness. Registry serving status remains independent.
* Storage follows resident original messages, not every monthly message. Broker delivery bytes include redeliveries.
* FIFO estimates do not qualify dedup support, group throughput or single-group latency; backend limitations remain applicable.
* Azure Database for PostgreSQL Flexible Server bills vCores with a fixed memory ratio per series; the vCPU and memory rates decompose the General Purpose and Memory Optimized v5 prices. High availability bills the standby's compute and storage as a second copy. The minimum is the smallest Burstable server, which does not support high availability; the smallest General Purpose server (2 vCores) costs USD 133.62 per month. Additional IOPS, backup storage and reserved capacity are not selected.
* Row-store throughput (capacityOpsPerVcpuSecond, default 1500) is measured-by-tensor9 as a lower bound: the DynamoDB adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) served 2,974 ops/s of YCSB-A at 16 threads without recorded saturation (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlPostgresqlYcsbAT16GoYcsbV1\_0\_0.kt). Published CPU-bound pgbench reaches 3,101 read-write transactions and 20,289 point reads per vCPU-second (AWS z1d.2xlarge, PostgreSQL 14.5), so actual capacity is likely higher. Reads and writes share one coefficient: at the same adapter version, read-only YCSB-C was not faster than 50%-update YCSB-A.
* Log-broker throughput (capacityStreamMiBPerVcpuSecond 20 at 0.5 utilization, 4 GiB RAM per vCPU) is provider-documented by Google Managed Service for Apache Kafka sizing ([https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size](https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size)): write-equivalent bytes are replicated writes plus a quarter of reads. Producer batches below 10 KB lower per-CPU throughput; that penalty is not modeled.
* Disk utilization 0.8 is provider-documented headroom below Cloud SQL automatic storage increase, which triggers near 91-95% full ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)). The 20 GiB reserve exceeds PostgreSQL's 1 GB default max\_wal\_size; the remainder of that reserve is unmeasured.
* CPU tiers, 4 GiB per vCPU, at most 6.5 GiB per vCPU, 96 vCPU and 65,536 GiB disk follow Cloud SQL Enterprise custom machine limits (provider-documented, same page); 624 GiB is 96 × 6.5. Targets billed per node, unit or throughput unit are sized by their backend instead.
* No public evidence: peak/mean work (2) and the RAM working-set fraction (0.1). Proposed measurements: the p99 one-minute rate over the monthly mean from customer CloudWatch metrics; the buffer hit ratio while stepping RAM under a fixed YCSB-B load.
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* AWS Price List API, AWSQueueService offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSQueueService/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSQueueService/current/us-east-1/index.json)
* Azure Retail Prices API: [https://prices.azure.com/api/retail/prices](https://prices.azure.com/api/retail/prices)

Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied.

Excluded costs and workload features:

* Additional network transfer, backups, KMS, one-time migration and operational labor unless an explicit meter includes them.
* Destination application execution and separately billed downstream services; supply those allocations separately.
* Taxes, discounts, credits and free-tier allowances unless explicitly reflected in edited rates.
* Unmodeled dependent services, task execution and operations outside the selected workload family.

List prices read: 2026-10-22. Model: `plan-89783f4d5bd47a02bac1ee1d677521ebf845f89c` / `2026-10-22.planning.2`. Curve: `workload-1`.

Sources: [AWS Price List API, AWSQueueService offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSQueueService/current/us-east-1/index.json), [Azure Retail Prices API](https://prices.azure.com/api/retail/prices).

## SQS Standard → Scaleway Managed Database for PostgreSQL

Origin API: `aws::1.0.0::sqs::classic`. Target backend: `scaleway::1.0.0::rdb::postgresql`.

### SQS Standard · SQS request billing units

Estimated monthly service charges by SQS request billing units. Adapter hosting and Tensor9 fees are excluded. Source: us-east-1; target: fr-par; currency: USD.

![SQS Standard · SQS request billing units: monthly service charges by SQS request billing units. Exact values are in the following table.](/images/diagrams/service-cost/1ae77b53c009c4ff1184113ff1aed34b1a9e441eb17d984669a23e6639c5b74c-light.svg)

![SQS Standard · SQS request billing units: monthly service charges by SQS request billing units. Exact values are in the following table.](/images/diagrams/service-cost/7e20a31a0f916ae8055b915abaed329c9cf0507dd6fdd7edb53c43edca4cc6cf-dark.svg)

Comparison pills describe all sampled scale points; card amounts show the named workload. Costs The Same means within 20% at every point. Costs Depend includes mixed results and unpriced samples.

Exact sampled model outputs in USD/month. Difference means target minus origin; a positive difference means the target costs more.
Estimated allocation from planning assumptions; not benchmark calibrated. Lines connect evaluated samples; intermediate capacity and prices are not inferred. Unpriced means no target quote or cost difference is available within the sizing policy.

| SQS request billing units (per second) | SQS (Simple Queue Service, standard queues) | Target scenario | Scaleway Managed Database for PostgreSQL | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Scaleway Managed Database for PostgreSQL (one copy) | 101.102715 | 101.102715 |
| 0 | 0 | Scaleway Managed Database for PostgreSQL (two copies) | 154.68715395 | 154.68715395 |
| 1 | 1.0512 | Scaleway Managed Database for PostgreSQL (one copy) | 101.102715 | 100.051515 |
| 1 | 1.0512 | Scaleway Managed Database for PostgreSQL (two copies) | 154.68715395 | 153.63595395 |
| 10 | 10.512 | Scaleway Managed Database for PostgreSQL (one copy) | 101.102715 | 90.590715 |
| 10 | 10.512 | Scaleway Managed Database for PostgreSQL (two copies) | 154.68715395 | 144.17515395 |
| 100 | 105.12 | Scaleway Managed Database for PostgreSQL (one copy) | 101.102715 | -4.017285 |
| 100 | 105.12 | Scaleway Managed Database for PostgreSQL (two copies) | 154.68715395 | 49.56715395 |
| 1000 | 1051.2 | Scaleway Managed Database for PostgreSQL (one copy) | 191.078865 | -860.121135 |
| 1000 | 1051.2 | Scaleway Managed Database for PostgreSQL (two copies) | 292.35066345 | -758.84933655 |
| 10000 | 10512 | Scaleway Managed Database for PostgreSQL (one copy) | 1450.744965 | -9061.255035 |
| 10000 | 10512 | Scaleway Managed Database for PostgreSQL (two copies) | 2219.63979645 | -8292.36020355 |

**Estimated allocation from planning assumptions; not benchmark calibrated.**

The sizing policy grows compute with translated work and peak headroom, memory with compute and working set, and disk with resident working state and reserve. Monthly usage is distinct from resident data; each workload's assumptions define the translation. HA changes pricing, not this policy's throughput estimate. Unpriced workloads exceed the policy's configuration range; no silent vertical cap or automatic sharding is assumed.

| Sample / scenario | Basis | Mean / peak work/s | Required vCPU | Allocated vCPU | Memory GiB | SSD GiB | Resident GiB | Policy | Constraints |
| - | - | -: | -: | -: | -: | -: | -: | - | - |
| 0 per second / Scaleway Managed Database for PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 0 per second / Scaleway Managed Database for PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1 per second / Scaleway Managed Database for PostgreSQL (one copy) | PlanningAssumption | 1.333333333333333333333333333333333 / 2.666666666666666666666666666666666 | 0.002539682539682539682539682539682539 | 2 | 8 | 100 | 0.000019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1 per second / Scaleway Managed Database for PostgreSQL (two copies) | PlanningAssumption | 1.333333333333333333333333333333333 / 2.666666666666666666666666666666666 | 0.002539682539682539682539682539682539 | 2 | 8 | 100 | 0.000019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 per second / Scaleway Managed Database for PostgreSQL (one copy) | PlanningAssumption | 13.33333333333333333333333333333333 / 26.66666666666666666666666666666666 | 0.02539682539682539682539682539682539 | 2 | 8 | 100 | 0.00019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 per second / Scaleway Managed Database for PostgreSQL (two copies) | PlanningAssumption | 13.33333333333333333333333333333333 / 26.66666666666666666666666666666666 | 0.02539682539682539682539682539682539 | 2 | 8 | 100 | 0.00019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 per second / Scaleway Managed Database for PostgreSQL (one copy) | PlanningAssumption | 133.3333333333333333333333333333333 / 266.6666666666666666666666666666666 | 0.2539682539682539682539682539682539 | 2 | 8 | 100 | 0.0019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 per second / Scaleway Managed Database for PostgreSQL (two copies) | PlanningAssumption | 133.3333333333333333333333333333333 / 266.6666666666666666666666666666666 | 0.2539682539682539682539682539682539 | 2 | 8 | 100 | 0.0019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 per second / Scaleway Managed Database for PostgreSQL (one copy) | PlanningAssumption | 1333.333333333333333333333333333333 / 2666.666666666666666666666666666666 | 2.539682539682539682539682539682539 | 4 | 16 | 100 | 0.019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 per second / Scaleway Managed Database for PostgreSQL (two copies) | PlanningAssumption | 1333.333333333333333333333333333333 / 2666.666666666666666666666666666666 | 2.539682539682539682539682539682539 | 4 | 16 | 100 | 0.019073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 per second / Scaleway Managed Database for PostgreSQL (one copy) | PlanningAssumption | 13333.33333333333333333333333333333 / 26666.66666666666666666666666666666 | 25.39682539682539682539682539682539 | 32 | 128 | 100 | 0.19073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 per second / Scaleway Managed Database for PostgreSQL (two copies) | PlanningAssumption | 13333.33333333333333333333333333333 / 26666.66666666666666666666666666666 | 25.39682539682539682539682539682539 | 32 | 128 | 100 | 0.19073486328125 | `service-adapter-planning-2026-10-22.1` | None reported |

* Row-store throughput (capacityOpsPerVcpuSecond, default 1500) is measured-by-tensor9 as a lower bound: the DynamoDB adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) served 2,974 ops/s of YCSB-A at 16 threads without recorded saturation (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlPostgresqlYcsbAT16GoYcsbV1\_0\_0.kt). Published CPU-bound pgbench reaches 3,101 read-write transactions and 20,289 point reads per vCPU-second (AWS z1d.2xlarge, PostgreSQL 14.5), so actual capacity is likely higher. Reads and writes share one coefficient: at the same adapter version, read-only YCSB-C was not faster than 50%-update YCSB-A.
* Log-broker throughput (capacityStreamMiBPerVcpuSecond 20 at 0.5 utilization, 4 GiB RAM per vCPU) is provider-documented by Google Managed Service for Apache Kafka sizing ([https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size](https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size)): write-equivalent bytes are replicated writes plus a quarter of reads. Producer batches below 10 KB lower per-CPU throughput; that penalty is not modeled.
* Disk utilization 0.8 is provider-documented headroom below Cloud SQL automatic storage increase, which triggers near 91-95% full ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)). The 20 GiB reserve exceeds PostgreSQL's 1 GB default max\_wal\_size; the remainder of that reserve is unmeasured.
* CPU tiers, 4 GiB per vCPU, at most 6.5 GiB per vCPU, 96 vCPU and 65,536 GiB disk follow Cloud SQL Enterprise custom machine limits (provider-documented, same page); 624 GiB is 96 × 6.5. Targets billed per node, unit or throughput unit are sized by their backend instead.
* No public evidence: peak/mean work (2) and the RAM working-set fraction (0.1). Proposed measurements: the p99 one-minute rate over the monthly mean from customer CloudWatch metrics; the buffer hit ratio while stepping RAM under a fixed YCSB-B load.
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Scaleway Managed Database for PostgreSQL (one copy) | Origin list price · SQS billing units | 0.0000004 | USD/64-KiB request units |
| Scaleway Managed Database for PostgreSQL (one copy) | Representative message size | 1024 | bytes |
| Scaleway Managed Database for PostgreSQL (one copy) | Origin send batch fill | 1 | messages/request |
| Scaleway Managed Database for PostgreSQL (one copy) | Origin receive batch fill | 1 | messages/request |
| Scaleway Managed Database for PostgreSQL (one copy) | Origin delete batch fill | 1 | messages/request |
| Scaleway Managed Database for PostgreSQL (one copy) | Deliveries per message | 1 | attempts |
| Scaleway Managed Database for PostgreSQL (one copy) | Empty receive calls per message | 0 | requests |
| Scaleway Managed Database for PostgreSQL (one copy) | Queue residence window | 60 | seconds |
| Scaleway Managed Database for PostgreSQL (one copy) | Ordering and dedup work multiplier | 1 | multiplier |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · read | 0 | USD/read |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · write | 0 | USD/write |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · provider operation | 0 | USD/provider operation |
| Scaleway Managed Database for PostgreSQL (one copy) | Target list price · GiB-month | 0.11126565 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · published GiB | 0 | USD/published GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · network GiB | 0 | USD/network GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Target list price · vCPU-hour | 0.0367275 | USD/vCPU-hour |
| Scaleway Managed Database for PostgreSQL (one copy) | Target list price · GiB-hour | 0.006225 | USD/GiB-hour |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · resource-month | 0 | USD/resource-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · input token | 0 | USD/input token |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · output token | 0 | USD/output token |
| Scaleway Managed Database for PostgreSQL (one copy) | Target monthly base charge | 0 | USD/month |
| Scaleway Managed Database for PostgreSQL (one copy) | Target service minimum | 89.97615 | USD/month |
| Scaleway Managed Database for PostgreSQL (one copy) | Minimum primary CPU | 2 | vCPU |
| Scaleway Managed Database for PostgreSQL (one copy) | Minimum primary RAM | 8 | GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Minimum primary disk | 100 | GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Additional full-price standby copy | 0 | 0 or 1 |
| Scaleway Managed Database for PostgreSQL (one copy) | Allocated share of provisioned cost | 1 | fraction |
| Scaleway Managed Database for PostgreSQL (one copy) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Scaleway Managed Database for PostgreSQL (one copy) | Planning peak / mean work | 2 | multiplier |
| Scaleway Managed Database for PostgreSQL (one copy) | Planning primary CPU utilization | 0.7 | fraction |
| Scaleway Managed Database for PostgreSQL (one copy) | Resident state reserved in RAM | 0.1 | fraction |
| Scaleway Managed Database for PostgreSQL (one copy) | Planning disk utilization | 0.8 | fraction |
| Scaleway Managed Database for PostgreSQL (one copy) | Maintenance and log disk reserve | 20 | GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Scaleway Managed Database for PostgreSQL (one copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Scaleway Managed Database for PostgreSQL (one copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| Scaleway Managed Database for PostgreSQL (two copies) | Origin list price · SQS billing units | 0.0000004 | USD/64-KiB request units |
| Scaleway Managed Database for PostgreSQL (two copies) | Representative message size | 1024 | bytes |
| Scaleway Managed Database for PostgreSQL (two copies) | Origin send batch fill | 1 | messages/request |
| Scaleway Managed Database for PostgreSQL (two copies) | Origin receive batch fill | 1 | messages/request |
| Scaleway Managed Database for PostgreSQL (two copies) | Origin delete batch fill | 1 | messages/request |
| Scaleway Managed Database for PostgreSQL (two copies) | Deliveries per message | 1 | attempts |
| Scaleway Managed Database for PostgreSQL (two copies) | Empty receive calls per message | 0 | requests |
| Scaleway Managed Database for PostgreSQL (two copies) | Queue residence window | 60 | seconds |
| Scaleway Managed Database for PostgreSQL (two copies) | Ordering and dedup work multiplier | 1 | multiplier |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · read | 0 | USD/read |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · write | 0 | USD/write |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · provider operation | 0 | USD/provider operation |
| Scaleway Managed Database for PostgreSQL (two copies) | Target list price · GiB-month | 0.11126565 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · published GiB | 0 | USD/published GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · network GiB | 0 | USD/network GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Scaleway Managed Database for PostgreSQL (two copies) | Target list price · vCPU-hour | 0.0367275 | USD/vCPU-hour |
| Scaleway Managed Database for PostgreSQL (two copies) | Target list price · GiB-hour | 0.006225 | USD/GiB-hour |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · resource-month | 0 | USD/resource-month |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · input token | 0 | USD/input token |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · output token | 0 | USD/output token |
| Scaleway Managed Database for PostgreSQL (two copies) | Target monthly base charge | 0 | USD/month |
| Scaleway Managed Database for PostgreSQL (two copies) | Target service minimum | 89.97615 | USD/month |
| Scaleway Managed Database for PostgreSQL (two copies) | Minimum primary CPU | 2 | vCPU |
| Scaleway Managed Database for PostgreSQL (two copies) | Minimum primary RAM | 8 | GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Minimum primary disk | 100 | GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Additional full-price standby copy | 1 | 0 or 1 |
| Scaleway Managed Database for PostgreSQL (two copies) | Allocated share of provisioned cost | 1 | fraction |
| Scaleway Managed Database for PostgreSQL (two copies) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Scaleway Managed Database for PostgreSQL (two copies) | Planning peak / mean work | 2 | multiplier |
| Scaleway Managed Database for PostgreSQL (two copies) | Planning primary CPU utilization | 0.7 | fraction |
| Scaleway Managed Database for PostgreSQL (two copies) | Resident state reserved in RAM | 0.1 | fraction |
| Scaleway Managed Database for PostgreSQL (two copies) | Planning disk utilization | 0.8 | fraction |
| Scaleway Managed Database for PostgreSQL (two copies) | Maintenance and log disk reserve | 20 | GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Scaleway Managed Database for PostgreSQL (two copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Scaleway Managed Database for PostgreSQL (two copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (two copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (two copies) | Dependent object sink write price guess | 0.000005 | USD/write |

* 1-KiB messages, unbatched send/receive/delete; actual batch and delivery assumptions stay visible. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → fr-par, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Explicit tariff samples are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* Authored planning assumptions, not measured adapter capacity. Origin rates are cited first-tier list prices, before free allowances and discounts.
* A cost scenario does not establish backend availability, protocol fidelity or production readiness. Registry serving status remains independent.
* Storage follows resident original messages, not every monthly message. Broker delivery bytes include redeliveries.
* FIFO estimates do not qualify dedup support, group throughput or single-group latency; backend limitations remain applicable.
* Scaleway Managed Database for PostgreSQL at Production Optimized (PRO2) prices in EUR converted at the ECB reference rate. A high-availability or replica node bills Scaleway's 'Additional nodes' price, EUR 0.0583 per hour for PRO2-XXS, 53% of the main node. Scaleway lists no egress charge for Managed Databases, so selected network is not charged. Cost Optimized ranges (DB-DEV-S from EUR 0.0156 per hour), Block Storage 15K and backups (EUR 0.03 per GB-month) are not selected.
* Row-store throughput (capacityOpsPerVcpuSecond, default 1500) is measured-by-tensor9 as a lower bound: the DynamoDB adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) served 2,974 ops/s of YCSB-A at 16 threads without recorded saturation (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlPostgresqlYcsbAT16GoYcsbV1\_0\_0.kt). Published CPU-bound pgbench reaches 3,101 read-write transactions and 20,289 point reads per vCPU-second (AWS z1d.2xlarge, PostgreSQL 14.5), so actual capacity is likely higher. Reads and writes share one coefficient: at the same adapter version, read-only YCSB-C was not faster than 50%-update YCSB-A.
* Log-broker throughput (capacityStreamMiBPerVcpuSecond 20 at 0.5 utilization, 4 GiB RAM per vCPU) is provider-documented by Google Managed Service for Apache Kafka sizing ([https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size](https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size)): write-equivalent bytes are replicated writes plus a quarter of reads. Producer batches below 10 KB lower per-CPU throughput; that penalty is not modeled.
* Disk utilization 0.8 is provider-documented headroom below Cloud SQL automatic storage increase, which triggers near 91-95% full ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)). The 20 GiB reserve exceeds PostgreSQL's 1 GB default max\_wal\_size; the remainder of that reserve is unmeasured.
* CPU tiers, 4 GiB per vCPU, at most 6.5 GiB per vCPU, 96 vCPU and 65,536 GiB disk follow Cloud SQL Enterprise custom machine limits (provider-documented, same page); 624 GiB is 96 × 6.5. Targets billed per node, unit or throughput unit are sized by their backend instead.
* No public evidence: peak/mean work (2) and the RAM working-set fraction (0.1). Proposed measurements: the p99 one-minute rate over the monthly mean from customer CloudWatch metrics; the buffer hit ratio while stepping RAM under a fixed YCSB-B load.
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* AWS Price List API, AWSQueueService offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSQueueService/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSQueueService/current/us-east-1/index.json)
* Scaleway Managed Databases pricing: [https://www.scaleway.com/en/pricing/managed-databases/](https://www.scaleway.com/en/pricing/managed-databases/)

Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied.

Excluded costs and workload features:

* Additional network transfer, backups, KMS, one-time migration and operational labor unless an explicit meter includes them.
* Destination application execution and separately billed downstream services; supply those allocations separately.
* Taxes, discounts, credits and free-tier allowances unless explicitly reflected in edited rates.
* Unmodeled dependent services, task execution and operations outside the selected workload family.

List prices read: 2026-10-22. Model: `plan-815ddc40e99f05f91bcd38c679512124353bbc6b` / `2026-10-22.planning.2`. Curve: `workload-1`.

Sources: [AWS Price List API, AWSQueueService offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSQueueService/current/us-east-1/index.json), [Scaleway Managed Databases pricing](https://www.scaleway.com/en/pricing/managed-databases/).

## SQS Standard → Scaleway Queues (SQS-compatible)

Origin API: `aws::1.0.0::sqs::classic`. Target backend: `scaleway::1.0.0::queues`.

### SQS Standard · SQS request billing units

Estimated monthly service charges by SQS request billing units. Adapter hosting and Tensor9 fees are excluded. Source: us-east-1; target: fr-par; currency: USD.

![SQS Standard · SQS request billing units: monthly service charges by SQS request billing units. Exact values are in the following table.](/images/diagrams/service-cost/244ae5638c0e717d88b1703a9a571b80e2ee16e1e992645150aba8bd42a5f50c-light.svg)

![SQS Standard · SQS request billing units: monthly service charges by SQS request billing units. Exact values are in the following table.](/images/diagrams/service-cost/a4e0070279486b489f177eea7323ea17e434171a4b38156bc3bc270a43bf4dd9-dark.svg)

Comparison pills describe all sampled scale points; card amounts show the named workload. Costs The Same means within 20% at every point. Costs Depend includes mixed results and unpriced samples.

Exact sampled model outputs in USD/month. Difference means target minus origin; a positive difference means the target costs more.

| SQS request billing units (per second) | SQS (Simple Queue Service, standard queues) | Target scenario | Scaleway Queues (SQS-compatible) | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Scaleway Queues (SQS-compatible) | 0 | 0 |
| 1 | 1.0512 | Scaleway Queues (SQS-compatible) | 0.009360866546630859375 | -1.041839133453369140625 |
| 10 | 10.512 | Scaleway Queues (SQS-compatible) | 0.09360866546630859375 | -10.41839133453369140625 |
| 100 | 105.12 | Scaleway Queues (SQS-compatible) | 0.9360866546630859375 | -104.1839133453369140625 |
| 1000 | 1051.2 | Scaleway Queues (SQS-compatible) | 9.360866546630859375 | -1041.839133453369140625 |
| 10000 | 10512 | Scaleway Queues (SQS-compatible) | 93.60866546630859375 | -10418.39133453369140625 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Scaleway Queues (SQS-compatible) | Origin list price · SQS billing units | 0.0000004 | USD/64-KiB request units |
| Scaleway Queues (SQS-compatible) | Representative message size | 1024 | bytes |
| Scaleway Queues (SQS-compatible) | Origin send batch fill | 1 | messages/request |
| Scaleway Queues (SQS-compatible) | Origin receive batch fill | 1 | messages/request |
| Scaleway Queues (SQS-compatible) | Origin delete batch fill | 1 | messages/request |
| Scaleway Queues (SQS-compatible) | Deliveries per message | 1 | attempts |
| Scaleway Queues (SQS-compatible) | Empty receive calls per message | 0 | requests |
| Scaleway Queues (SQS-compatible) | Queue residence window | 60 | seconds |
| Scaleway Queues (SQS-compatible) | Ordering and dedup work multiplier | 1 | multiplier |
| Scaleway Queues (SQS-compatible) | Target price guess · read | 0 | USD/read |
| Scaleway Queues (SQS-compatible) | Target price guess · write | 0 | USD/write |
| Scaleway Queues (SQS-compatible) | Target price guess · provider operation | 0 | USD/provider operation |
| Scaleway Queues (SQS-compatible) | Target price guess · GiB-month | 0 | USD/GiB-month |
| Scaleway Queues (SQS-compatible) | Target list price · published GiB | 0.011205 | USD/published GiB |
| Scaleway Queues (SQS-compatible) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Scaleway Queues (SQS-compatible) | Target price guess · network GiB | 0 | USD/network GiB |
| Scaleway Queues (SQS-compatible) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Scaleway Queues (SQS-compatible) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Scaleway Queues (SQS-compatible) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Scaleway Queues (SQS-compatible) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Scaleway Queues (SQS-compatible) | Target price guess · resource-month | 0 | USD/resource-month |
| Scaleway Queues (SQS-compatible) | Target price guess · input token | 0 | USD/input token |
| Scaleway Queues (SQS-compatible) | Target price guess · output token | 0 | USD/output token |
| Scaleway Queues (SQS-compatible) | Target monthly base charge | 0 | USD/month |
| Scaleway Queues (SQS-compatible) | Approximate target service minimum | 0 | USD/month |
| Scaleway Queues (SQS-compatible) | Minimum primary CPU | 2 | vCPU |
| Scaleway Queues (SQS-compatible) | Minimum primary RAM | 8 | GiB |
| Scaleway Queues (SQS-compatible) | Minimum primary disk | 100 | GiB |
| Scaleway Queues (SQS-compatible) | Additional full-price standby copy | 0 | 0 or 1 |
| Scaleway Queues (SQS-compatible) | Allocated share of provisioned cost | 1 | fraction |
| Scaleway Queues (SQS-compatible) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Scaleway Queues (SQS-compatible) | Planning peak / mean work | 2 | multiplier |
| Scaleway Queues (SQS-compatible) | Planning primary CPU utilization | 0.7 | fraction |
| Scaleway Queues (SQS-compatible) | Resident state reserved in RAM | 0.1 | fraction |
| Scaleway Queues (SQS-compatible) | Planning disk utilization | 0.8 | fraction |
| Scaleway Queues (SQS-compatible) | Maintenance and log disk reserve | 20 | GiB |
| Scaleway Queues (SQS-compatible) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Scaleway Queues (SQS-compatible) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Scaleway Queues (SQS-compatible) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Scaleway Queues (SQS-compatible) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Scaleway Queues (SQS-compatible) | Dependent object sink write price guess | 0.000005 | USD/write |

* 1-KiB messages, unbatched send/receive/delete; actual batch and delivery assumptions stay visible. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → fr-par, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Explicit tariff samples are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* Authored planning assumptions, not measured adapter capacity. Origin rates are cited first-tier list prices, before free allowances and discounts.
* A cost scenario does not establish backend availability, protocol fidelity or production readiness. Registry serving status remains independent.
* Storage follows resident original messages, not every monthly message. Broker delivery bytes include redeliveries.
* FIFO estimates do not qualify dedup support, group throughput or single-group latency; backend limitations remain applicable.
* Scaleway Queues bills the volume of messages travelling through queues, not requests or storage ([https://www.scaleway.com/en/docs/queues/faq/](https://www.scaleway.com/en/docs/queues/faq/)). Scaleway bills published bytes; it does not say whether a received message counts again, so delivered bytes are not charged.
* AWS Price List API, AWSQueueService offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSQueueService/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSQueueService/current/us-east-1/index.json)
* Scaleway public product catalog: [https://api.scaleway.com/product-catalog/v2alpha1/public-catalog/products](https://api.scaleway.com/product-catalog/v2alpha1/public-catalog/products)

Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied.

Excluded costs and workload features:

* Additional network transfer, backups, KMS, one-time migration and operational labor unless an explicit meter includes them.
* Destination application execution and separately billed downstream services; supply those allocations separately.
* Taxes, discounts, credits and free-tier allowances unless explicitly reflected in edited rates.
* Unmodeled dependent services, task execution and operations outside the selected workload family.

List prices read: 2026-10-22. Model: `plan-63b489f0a3bfc0d52f4664f3bf3e716a4311cb75` / `2026-10-22.planning.2`. Curve: `workload-1`.

Sources: [AWS Price List API, AWSQueueService offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSQueueService/current/us-east-1/index.json), [Scaleway public product catalog](https://api.scaleway.com/product-catalog/v2alpha1/public-catalog/products).

## SQS → Cloud SQL for PostgreSQL

Origin API: `aws::1.0.0::sqs::classic`. Target backend: `google::1.0.0::cloudsql::postgresql`.

### Monthly cost by SQS request rate

Reference monthly service charges by Average API requests/s. Adapter hosting and Tensor9 fees are excluded. Source: us-east-1; target: us-central1; currency: USD.

![Monthly cost by SQS request rate: monthly service charges by Average API requests/s. Exact values are in the following table.](/images/diagrams/service-cost/fa2cade1178e9faa3966ae9dd4e19a781abb515e5278692f9ee12b9f4ca91e41-light.svg)

![Monthly cost by SQS request rate: monthly service charges by Average API requests/s. Exact values are in the following table.](/images/diagrams/service-cost/415040223d11b4f64162a2d3f057d642d7070165e19943bcb2b682e95a701090-dark.svg)

Comparison pills describe all sampled scale points; card amounts show the named workload. Costs The Same means within 20% at every point. Costs Depend includes mixed results and unpriced samples.

Exact sampled model outputs in USD/month. Difference means target minus origin; a positive difference means the target costs more.
Estimated allocation from planning assumptions; not benchmark calibrated. Lines connect evaluated samples; intermediate capacity and prices are not inferred. Unpriced means no target quote or cost difference is available within the sizing policy.

| Average API requests/s (requests/s) | SQS (Simple Queue Service, standard queues) | Target scenario | Cloud SQL for PostgreSQL | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Cloud SQL for PostgreSQL (HA) | 236.356 | 236.356 |
| 0 | 0 | Cloud SQL for PostgreSQL (zonal) | 118.178 | 118.178 |
| 1 | 1.0512 | Cloud SQL for PostgreSQL (HA) | 236.356 | 235.3048 |
| 1 | 1.0512 | Cloud SQL for PostgreSQL (zonal) | 118.178 | 117.1268 |
| 10 | 10.512 | Cloud SQL for PostgreSQL (HA) | 236.356 | 225.844 |
| 10 | 10.512 | Cloud SQL for PostgreSQL (zonal) | 118.178 | 107.666 |
| 100 | 105.12 | Cloud SQL for PostgreSQL (HA) | 236.356 | 131.236 |
| 100 | 105.12 | Cloud SQL for PostgreSQL (zonal) | 118.178 | 13.058 |
| 1000 | 1051.2 | Cloud SQL for PostgreSQL (HA) | 843.424 | -207.776 |
| 1000 | 1051.2 | Cloud SQL for PostgreSQL (zonal) | 421.712 | -629.488 |
| 10000 | 10512 | Cloud SQL for PostgreSQL (HA) | 6509.392 | -4002.608 |
| 10000 | 10512 | Cloud SQL for PostgreSQL (zonal) | 3254.696 | -7257.304 |
| 30000 | 31536 | Cloud SQL for PostgreSQL (HA) | Unpriced | Unavailable |
| 30000 | 31536 | Cloud SQL for PostgreSQL (zonal) | Unpriced | Unavailable |

**Estimated allocation from planning assumptions; not benchmark calibrated.**

The sizing policy grows compute with translated work and peak headroom, memory with compute and working set, and disk with resident working state and reserve. Monthly usage is distinct from resident data; each workload's assumptions define the translation. HA changes pricing, not this policy's throughput estimate. Unpriced workloads exceed the policy's configuration range; no silent vertical cap or automatic sharding is assumed.

| Sample / scenario | Basis | Mean / peak work/s | Required vCPU | Allocated vCPU | Memory GiB | SSD GiB | Resident GiB | Policy | Constraints |
| - | - | -: | -: | -: | -: | -: | -: | - | - |
| 0 requests/s / Cloud SQL for PostgreSQL (HA) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `sqs-cloudsql-planning-2026-10-22.1` | None reported |
| 0 requests/s / Cloud SQL for PostgreSQL (zonal) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `sqs-cloudsql-planning-2026-10-22.1` | None reported |
| 1 requests/s / Cloud SQL for PostgreSQL (HA) | PlanningAssumption | 0.3333333333333333333333333333333333 / 0.6666666666666666666666666666666666 | 0.006349206349206349206349206349206349 | 2 | 8 | 100 | 0.00011444091796875 | `sqs-cloudsql-planning-2026-10-22.1` | None reported |
| 1 requests/s / Cloud SQL for PostgreSQL (zonal) | PlanningAssumption | 0.3333333333333333333333333333333333 / 0.6666666666666666666666666666666666 | 0.006349206349206349206349206349206349 | 2 | 8 | 100 | 0.00011444091796875 | `sqs-cloudsql-planning-2026-10-22.1` | None reported |
| 10 requests/s / Cloud SQL for PostgreSQL (HA) | PlanningAssumption | 3.333333333333333333333333333333333 / 6.666666666666666666666666666666666 | 0.06349206349206349206349206349206349 | 2 | 8 | 100 | 0.0011444091796875 | `sqs-cloudsql-planning-2026-10-22.1` | None reported |
| 10 requests/s / Cloud SQL for PostgreSQL (zonal) | PlanningAssumption | 3.333333333333333333333333333333333 / 6.666666666666666666666666666666666 | 0.06349206349206349206349206349206349 | 2 | 8 | 100 | 0.0011444091796875 | `sqs-cloudsql-planning-2026-10-22.1` | None reported |
| 100 requests/s / Cloud SQL for PostgreSQL (HA) | PlanningAssumption | 33.33333333333333333333333333333333 / 66.66666666666666666666666666666666 | 0.6349206349206349206349206349206349 | 2 | 8 | 100 | 0.011444091796875 | `sqs-cloudsql-planning-2026-10-22.1` | None reported |
| 100 requests/s / Cloud SQL for PostgreSQL (zonal) | PlanningAssumption | 33.33333333333333333333333333333333 / 66.66666666666666666666666666666666 | 0.6349206349206349206349206349206349 | 2 | 8 | 100 | 0.011444091796875 | `sqs-cloudsql-planning-2026-10-22.1` | None reported |
| 1000 requests/s / Cloud SQL for PostgreSQL (HA) | PlanningAssumption | 333.3333333333333333333333333333333 / 666.6666666666666666666666666666666 | 6.349206349206349206349206349206349 | 8 | 32 | 100 | 0.11444091796875 | `sqs-cloudsql-planning-2026-10-22.1` | None reported |
| 1000 requests/s / Cloud SQL for PostgreSQL (zonal) | PlanningAssumption | 333.3333333333333333333333333333333 / 666.6666666666666666666666666666666 | 6.349206349206349206349206349206349 | 8 | 32 | 100 | 0.11444091796875 | `sqs-cloudsql-planning-2026-10-22.1` | None reported |
| 10000 requests/s / Cloud SQL for PostgreSQL (HA) | PlanningAssumption | 3333.333333333333333333333333333333 / 6666.666666666666666666666666666666 | 63.49206349206349206349206349206349 | 64 | 256 | 100 | 1.1444091796875 | `sqs-cloudsql-planning-2026-10-22.1` | None reported |
| 10000 requests/s / Cloud SQL for PostgreSQL (zonal) | PlanningAssumption | 3333.333333333333333333333333333333 / 6666.666666666666666666666666666666 | 63.49206349206349206349206349206349 | 64 | 256 | 100 | 1.1444091796875 | `sqs-cloudsql-planning-2026-10-22.1` | None reported |
| 30000 requests/s / Cloud SQL for PostgreSQL (HA) | Unpriced | 10000 / 20000 | 190.4761904761904761904761904761905 | Unpriced | Unpriced | Unpriced | 3.4332275390625 | `sqs-cloudsql-planning-2026-10-22.1` | No listed primary CPU tier through 96 vCPUs satisfies required CPU 190.4761904761904761904761904761905, caller minimum 2 vCPUs and memory at most 6.5 GiB/vCPU or 624 GiB. Required memory at 96 vCPUs is 384 GiB. |
| 30000 requests/s / Cloud SQL for PostgreSQL (zonal) | Unpriced | 10000 / 20000 | 190.4761904761904761904761904761905 | Unpriced | Unpriced | Unpriced | 3.4332275390625 | `sqs-cloudsql-planning-2026-10-22.1` | No listed primary CPU tier through 96 vCPUs satisfies required CPU 190.4761904761904761904761904761905, caller minimum 2 vCPUs and memory at most 6.5 GiB/vCPU or 624 GiB. Required memory at 96 vCPUs is 384 GiB. |

* 150 full lifecycle equivalents per primary vCPU-second for a 1 KiB reference message (send, receive/claim and delete). Default 150 is a measured-by-tensor9 lower bound, not benchmark calibrated capacity: k6 offered 300 lifecycles/s to the SQS adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) with short timestamp bodies and 299.93/s completed (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlK6RoundtripR300T8K6V1\_0\_0.kt); database CPU was not recorded. These are modeled work units, not measured SQL transactions/s.
* Mean work uses original message arrivals × (2 + deliveries/message + 0.1 × empty receives/message) / 3, then scales by max(1, message bytes / 1024). Source batch fill was already used to infer original messages and is not applied again.
* Peak work is mean work × 2. Required primary CPU divides peak work by 150 lifecycle equivalents/vCPU-second × 0.7 target utilization.
* Resident data uses peak original arrivals × 60 residence seconds × 1024 message bytes × 3 physical storage multiplier. One binary GiB is 1073741824 bytes.
* Provisioned disk rounds (resident GiB + 20 GiB reserve) / 0.7 target disk utilization upward to whole GiB, retaining the caller minimum. Memory is the maximum of caller minimum, CPU × 4 GiB/vCPU and 0.1 of resident data, with a 0.9 GiB/vCPU floor and quarter-GiB upward rounding.
* CPU choices are 2, 4, 8, 16, 32, 64 and 96 primary vCPUs. CPU and memory promote jointly, with at most 6.5 GiB/vCPU, 624 GiB RAM and 65536 GiB disk.
* HA changes standby pricing and does not double primary throughput. Shared allocation changes the assigned cost and does not reduce required capacity.
* No benchmark sample calibrates this policy. Latency, IOPS, polling contention, WAL, vacuum and actual throughput require qualification. Demand beyond the listed configuration bounds is unpriced; this policy does not clamp, automatically shard or extrapolate capacity.
* No listed primary CPU tier through 96 vCPUs satisfies required CPU 190.4761904761904761904761904761905, caller minimum 2 vCPUs and memory at most 6.5 GiB/vCPU or 624 GiB. Required memory at 96 vCPUs is 384 GiB.

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Cloud SQL for PostgreSQL (HA) | Representative SQS message size | 1024 | bytes |
| Cloud SQL for PostgreSQL (HA) | Origin send batch fill | 1 | messages/request |
| Cloud SQL for PostgreSQL (HA) | Origin receive batch fill | 1 | messages/request |
| Cloud SQL for PostgreSQL (HA) | Origin delete batch fill | 1 | messages/request |
| Cloud SQL for PostgreSQL (HA) | Receive deliveries per original message | 1 | deliveries/message |
| Cloud SQL for PostgreSQL (HA) | Empty receive requests per original message | 0 | requests/message |
| Cloud SQL for PostgreSQL (HA) | Minimum requested Cloud SQL vCPUs | 2 | vCPU |
| Cloud SQL for PostgreSQL (HA) | Minimum requested Cloud SQL memory | 8 | GiB |
| Cloud SQL for PostgreSQL (HA) | Minimum requested Cloud SQL SSD | 100 | GiB |
| Cloud SQL for PostgreSQL (HA) | Cloud SQL high availability | 1 | 0 = zonal, 1 = HA |
| Cloud SQL for PostgreSQL (HA) | Share of database cost allocated here | 1 | fraction |
| Cloud SQL for PostgreSQL (HA) | Planning lifecycle work per vCPU | 150 | 1-KiB lifecycle equivalents/vCPU-second |
| Cloud SQL for PostgreSQL (HA) | Peak / average queue work | 2 | multiplier |
| Cloud SQL for PostgreSQL (HA) | Target primary compute utilization | 0.7 | fraction |
| Cloud SQL for PostgreSQL (HA) | Peak message residence or backlog window | 60 | seconds |
| Cloud SQL for PostgreSQL (HA) | Queue physical storage / payload bytes | 3 | multiplier |
| Cloud SQL for PostgreSQL (HA) | WAL and maintenance disk reserve | 20 | GiB |
| Cloud SQL for PostgreSQL (HA) | Target provisioned disk utilization | 0.7 | fraction |
| Cloud SQL for PostgreSQL (HA) | Planning memory per primary vCPU | 4 | GiB/vCPU |
| Cloud SQL for PostgreSQL (HA) | Resident-data working set in memory | 0.1 | fraction |
| Cloud SQL for PostgreSQL (zonal) | Representative SQS message size | 1024 | bytes |
| Cloud SQL for PostgreSQL (zonal) | Origin send batch fill | 1 | messages/request |
| Cloud SQL for PostgreSQL (zonal) | Origin receive batch fill | 1 | messages/request |
| Cloud SQL for PostgreSQL (zonal) | Origin delete batch fill | 1 | messages/request |
| Cloud SQL for PostgreSQL (zonal) | Receive deliveries per original message | 1 | deliveries/message |
| Cloud SQL for PostgreSQL (zonal) | Empty receive requests per original message | 0 | requests/message |
| Cloud SQL for PostgreSQL (zonal) | Minimum requested Cloud SQL vCPUs | 2 | vCPU |
| Cloud SQL for PostgreSQL (zonal) | Minimum requested Cloud SQL memory | 8 | GiB |
| Cloud SQL for PostgreSQL (zonal) | Minimum requested Cloud SQL SSD | 100 | GiB |
| Cloud SQL for PostgreSQL (zonal) | Cloud SQL high availability | 0 | 0 = zonal, 1 = HA |
| Cloud SQL for PostgreSQL (zonal) | Share of database cost allocated here | 1 | fraction |
| Cloud SQL for PostgreSQL (zonal) | Planning lifecycle work per vCPU | 150 | 1-KiB lifecycle equivalents/vCPU-second |
| Cloud SQL for PostgreSQL (zonal) | Peak / average queue work | 2 | multiplier |
| Cloud SQL for PostgreSQL (zonal) | Target primary compute utilization | 0.7 | fraction |
| Cloud SQL for PostgreSQL (zonal) | Peak message residence or backlog window | 60 | seconds |
| Cloud SQL for PostgreSQL (zonal) | Queue physical storage / payload bytes | 3 | multiplier |
| Cloud SQL for PostgreSQL (zonal) | WAL and maintenance disk reserve | 20 | GiB |
| Cloud SQL for PostgreSQL (zonal) | Target provisioned disk utilization | 0.7 | fraction |
| Cloud SQL for PostgreSQL (zonal) | Planning memory per primary vCPU | 4 | GiB/vCPU |
| Cloud SQL for PostgreSQL (zonal) | Resident-data working set in memory | 0.1 | fraction |

* 1 KiB messages; unbatched send, receive and delete requests in a 1:1:1 mix, with no empty receives or redeliveries. 730 hours/month; one billing unit per API request. Requested minima are 2 vCPU, 8 GiB memory and 100 GiB SSD, fully allocated. A versioned planning policy grows CPU, RAM and disk using 2x peak load, 70% utilization and explicit resident-data assumptions; it is not benchmark calibrated. Above the modeled configuration range, target price and savings are unavailable.
* Reference list rates as of 2026-10-18: us-east-1 → us-central1, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Explicit tariff samples are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* 730 running hours per modeled month. Dedicated database compute and disk cost money even with zero origin traffic.
* Shared database allocation is a caller assumption. Do not sum a full database charge for every adapter sharing that database.
* Estimated allocation from planning assumptions; not benchmark calibrated. CPU, RAM and provisioned disk grow with the inferred workload and explicit peak/backlog assumptions.
* Average API requests, 64-KiB billing units, original messages and complete lifecycle work are distinct. One unbatched send/receive/delete cycle is one lifecycle, not three TPS.
* CPU tiers stop at 96 primary vCPUs; unsupported demand retains source cost but has no target cost, adapted total or savings. No sharding is inferred.
* Actual throughput, latency, connection limits, disk IOPS, claim contention, WAL and vacuum remain unqualified until comparable sustained benchmark samples exist.
* 150 full lifecycle equivalents per primary vCPU-second for a 1 KiB reference message (send, receive/claim and delete). Default 150 is a measured-by-tensor9 lower bound, not benchmark calibrated capacity: k6 offered 300 lifecycles/s to the SQS adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) with short timestamp bodies and 299.93/s completed (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlK6RoundtripR300T8K6V1\_0\_0.kt); database CPU was not recorded. These are modeled work units, not measured SQL transactions/s.
* Mean work uses original message arrivals × (2 + deliveries/message + 0.1 × empty receives/message) / 3, then scales by max(1, message bytes / 1024). Source batch fill was already used to infer original messages and is not applied again.
* Peak work is mean work × 2. Required primary CPU divides peak work by 150 lifecycle equivalents/vCPU-second × 0.7 target utilization.
* Resident data uses peak original arrivals × 60 residence seconds × 1024 message bytes × 3 physical storage multiplier. One binary GiB is 1073741824 bytes.
* Provisioned disk rounds (resident GiB + 20 GiB reserve) / 0.7 target disk utilization upward to whole GiB, retaining the caller minimum. Memory is the maximum of caller minimum, CPU × 4 GiB/vCPU and 0.1 of resident data, with a 0.9 GiB/vCPU floor and quarter-GiB upward rounding.
* CPU choices are 2, 4, 8, 16, 32, 64 and 96 primary vCPUs. CPU and memory promote jointly, with at most 6.5 GiB/vCPU, 624 GiB RAM and 65536 GiB disk.
* HA changes standby pricing and does not double primary throughput. Shared allocation changes the assigned cost and does not reduce required capacity.
* No benchmark sample calibrates this policy. Latency, IOPS, polling contention, WAL, vacuum and actual throughput require qualification. Demand beyond the listed configuration bounds is unpriced; this policy does not clamp, automatically shard or extrapolate capacity.
* Source usage is priced at reference rates; source lines are not actual invoice charges. Free or discounted usage still consumes target resources.
* AWS Standard SQS pricing: [https://aws.amazon.com/sqs/pricing/](https://aws.amazon.com/sqs/pricing/)
* Cloud SQL Enterprise PostgreSQL pricing: [https://cloud.google.com/sql/pricing/](https://cloud.google.com/sql/pricing/)
* Cloud SQL for PostgreSQL instance resource settings: [https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)

Cost scope: Modeled monthly service usage and selected database allocation; adapter hosting and Tensor9 fees only when explicitly supplied.

Excluded costs and workload features:

* Free allowances, negotiated discounts, credits, tax and one-time migration charges.
* Charges not listed in the breakdown, including additional network transfer, backups and encryption/KMS.
* Application compute changes, operational labor and portfolio-wide sharing or deduplication of infrastructure.
* SQS FIFO and fair queues; actual throughput/latency and resident-data behavior beyond the explicit planning assumptions.

Rate snapshot: 2026-10-18. Model: `sqs-cloudsql` / `2026-10-18.4`. Curve: `request-rate`.

Sources: [AWS Standard SQS pricing](https://aws.amazon.com/sqs/pricing/), [Cloud SQL Enterprise PostgreSQL pricing](https://cloud.google.com/sql/pricing/), [Cloud SQL for PostgreSQL instance resource settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings).

### SQS → Cloud SQL planned scale-point benchmark

This is a benchmark plan, with historical reference observations retained separately. Planned cases are not completed measurements. The observations below do not calibrate the estimated allocation policy.

Plan: `sqs-cloudsql-scale-v1`. Model: `sqs-cloudsql`. Workload: 1 KiB unbatched SQS send/receive/delete message cycles (`sqs-1kib-unbatched-cycle`).

| Payload bytes | Send batch | Receive batch | Delete batch | Queues | Concurrency |
| -: | -: | -: | -: | -: | -: |
| 1024 | 1 | 1 | 1 | 1 | 32 |

Operation mix: SendMessage:ReceiveMessage:DeleteMessage = 1:1:1; no empty receives or retries. Latency scope: send start through successful delete completion.

**Planned configurations**

| Configuration | vCPU | Memory GiB | SSD GiB | Availability | Region | Parameters |
| - | -: | -: | -: | - | - | - |
| cloudsql-zonal-2vcpu | 2 | 8 | 100 | Zonal | us-central1 | storageType=SSD, edition=Enterprise, dbEngineVersion=POSTGRES\_16, adapterVcpus=Unresolved, adapterMemoryGiB=Unresolved, adapterReplicas=Unresolved, loadGeneratorVcpus=Unresolved, loadGeneratorMemoryGiB=Unresolved, connectionPoolSize=Unresolved |
| cloudsql-zonal-4vcpu | 4 | 16 | 100 | Zonal | us-central1 | storageType=SSD, edition=Enterprise, dbEngineVersion=POSTGRES\_16, adapterVcpus=Unresolved, adapterMemoryGiB=Unresolved, adapterReplicas=Unresolved, loadGeneratorVcpus=Unresolved, loadGeneratorMemoryGiB=Unresolved, connectionPoolSize=Unresolved |
| cloudsql-zonal-8vcpu | 8 | 32 | 100 | Zonal | us-central1 | storageType=SSD, edition=Enterprise, dbEngineVersion=POSTGRES\_16, adapterVcpus=Unresolved, adapterMemoryGiB=Unresolved, adapterReplicas=Unresolved, loadGeneratorVcpus=Unresolved, loadGeneratorMemoryGiB=Unresolved, connectionPoolSize=Unresolved |
| cloudsql-zonal-16vcpu | 16 | 64 | 100 | Zonal | us-central1 | storageType=SSD, edition=Enterprise, dbEngineVersion=POSTGRES\_16, adapterVcpus=Unresolved, adapterMemoryGiB=Unresolved, adapterReplicas=Unresolved, loadGeneratorVcpus=Unresolved, loadGeneratorMemoryGiB=Unresolved, connectionPoolSize=Unresolved |

Required environment keys must be resolved before a planned case can produce matching evidence: `dbEngineVersion`, `adapterVcpus`, `adapterMemoryGiB`, `adapterReplicas`, `loadGeneratorVcpus`, `loadGeneratorMemoryGiB`, `connectionPoolSize`.

* **cloudsql-zonal-2vcpu** unresolved: `adapterVcpus`, `adapterMemoryGiB`, `adapterReplicas`, `loadGeneratorVcpus`, `loadGeneratorMemoryGiB`, `connectionPoolSize`.
* **cloudsql-zonal-4vcpu** unresolved: `adapterVcpus`, `adapterMemoryGiB`, `adapterReplicas`, `loadGeneratorVcpus`, `loadGeneratorMemoryGiB`, `connectionPoolSize`.
* **cloudsql-zonal-8vcpu** unresolved: `adapterVcpus`, `adapterMemoryGiB`, `adapterReplicas`, `loadGeneratorVcpus`, `loadGeneratorMemoryGiB`, `connectionPoolSize`.
* **cloudsql-zonal-16vcpu** unresolved: `adapterVcpus`, `adapterMemoryGiB`, `adapterReplicas`, `loadGeneratorVcpus`, `loadGeneratorMemoryGiB`, `connectionPoolSize`.

**Planned measurement cases**

Offered throughput is a test input. Completed throughput, error rate, latency and backlog must be measured against the stated acceptance thresholds.

| Case | Configuration / workload | Offered cycles/s | Warmup s | Measure s | Repetitions | p99 limit ms | Error-rate limit | Backlog-growth limit | Region / adapter version |
| - | - | -: | -: | -: | -: | -: | -: | -: | - |
| cloudsql-zonal-2vcpu-25tps | cloudsql-zonal-2vcpu / sqs-1kib-unbatched-cycle | 25 | 60 | 300 | 3 | 200 | 0.001 | 0 | us-central1 / Unspecified |
| cloudsql-zonal-2vcpu-100tps | cloudsql-zonal-2vcpu / sqs-1kib-unbatched-cycle | 100 | 60 | 300 | 3 | 200 | 0.001 | 0 | us-central1 / Unspecified |
| cloudsql-zonal-2vcpu-300tps | cloudsql-zonal-2vcpu / sqs-1kib-unbatched-cycle | 300 | 60 | 300 | 3 | 200 | 0.001 | 0 | us-central1 / Unspecified |
| cloudsql-zonal-2vcpu-1000tps | cloudsql-zonal-2vcpu / sqs-1kib-unbatched-cycle | 1000 | 60 | 300 | 3 | 200 | 0.001 | 0 | us-central1 / Unspecified |
| cloudsql-zonal-4vcpu-25tps | cloudsql-zonal-4vcpu / sqs-1kib-unbatched-cycle | 25 | 60 | 300 | 3 | 200 | 0.001 | 0 | us-central1 / Unspecified |
| cloudsql-zonal-4vcpu-100tps | cloudsql-zonal-4vcpu / sqs-1kib-unbatched-cycle | 100 | 60 | 300 | 3 | 200 | 0.001 | 0 | us-central1 / Unspecified |
| cloudsql-zonal-4vcpu-300tps | cloudsql-zonal-4vcpu / sqs-1kib-unbatched-cycle | 300 | 60 | 300 | 3 | 200 | 0.001 | 0 | us-central1 / Unspecified |
| cloudsql-zonal-4vcpu-1000tps | cloudsql-zonal-4vcpu / sqs-1kib-unbatched-cycle | 1000 | 60 | 300 | 3 | 200 | 0.001 | 0 | us-central1 / Unspecified |
| cloudsql-zonal-8vcpu-25tps | cloudsql-zonal-8vcpu / sqs-1kib-unbatched-cycle | 25 | 60 | 300 | 3 | 200 | 0.001 | 0 | us-central1 / Unspecified |
| cloudsql-zonal-8vcpu-100tps | cloudsql-zonal-8vcpu / sqs-1kib-unbatched-cycle | 100 | 60 | 300 | 3 | 200 | 0.001 | 0 | us-central1 / Unspecified |
| cloudsql-zonal-8vcpu-300tps | cloudsql-zonal-8vcpu / sqs-1kib-unbatched-cycle | 300 | 60 | 300 | 3 | 200 | 0.001 | 0 | us-central1 / Unspecified |
| cloudsql-zonal-8vcpu-1000tps | cloudsql-zonal-8vcpu / sqs-1kib-unbatched-cycle | 1000 | 60 | 300 | 3 | 200 | 0.001 | 0 | us-central1 / Unspecified |
| cloudsql-zonal-16vcpu-25tps | cloudsql-zonal-16vcpu / sqs-1kib-unbatched-cycle | 25 | 60 | 300 | 3 | 200 | 0.001 | 0 | us-central1 / Unspecified |
| cloudsql-zonal-16vcpu-100tps | cloudsql-zonal-16vcpu / sqs-1kib-unbatched-cycle | 100 | 60 | 300 | 3 | 200 | 0.001 | 0 | us-central1 / Unspecified |
| cloudsql-zonal-16vcpu-300tps | cloudsql-zonal-16vcpu / sqs-1kib-unbatched-cycle | 300 | 60 | 300 | 3 | 200 | 0.001 | 0 | us-central1 / Unspecified |
| cloudsql-zonal-16vcpu-1000tps | cloudsql-zonal-16vcpu / sqs-1kib-unbatched-cycle | 1000 | 60 | 300 | 3 | 200 | 0.001 | 0 | us-central1 / Unspecified |

**Historical reference observations**

These observations remain separate records. Unknown payload, measurement duration, availability, completed-cycle throughput or other missing fields prevent treating a tool's request rate as qualified message-lifecycle capacity.

| Observation / date | Tool / version | vCPU / memory GiB / SSD GiB / availability | Region / adapter version | Offered / produced / completed cycles/s | Warmup / measure s | Original observed metrics |
| - | - | - | - | - | - | - |
| historical-k6-roundtrip-r300-t8-1-0-0 / 2026-06-24 | k6 / k6 | 2 / 7.5 / 100 / Unknown | us-west1 / 1.0.0 | Unknown / Unknown / Unknown | Unknown / Unknown | send-p50: 4 ms; send-p90: 6 ms; send-p99: 9 ms; send-max: 16 ms; receive-p50: 4 ms; receive-p90: 7 ms; receive-p99: 107 ms; receive-max: 311 ms; e2e-p50: 24 ms; e2e-p90: 86 ms; e2e-p99: 140 ms; e2e-max: 186 ms; throughput: 299.9295953334676 tool-reported ops/s |
| historical-locust-roundtrip-t8-1-0-0 / 2026-06-24 | locust / locust-2.34 | 2 / 7.5 / 100 / Unknown | us-west1 / 1.0.0 | Unknown / Unknown / Unknown | Unknown / Unknown | delete-p50: 13 ms; delete-p90: 16 ms; delete-p99: 18 ms; delete-p999: 33 ms; delete-max: 58 ms; send-p50: 11 ms; send-p90: 13 ms; send-p99: 17 ms; send-p999: 30 ms; send-max: 54 ms; receive-p50: 13 ms; receive-p90: 16 ms; receive-p99: 21 ms; receive-p999: 33 ms; receive-max: 58 ms; e2e-p50: 24 ms; e2e-p90: 27 ms; e2e-p99: 35 ms; e2e-p999: 67 ms; e2e-max: 68 ms; throughput: 204.92061416417454 tool-reported ops/s |
| historical-omb-roundtrip-t2-1-0-0 / 2026-06-24 | omb / omb | 2 / 7.5 / 100 / Unknown | us-west1 / 1.0.0 | Unknown / Unknown / Unknown | Unknown / Unknown | send-p50: 4.248 ms; send-p99: 6.778 ms; send-p999: 12.155 ms; send-max: 57.875 ms; e2e-p50: 13 ms; e2e-p99: 83 ms; e2e-p999: 108 ms; e2e-max: 156 ms; throughput: 150.02719048019992 tool-reported ops/s |

* **historical-k6-roundtrip-r300-t8-1-0-0**: source `src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlK6RoundtripR300T8K6V1_0_0.kt`; case unmatched historical observation. Payload unknown bytes; batch fill send/receive/delete unknown/unknown/unknown; queues unknown; concurrency unknown. Operation mix: unknown. Latency scope: historical e2e metric; full send-through-delete timing is not established. Completed cycles unknown; error rate unknown; backlog start/end unknown/unknown; CPU/memory utilization unknown/unknown; p50/p99 24/140 ms; coordinated-omission correction true. The original generated EvalMeasurement is authoritative; metrics are projected from it without independently restating measured values. Tool-reported throughput does not identify offered, produced and sustained completed-message-cycle rates separately. Payload size, batch mix, queue count, concurrency, duration, completed count, errors, backlog, CPU/memory observations and HA are not established by this record. k6/Locust scripts used timestamp-string bodies rather than an exact 1 KiB payload; the OMB payload is also not established here. The source records storage as GB PD\_SSD; tier memory is derived from db-custom MiB. Raw tuning is retained alongside the normalized allocation.

* **historical-locust-roundtrip-t8-1-0-0**: source `src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlLocustRoundtripT8LocustV1_0_0.kt`; case unmatched historical observation. Payload unknown bytes; batch fill send/receive/delete unknown/unknown/unknown; queues unknown; concurrency unknown. Operation mix: unknown. Latency scope: historical e2e metric; full send-through-delete timing is not established. Completed cycles unknown; error rate unknown; backlog start/end unknown/unknown; CPU/memory utilization unknown/unknown; p50/p99 24/35 ms; coordinated-omission correction false. The original generated EvalMeasurement is authoritative; metrics are projected from it without independently restating measured values. Tool-reported throughput does not identify offered, produced and sustained completed-message-cycle rates separately. Payload size, batch mix, queue count, concurrency, duration, completed count, errors, backlog, CPU/memory observations and HA are not established by this record. k6/Locust scripts used timestamp-string bodies rather than an exact 1 KiB payload; the OMB payload is also not established here. The source records storage as GB PD\_SSD; tier memory is derived from db-custom MiB. Raw tuning is retained alongside the normalized allocation.

* **historical-omb-roundtrip-t2-1-0-0**: source `src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlOmbRoundtripT2OmbV1_0_0.kt`; case unmatched historical observation. Payload unknown bytes; batch fill send/receive/delete unknown/unknown/unknown; queues unknown; concurrency unknown. Operation mix: unknown. Latency scope: historical e2e metric; full send-through-delete timing is not established. Completed cycles unknown; error rate unknown; backlog start/end unknown/unknown; CPU/memory utilization unknown/unknown; p50/p99 13/83 ms; coordinated-omission correction true. The original generated EvalMeasurement is authoritative; metrics are projected from it without independently restating measured values. Tool-reported throughput does not identify offered, produced and sustained completed-message-cycle rates separately. Payload size, batch mix, queue count, concurrency, duration, completed count, errors, backlog, CPU/memory observations and HA are not established by this record. k6/Locust scripts used timestamp-string bodies rather than an exact 1 KiB payload; the OMB payload is also not established here. The source records storage as GB PD\_SSD; tier memory is derived from db-custom MiB. Raw tuning is retained alongside the normalized allocation.

* The 16 cases are planned experiments, each requiring three independent repetitions. No planned case has measured samples yet.

* Pin an adapter version before running a case. Completed-message-cycle throughput, p99 cycle latency, errors and backlog must be measured over 300 seconds after 60 seconds of warmup.

* Acceptance is authored: sustained completed cycles meet the offered rate, p99 ≤ 200 ms, error rate ≤ 0.001 and no backlog growth. This is not measured capacity evidence.

* Tail-latency qualification requires coordinated-omission-corrected measurements under the offered-load workload; correction alone never establishes completion or capacity.

* Historical k6, Locust and OMB observations are different workloads/tools at the same 2-vCPU allocation in us-west1. They are not hardware scaling points and are not averaged.

* Historical observations lack exact payload, HA, duration, completed-cycle counts, error/backlog and resource observations; none qualifies the sizing policy.

* The k6 observation completed its offered 300 cycles/s on 2 vCPU, so the sizing default of 150 lifecycles per vCPU-second is a lower bound. The planned cases must also record database CPU before a measured capacity can replace it.

* Adapter, load-generator and connection-pool allocations must be recorded before a case can qualify. Empty planned environment values are unresolved requirements, not defaults.

## SQS → Google Cloud Pub/Sub

Origin API: `aws::1.0.0::sqs::classic`. Target backend: `google::1.0.0::pubsub`.

### Monthly cost by SQS request rate

Reference monthly service charges by API requests/s. Adapter hosting and Tensor9 fees are excluded. Source: us-east-1; target: us-central1; currency: USD.

![Monthly cost by SQS request rate: monthly service charges by API requests/s. Exact values are in the following table.](/images/diagrams/service-cost/c86c6c160add7581168bde7301c04eac32f00fbb184cf788ca880b2a96df356f-light.svg)

![Monthly cost by SQS request rate: monthly service charges by API requests/s. Exact values are in the following table.](/images/diagrams/service-cost/f45bfa774c9fdc098ac99d82fce35aab549d40dfb549a51fd27ea317a7caa958-dark.svg)

Comparison pills describe all sampled scale points; card amounts show the named workload. Costs The Same means within 20% at every point. Costs Depend includes mixed results and unpriced samples.

Exact sampled model outputs in USD/month. Difference means target minus origin; a positive difference means the target costs more.

| API requests/s (requests/s) | SQS (Simple Queue Service, standard queues) | Target scenario | Pub/Sub | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Pub/Sub (one subscription) | 0 | 0 |
| 1 | 1.0512 | Pub/Sub (one subscription) | 0.069346278906 | -0.981853721094 |
| 10 | 10.512 | Pub/Sub (one subscription) | 0.693462789058 | -9.818537210942 |
| 100 | 105.12 | Pub/Sub (one subscription) | 6.934627890586 | -98.185372109414 |
| 1000 | 1051.2 | Pub/Sub (one subscription) | 69.346278905868 | -981.853721094132 |
| 10000 | 10512 | Pub/Sub (one subscription) | 693.462789058686 | -9818.537210941314 |
| 30000 | 31536 | Pub/Sub (one subscription) | 2080.388367176056 | -29455.611632823944 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Pub/Sub (one subscription) | Representative SQS message size | 1024 | bytes |
| Pub/Sub (one subscription) | Origin send batch fill | 1 | messages/request |
| Pub/Sub (one subscription) | Origin receive batch fill | 1 | messages/request |
| Pub/Sub (one subscription) | Origin delete batch fill | 1 | messages/request |
| Pub/Sub (one subscription) | Receive deliveries per original message | 1 | deliveries/message |
| Pub/Sub (one subscription) | Empty receive requests per original message | 0 | requests/message |
| Pub/Sub (one subscription) | Pub/Sub metadata and carrier overhead | 64 | bytes/message |
| Pub/Sub (one subscription) | Target publish batch fill | 1 | messages/request |
| Pub/Sub (one subscription) | Target delivery batch fill | 1 | messages/request |

* 1 KiB messages; unbatched send, receive and delete requests in a 1:1:1 mix, with no empty receives or redeliveries. 730 hours/month; one SQS billing unit per API request. Pub/Sub uses one subscription and 64 bytes of assumed overhead.
* Reference list rates as of 2026-10-18: us-east-1 → us-central1, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Explicit tariff samples are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* One pull subscription, Standard SQS semantics compatible with this mapping, representative message size and batching.
* Pub/Sub publish and delivery each cost USD 40/TiB, with a 1,000-byte minimum per request. Metadata overhead is an explicit assumption.
* Source usage is priced at reference rates; source lines are not actual invoice charges. Free or discounted usage still consumes target resources.
* AWS Standard SQS pricing: [https://aws.amazon.com/sqs/pricing/](https://aws.amazon.com/sqs/pricing/)
* Pub/Sub pricing: [https://cloud.google.com/pubsub/pricing/](https://cloud.google.com/pubsub/pricing/)

Cost scope: Modeled monthly service usage and selected database allocation; adapter hosting and Tensor9 fees only when explicitly supplied.

Excluded costs and workload features:

* Free allowances, negotiated discounts, credits, tax and one-time migration charges.
* Charges not listed in the breakdown, including additional network transfer, backups and encryption/KMS.
* Application compute changes, operational labor and portfolio-wide sharing or deduplication of infrastructure.
* Pub/Sub retained-message storage, snapshots, extra subscriptions and transformations; SQS delay/FIFO features and visibility-extension traffic.

Rate snapshot: 2026-10-18. Model: `sqs-pubsub` / `2026-10-18.4`. Curve: `request-rate`.

Sources: [AWS Standard SQS pricing](https://aws.amazon.com/sqs/pricing/), [Pub/Sub pricing](https://cloud.google.com/pubsub/pricing/).

See the [service catalog](/byoc/service-adapters/catalog.md) for supported directions, operation coverage and adapter limitations.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.