> ## 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.

# MSK (Kafka)

> MSK (Kafka) APIs with Cloud Adapter.

This page describes how MSK (Kafka) maps to services in the environment where the application runs, including backend choices, supported operations and service-specific behavior.

## Supported environments

* Akamai
* Azure
* DigitalOcean
* Google Cloud
* OCI
* Private Kubernetes
* Scaleway

Check the operation and capability tables for the behavior your application depends on. A supported environment does not imply that every operation of the origin service is available.

## How the backends compare

Each row compares a capability of MSK (Kafka) with its adaptation on each backend.
A dash means this profile does not state the capability for that backend.

### Cloud Adapter

| Capability | MSK (Kafka) | Akamai, DigitalOcean, Google Cloud, Private Kubernetes, and Scaleway · Strimzi Kafka | Akamai, Google Cloud, Private Kubernetes, and Scaleway · Bitnami Kafka | Akamai, Private Kubernetes, and Scaleway · Apache Kafka | Azure | DigitalOcean · DigitalOcean Managed Kafka | Google Cloud · Managed Service for Apache Kafka | OCI | Scaleway · Scaleway Clusters for Apache Kafka |
| - | - | - | - | - | - | - | - | - | - |
| Kafka wire protocol | Apache Kafka | native: producer/consumer unchanged | native: producer/consumer unchanged | native: producer/consumer unchanged | native: producer/consumer unchanged | native: producer/consumer unchanged | native: producer/consumer unchanged | native: producer/consumer unchanged | native: producer/consumer unchanged |
| Durability / replication / HA · who operates the broker | AWS-managed (MSK) | you (self-managed on the cluster) | you (self-managed on the cluster) | you (self-managed on the cluster) | Microsoft (managed Event Hubs) | DigitalOcean (managed Kafka, currently 3.8) | Google (managed Apache Kafka) | Oracle (OCI-managed stream pool) | Scaleway (Clusters for Apache Kafka, a real Apache Kafka engine) |
| Authentication · broker auth | SASL/SCRAM, mTLS, IAM | SASL/SCRAM + mTLS (MSK IAM has no analog) | SASL/SCRAM + mTLS (MSK IAM has no analog) | SASL/SCRAM + mTLS (MSK IAM has no analog) | Shared Access Signatures / Microsoft Entra (not Kafka SASL or MSK IAM) | DigitalOcean-issued SASL/TLS (MSK IAM has no analog) | Google Cloud IAM over SASL\_SSL/OAUTHBEARER (MSK IAM, SASL/SCRAM and mTLS have no analog) | OCI auth tokens (not MSK SASL/SCRAM/mTLS/IAM) | Scaleway-issued username/password on the cluster (MSK's SASL/IAM has no analog) |
| Retention / storage | broker log + tiered storage | the broker's own local storage (no tiered storage) | the broker's own local storage (no tiered storage) | the broker's own local storage (no tiered storage) | Event Hubs managed retention (capacity sized in throughput/processing units, separate from the partition count) | the managed broker's own storage | the managed broker's own storage, tuned per topic | the stream pool's managed storage, under OCI quotas | the managed broker's own storage, allocated in 5 GB steps from a 10 GB floor |
| Encryption in transit | Yes | Yes - client-broker TLS terminates on the target listener's TLS | Yes - client-broker TLS terminates on the target listener's TLS | Yes - client-broker TLS terminates on the target listener's TLS | Yes - client-broker TLS terminates on the target listener's TLS | Yes - client-broker TLS terminates on the target listener's TLS | Yes - client-broker TLS terminates on the target listener's TLS | Yes - client-broker TLS terminates on the target listener's TLS | Yes - client-broker TLS terminates on the target listener's TLS |
| Encryption at rest | KMS key ARN | the backend's own storage / managed encryption (the KMS key ARN has no equivalent) | the backend's own storage / managed encryption (the KMS key ARN has no equivalent) | the backend's own storage / managed encryption (the KMS key ARN has no equivalent) | the backend's own storage / managed encryption (the KMS key ARN has no equivalent) | the backend's own storage / managed encryption (the KMS key ARN has no equivalent) | the backend's own storage / managed encryption (the KMS key ARN has no equivalent) | the backend's own storage / managed encryption (the KMS key ARN has no equivalent) | the backend's own storage / managed encryption (the KMS key ARN has no equivalent) |
| API coverage | full | high | high | high | partial | high | high | partial | high |
| SASL/IAM clients need a client-side change · a mechanism, not a credential | AWS\_MSK\_IAM via aws-msk-iam-auth | - | - | - | - | - | - | - | SASL/PLAIN or SASL/SCRAM with Scaleway's credentials |
| The Kafka version is chosen, not copied · and this is why | your cluster's kafka\_version | - | - | - | - | - | - | - | 4.1.1, the newest Scaleway offers |
| Every broker size is marked beta · Scaleway's own flag, not ours | the MSK broker instance type you chose | - | - | - | - | - | - | - | brokernode-shared-2c-8g (2 vCPU / 8 GB) |
| The same stack references work on either cloud · a deliberate constraint | bootstrap\_brokers\_tls, bootstrap\_brokers\_sasl\_scram, … | - | - | - | - | - | - | - | the identical set on Scaleway and DigitalOcean |

## On Akamai, DigitalOcean, Google Cloud, Private Kubernetes, and Scaleway

### Strimzi Kafka

| Operation | Area | Support | Depth | Notes |
| - | - | - | - | - |
| Monitoring / broker-log delivery / at-rest KMS / VPC placement | AWS control plane | Out of scope | Full surface | Configure backend monitoring and broker logs in place of MSK's CloudWatch, Prometheus, S3 and Firehose settings. Storage encryption uses the backend's key and storage configuration. Select target subnets and failure domains separately from the supplied bootstrap endpoint. |
| Broker config (custom broker-config revision) | Admin | Partial | Most usage | the backend broker natively accepts custom broker config (via the Strimzi or Bitnami chart's config values, or the broker's own config for a raw Apache deployment); MSK's custom broker-config revision has no counterpart, so broker config is set on the backend directly |
| Partition semantics | Admin | Supported | Most usage | partitions are the real broker's own; set and grow them via the AdminClient as on Kafka |
| Topic admin (create / delete / configs) | Admin | Supported | Most usage | the Kafka AdminClient talks to the real broker: create/delete topics, alter configs, and manage partitions natively |
| ACLs / SASL auth | Auth | Partial | Full surface | SASL/SCRAM and mutual TLS are supported. Replace MSK IAM authentication and configure access-control lists on the broker. |
| Offset commit (\_\_consumer\_offsets) | Consume | Supported | Most usage | offsets commit to the broker's own \_\_consumer\_offsets, exactly as on Kafka |
| Glue Schema Registry | Ecosystem | Out of scope | Full surface | AWS Glue Schema Registry has no target-side analog; run a Kafka-native schema registry (Confluent/Apicurio) alongside the broker if you need one |
| MSK Connect | Ecosystem | Out of scope | Full surface | MSK Connect (managed Kafka Connect) is not provisioned; run Kafka Connect yourself against the broker if you need connectors |
| acks / idempotence / transactions | Producer semantics | Supported | Most usage | acks, idempotence, and transactions are the real broker's own, with full exactly-once semantics |
| Broker sizing (MSK broker instance type → CPU / memory / storage) | Sizing | Supported | Most usage | the MSK broker instance type is normalized to CPU/memory and emitted as the broker pod's resource requests/limits (kafka.m5.large → 2 vCPU / 8 GiB), and the storage volume size becomes the broker's persistent-volume size, so sizing follows through to a broker you own |
| Tiered storage | Storage | Out of scope | Full surface | MSK's tiered storage is not configured on the backend; a self-hosted Kafka broker has native tiered storage (KIP-405, production-ready in Kafka 3.9+) you can enable yourself with a remote-store backend, and the managed backends expose no equivalent knob; retention is the target broker's own local or managed storage |
| Consume (consumer groups) | Wire protocol | Supported | Common | your Kafka consumer and consumer-group membership run unchanged over the wire |
| Produce (Kafka wire) | Wire protocol | Supported | Common | your Kafka producer runs unchanged; the adapter supplies the backend's bootstrap-broker endpoint to your producer |

#### How it works

Your producers and consumers keep their Kafka clients and connect directly to Apache Kafka on Kubernetes cluster (via the Strimzi operator) over the Kafka protocol. Tensor9 supplies the bootstrap endpoint; there is no Tensor9 proxy between client and broker. Broker metadata can return further advertised addresses, so clients need network access and TLS trust for those addresses as well as the bootstrap address.

Authentication changes with the broker: SASL/SCRAM and mutual TLS are supported. Replace MSK IAM authentication and manage the broker's access-control lists. Check producer acknowledgement, idempotence and transaction settings against the support table for this broker; a Kafka-compatible endpoint does not guarantee every Kafka administrative or transactional feature.

#### Limitations

* **Moving records, offsets and consumer-group state is not supported.** A new broker starts without the source records, offsets or consumer groups, and source offsets cannot be applied to a different log. If retained history must move, plan a separate replication process. - **You must replace AWS IAM authentication, MSK Connect and Glue Schema Registry separately.** Changing the bootstrap servers does not replace those dependencies.

#### Other considerations

**Who runs what.** You configure the replication factor and minimum in-sync replicas (ISR), monitor replica health, and operate storage, recovery and upgrades. Topic partitions hold the retained log, and consumer-group offsets record progress.

**Before cutover.** Coordinate producer and consumer cutover. Review topic creation, retention, partition counts and broker configuration on Apache Kafka on Kubernetes cluster (via the Strimzi operator), and set up monitoring, backup or recovery and certificate rotation first.

**Performance.** It depends on the broker, storage and workload; this profile has no Tensor9 broker benchmark.

## On Akamai, Google Cloud, Private Kubernetes, and Scaleway

### Bitnami Kafka

| Operation | Area | Support | Depth | Notes |
| - | - | - | - | - |
| Monitoring / broker-log delivery / at-rest KMS / VPC placement | AWS control plane | Out of scope | Full surface | Configure backend monitoring and broker logs in place of MSK's CloudWatch, Prometheus, S3 and Firehose settings. Storage encryption uses the backend's key and storage configuration. Select target subnets and failure domains separately from the supplied bootstrap endpoint. |
| Broker config (custom broker-config revision) | Admin | Partial | Most usage | the backend broker natively accepts custom broker config (via the Strimzi or Bitnami chart's config values, or the broker's own config for a raw Apache deployment); MSK's custom broker-config revision has no counterpart, so broker config is set on the backend directly |
| Partition semantics | Admin | Supported | Most usage | partitions are the real broker's own; set and grow them via the AdminClient as on Kafka |
| Topic admin (create / delete / configs) | Admin | Supported | Most usage | the Kafka AdminClient talks to the real broker: create/delete topics, alter configs, and manage partitions natively |
| ACLs / SASL auth | Auth | Partial | Full surface | SASL/SCRAM and mutual TLS are supported. Replace MSK IAM authentication and configure access-control lists on the broker. |
| Offset commit (\_\_consumer\_offsets) | Consume | Supported | Most usage | offsets commit to the broker's own \_\_consumer\_offsets, exactly as on Kafka |
| Glue Schema Registry | Ecosystem | Out of scope | Full surface | AWS Glue Schema Registry has no target-side analog; run a Kafka-native schema registry (Confluent/Apicurio) alongside the broker if you need one |
| MSK Connect | Ecosystem | Out of scope | Full surface | MSK Connect (managed Kafka Connect) is not provisioned; run Kafka Connect yourself against the broker if you need connectors |
| acks / idempotence / transactions | Producer semantics | Supported | Most usage | acks, idempotence, and transactions are the real broker's own, with full exactly-once semantics |
| Broker sizing (MSK broker instance type → CPU / memory / storage) | Sizing | Supported | Most usage | the MSK broker instance type is normalized to CPU/memory and emitted as the broker pod's resource requests/limits (kafka.m5.large → 2 vCPU / 8 GiB), and the storage volume size becomes the broker's persistent-volume size, so sizing follows through to a broker you own |
| Tiered storage | Storage | Out of scope | Full surface | MSK's tiered storage is not configured on the backend; a self-hosted Kafka broker has native tiered storage (KIP-405, production-ready in Kafka 3.9+) you can enable yourself with a remote-store backend, and the managed backends expose no equivalent knob; retention is the target broker's own local or managed storage |
| Consume (consumer groups) | Wire protocol | Supported | Common | your Kafka consumer and consumer-group membership run unchanged over the wire |
| Produce (Kafka wire) | Wire protocol | Supported | Common | your Kafka producer runs unchanged; the adapter supplies the backend's bootstrap-broker endpoint to your producer |

#### How it works

Your producers and consumers keep their Kafka clients and connect directly to Apache Kafka on Kubernetes cluster (via the Bitnami Kafka chart) over the Kafka protocol. Tensor9 supplies the bootstrap endpoint; there is no Tensor9 proxy between client and broker. Broker metadata can return further advertised addresses, so clients need network access and TLS trust for those addresses as well as the bootstrap address.

Authentication changes with the broker: SASL/SCRAM and mutual TLS are supported. Replace MSK IAM authentication and manage the broker's access-control lists. Check producer acknowledgement, idempotence and transaction settings against the support table for this broker; a Kafka-compatible endpoint does not guarantee every Kafka administrative or transactional feature.

#### Limitations

* **Moving records, offsets and consumer-group state is not supported.** A new broker starts without the source records, offsets or consumer groups, and source offsets cannot be applied to a different log. If retained history must move, plan a separate replication process. - **You must replace AWS IAM authentication, MSK Connect and Glue Schema Registry separately.** Changing the bootstrap servers does not replace those dependencies.

#### Other considerations

**Who runs what.** You configure the replication factor and minimum in-sync replicas (ISR), monitor replica health, and operate storage, recovery and upgrades. Topic partitions hold the retained log, and consumer-group offsets record progress.

**Before cutover.** Coordinate producer and consumer cutover. Review topic creation, retention, partition counts and broker configuration on Apache Kafka on Kubernetes cluster (via the Bitnami Kafka chart), and set up monitoring, backup or recovery and certificate rotation first.

**Performance.** It depends on the broker, storage and workload; this profile has no Tensor9 broker benchmark.

## On Akamai, Private Kubernetes, and Scaleway

### Apache Kafka

| Operation | Area | Support | Depth | Notes |
| - | - | - | - | - |
| Monitoring / broker-log delivery / at-rest KMS / VPC placement | AWS control plane | Out of scope | Full surface | Configure backend monitoring and broker logs in place of MSK's CloudWatch, Prometheus, S3 and Firehose settings. Storage encryption uses the backend's key and storage configuration. Select target subnets and failure domains separately from the supplied bootstrap endpoint. |
| Broker config (custom broker-config revision) | Admin | Partial | Most usage | the backend broker natively accepts custom broker config (via the Strimzi or Bitnami chart's config values, or the broker's own config for a raw Apache deployment); MSK's custom broker-config revision has no counterpart, so broker config is set on the backend directly |
| Partition semantics | Admin | Supported | Most usage | partitions are the real broker's own; set and grow them via the AdminClient as on Kafka |
| Topic admin (create / delete / configs) | Admin | Supported | Most usage | the Kafka AdminClient talks to the real broker: create/delete topics, alter configs, and manage partitions natively |
| ACLs / SASL auth | Auth | Partial | Full surface | SASL/SCRAM and mutual TLS are supported. Replace MSK IAM authentication and configure access-control lists on the broker. |
| Offset commit (\_\_consumer\_offsets) | Consume | Supported | Most usage | offsets commit to the broker's own \_\_consumer\_offsets, exactly as on Kafka |
| Glue Schema Registry | Ecosystem | Out of scope | Full surface | AWS Glue Schema Registry has no target-side analog; run a Kafka-native schema registry (Confluent/Apicurio) alongside the broker if you need one |
| MSK Connect | Ecosystem | Out of scope | Full surface | MSK Connect (managed Kafka Connect) is not provisioned; run Kafka Connect yourself against the broker if you need connectors |
| acks / idempotence / transactions | Producer semantics | Supported | Most usage | acks, idempotence, and transactions are the real broker's own, with full exactly-once semantics |
| Broker sizing (MSK broker instance type → CPU / memory / storage) | Sizing | Supported | Most usage | the MSK broker instance type is normalized to CPU/memory and emitted as the broker pod's resource requests/limits (kafka.m5.large → 2 vCPU / 8 GiB), and the storage volume size becomes the broker's persistent-volume size, so sizing follows through to a broker you own |
| Tiered storage | Storage | Out of scope | Full surface | MSK's tiered storage is not configured on the backend; a self-hosted Kafka broker has native tiered storage (KIP-405, production-ready in Kafka 3.9+) you can enable yourself with a remote-store backend, and the managed backends expose no equivalent knob; retention is the target broker's own local or managed storage |
| Consume (consumer groups) | Wire protocol | Supported | Common | your Kafka consumer and consumer-group membership run unchanged over the wire |
| Produce (Kafka wire) | Wire protocol | Supported | Common | your Kafka producer runs unchanged; the adapter supplies the backend's bootstrap-broker endpoint to your producer |

#### How it works

Your producers and consumers keep their Kafka clients and connect directly to Apache Kafka on Kubernetes cluster (as a raw Apache Kafka deployment) over the Kafka protocol. Tensor9 supplies the bootstrap endpoint; there is no Tensor9 proxy between client and broker. Broker metadata can return further advertised addresses, so clients need network access and TLS trust for those addresses as well as the bootstrap address.

Authentication changes with the broker: SASL/SCRAM and mutual TLS are supported. Replace MSK IAM authentication and manage the broker's access-control lists. Check producer acknowledgement, idempotence and transaction settings against the support table for this broker; a Kafka-compatible endpoint does not guarantee every Kafka administrative or transactional feature.

#### Limitations

* **Moving records, offsets and consumer-group state is not supported.** A new broker starts without the source records, offsets or consumer groups, and source offsets cannot be applied to a different log. If retained history must move, plan a separate replication process. - **You must replace AWS IAM authentication, MSK Connect and Glue Schema Registry separately.** Changing the bootstrap servers does not replace those dependencies.

#### Other considerations

**Who runs what.** You configure the replication factor and minimum in-sync replicas (ISR), monitor replica health, and operate storage, recovery and upgrades. Topic partitions hold the retained log, and consumer-group offsets record progress.

**Before cutover.** Coordinate producer and consumer cutover. Review topic creation, retention, partition counts and broker configuration on Apache Kafka on Kubernetes cluster (as a raw Apache Kafka deployment), and set up monitoring, backup or recovery and certificate rotation first.

**Performance.** It depends on the broker, storage and workload; this profile has no Tensor9 broker benchmark.

## On Azure

### Azure Event Hubs

| Operation | Area | Support | Depth | Notes |
| - | - | - | - | - |
| Monitoring / broker-log delivery / at-rest KMS / VPC placement | AWS control plane | Out of scope | Full surface | Configure backend monitoring and broker logs in place of MSK's CloudWatch, Prometheus, S3 and Firehose settings. Storage encryption uses the backend's key and storage configuration. Select target subnets and failure domains separately from the supplied bootstrap endpoint. |
| Broker config (custom broker-config revision) | Admin | Out of scope | Most usage | Event Hubs does not expose Kafka broker config, so MSK's custom broker-config revision has no analog |
| Partition semantics | Admin | Partial | Most usage | on Standard the partition count is set at creation and cannot be changed; Premium and Dedicated allow increasing (but not decreasing) it after creation, as Kafka itself allows; capacity is sized on a separate axis (throughput units on Standard, processing units on Premium), independent of the partition count |
| Topic admin (create / delete / configs) | Admin | Partial | Most usage | topics are Event Hubs, created up front; the Kafka broker-admin/ACL surface differs, so it is not full AdminClient parity |
| ACLs / SASL auth | Auth | Partial | Full surface | authentication is Shared Access Signatures or Microsoft Entra, not Kafka SASL/SCRAM or MSK IAM; your Kafka clients configure the Event Hubs connection string instead |
| Offset commit (\_\_consumer\_offsets) | Consume | Partial | Most usage | Event Hubs keeps its own consumer-group offset store; the semantics differ slightly from Kafka's \_\_consumer\_offsets |
| Glue Schema Registry | Ecosystem | Out of scope | Full surface | AWS Glue Schema Registry has no target-side analog; run a Kafka-native schema registry (Confluent/Apicurio) alongside the broker if you need one |
| MSK Connect | Ecosystem | Out of scope | Full surface | MSK Connect (managed Kafka Connect) is not provisioned; run Kafka Connect yourself against the broker if you need connectors |
| acks / idempotence / transactions | Producer semantics | Partial | Most usage | produce over the Kafka wire is unchanged; full transactions/idempotence are not complete on the Event Hubs Kafka surface |
| Broker sizing (MSK broker instance type → CPU / memory / storage) | Sizing | Partial | Most usage | capacity is throughput units (Standard) or processing units (Premium), sized on a separate axis from the MSK broker instance type; the partition count is fixed at creation on Standard, while Premium and Dedicated allow increasing it |
| Tiered storage | Storage | Out of scope | Full surface | MSK's tiered storage is not configured on the backend; a self-hosted Kafka broker has native tiered storage (KIP-405, production-ready in Kafka 3.9+) you can enable yourself with a remote-store backend, and the managed backends expose no equivalent knob; retention is the target broker's own local or managed storage |
| Consume (consumer groups) | Wire protocol | Supported | Common | your Kafka consumer and consumer-group membership run unchanged over the wire |
| Produce (Kafka wire) | Wire protocol | Supported | Common | your Kafka producer runs unchanged; the adapter supplies the backend's bootstrap-broker endpoint to your producer |

#### How it works

Your Kafka client connects directly to Azure Event Hubs at `<namespace>.servicebus.windows.net:9093`, the Kafka endpoint of the Standard and Premium tiers. Produce and consume code stay the same; you change the bootstrap address and credentials. Tensor9 does not sit in these connections.

Event Hubs differs from Kafka in administration, transactions, authentication and capacity. Review the differences below before you choose this backend.

![On AWS, your application's Kafka client connects to the MSK brokers. On Azure, the same client connects with the same Kafka protocol to an Event Hubs namespace's Kafka endpoint on port 9093, with no Tensor9 adapter in between.](data:image/svg+xml;base64,<svg xmlns="http://www.w3.org/2000/svg" width="836" height="200" viewBox="0 0 836 200" role="img" aria-label="On AWS, your application's Kafka client connects to the MSK brokers. On Azure, the same client connects with the same Kafka protocol to an Event Hubs namespace's Kafka endpoint on port 9093, with no Tensor9 adapter in between."><style>text{font-family:Inter,-apple-system,BlinkMacSystemFont,'Segoe UI',Roboto,'Helvetica Neue',Arial,sans-serif;fill:#334155}</style>
<defs><marker id="eh1" viewBox="0 0 10 10" refX="8" refY="5" markerWidth="7" markerHeight="7" orient="auto-start-reverse"><path d="M0,0 L10,5 L0,10 z" style="fill:#94a3b8"/></marker></defs>
<rect x="16" y="44" width="384" height="138" rx="14" stroke-width="1.4" stroke-dasharray="5 5" style="fill:#f8fafc;stroke:#cbd5e1"/>
<text x="30" y="62" style="font: 700 10px Inter, sans-serif; letter-spacing: 1.3px; fill: #94a3b8; fill:#94a3b8">ON AWS TODAY</text>
<rect x="30" y="84" width="116" height="68" rx="11" stroke-width="1.5" style="fill:#ffffff;stroke:#cbd5e1"/>
<text x="88" y="115" text-anchor="middle" style="font: 650 13.5px Inter, sans-serif; fill: #0f172a; font-size:12px">Your app</text>
<text x="88" y="131" text-anchor="middle" style="font: 11px Inter, sans-serif; fill: #64748b">Kafka client</text>
<line x1="146" y1="118" x2="222" y2="118" stroke-width="2" marker-end="url(#eh1)" style="stroke:#94a3b8"/>
<text x="184" y="109" text-anchor="middle" style="font: 10px 'SF Mono', ui-monospace, 'JetBrains Mono', Menlo, monospace; fill: #64748b; font-size:8.5px">Kafka wire</text>
<rect x="226" y="82" width="160" height="72" rx="11" stroke-width="1.5" style="fill:#ffffff;stroke:#cbd5e1"/>
<svg x="236" y="94" width="16" height="16" viewBox="0 0 304 182" preserveAspectRatio="xMidYMid meet" style="display: inline"><g> <path d="M86.4,66.4c0,3.7,0.4,6.7,1.1,8.9c0.8,2.2,1.8,4.6,3.2,7.2c0.5,0.8,0.7,1.6,0.7,2.3c0,1-0.6,2-1.9,3l-6.3,4.2 c-0.9,0.6-1.8,0.9-2.6,0.9c-1,0-2-0.5-3-1.4C76.2,90,75,88.4,74,86.8c-1-1.7-2-3.6-3.1-5.9c-7.8,9.2-17.6,13.8-29.4,13.8 c-8.4,0-15.1-2.4-20-7.2c-4.9-4.8-7.4-11.2-7.4-19.2c0-8.5,3-15.4,9.1-20.6c6.1-5.2,14.2-7.8,24.5-7.8c3.4,0,6.9,0.3,10.6,0.8 c3.7,0.5,7.5,1.3,11.5,2.2v-7.3c0-7.6-1.6-12.9-4.7-16c-3.2-3.1-8.6-4.6-16.3-4.6c-3.5,0-7.1,0.4-10.8,1.3c-3.7,0.9-7.3,2-10.8,3.4 c-1.6,0.7-2.8,1.1-3.5,1.3c-0.7,0.2-1.2,0.3-1.6,0.3c-1.4,0-2.1-1-2.1-3.1v-4.9c0-1.6,0.2-2.8,0.7-3.5c0.5-0.7,1.4-1.4,2.8-2.1 c3.5-1.8,7.7-3.3,12.6-4.5c4.9-1.3,10.1-1.9,15.6-1.9c11.9,0,20.6,2.7,26.2,8.1c5.5,5.4,8.3,13.6,8.3,24.6V66.4z M45.8,81.6 c3.3,0,6.7-0.6,10.3-1.8c3.6-1.2,6.8-3.4,9.5-6.4c1.6-1.9,2.8-4,3.4-6.4c0.6-2.4,1-5.3,1-8.7v-4.2c-2.9-0.7-6-1.3-9.2-1.7 c-3.2-0.4-6.3-0.6-9.4-0.6c-6.7,0-11.6,1.3-14.9,4c-3.3,2.7-4.9,6.5-4.9,11.5c0,4.7,1.2,8.2,3.7,10.6 C37.7,80.4,41.2,81.6,45.8,81.6z M126.1,92.4c-1.8,0-3-0.3-3.8-1c-0.8-0.6-1.5-2-2.1-3.9L96.7,10.2c-0.6-2-0.9-3.3-0.9-4 c0-1.6,0.8-2.5,2.4-2.5h9.8c1.9,0,3.2,0.3,3.9,1c0.8,0.6,1.4,2,2,3.9l16.8,66.2l15.6-66.2c0.5-2,1.1-3.3,1.9-3.9c0.8-0.6,2.2-1,4-1 h8c1.9,0,3.2,0.3,4,1c0.8,0.6,1.5,2,1.9,3.9l15.8,67l17.3-67c0.6-2,1.3-3.3,2-3.9c0.8-0.6,2.1-1,3.9-1h9.3c1.6,0,2.5,0.8,2.5,2.5 c0,0.5-0.1,1-0.2,1.6c-0.1,0.6-0.3,1.4-0.7,2.5l-24.1,77.3c-0.6,2-1.3,3.3-2.1,3.9c-0.8,0.6-2.1,1-3.8,1h-8.6c-1.9,0-3.2-0.3-4-1 c-0.8-0.7-1.5-2-1.9-4L156,23l-15.4,64.4c-0.5,2-1.1,3.3-1.9,4c-0.8,0.7-2.2,1-4,1H126.1z M254.6,95.1c-5.2,0-10.4-0.6-15.4-1.8 c-5-1.2-8.9-2.5-11.5-4c-1.6-0.9-2.7-1.9-3.1-2.8c-0.4-0.9-0.6-1.9-0.6-2.8v-5.1c0-2.1,0.8-3.1,2.3-3.1c0.6,0,1.2,0.1,1.8,0.3 c0.6,0.2,1.5,0.6,2.5,1c3.4,1.5,7.1,2.7,11,3.5c4,0.8,7.9,1.2,11.9,1.2c6.3,0,11.2-1.1,14.6-3.3c3.4-2.2,5.2-5.4,5.2-9.5 c0-2.8-0.9-5.1-2.7-7c-1.8-1.9-5.2-3.6-10.1-5.2L246,52c-7.3-2.3-12.7-5.7-16-10.2c-3.3-4.4-5-9.3-5-14.5c0-4.2,0.9-7.9,2.7-11.1 c1.8-3.2,4.2-6,7.2-8.2c3-2.3,6.4-4,10.4-5.2c4-1.2,8.2-1.7,12.6-1.7c2.2,0,4.5,0.1,6.7,0.4c2.3,0.3,4.4,0.7,6.5,1.1 c2,0.5,3.9,1,5.7,1.6c1.8,0.6,3.2,1.2,4.2,1.8c1.4,0.8,2.4,1.6,3,2.5c0.6,0.8,0.9,1.9,0.9,3.3v4.7c0,2.1-0.8,3.2-2.3,3.2 c-0.8,0-2.1-0.4-3.8-1.2c-5.7-2.6-12.1-3.9-19.2-3.9c-5.7,0-10.2,0.9-13.3,2.8c-3.1,1.9-4.7,4.8-4.7,8.9c0,2.8,1,5.2,3,7.1 c2,1.9,5.7,3.8,11,5.5l14.2,4.5c7.2,2.3,12.4,5.5,15.5,9.6c3.1,4.1,4.6,8.8,4.6,14c0,4.3-0.9,8.2-2.6,11.6 c-1.8,3.4-4.2,6.4-7.3,8.8c-3.1,2.5-6.8,4.3-11.1,5.6C264.4,94.4,259.7,95.1,254.6,95.1z" style="fill:#252F3E"/> <g> <path d="M273.5,143.7c-32.9,24.3-80.7,37.2-121.8,37.2c-57.6,0-109.5-21.3-148.7-56.7c-3.1-2.8-0.3-6.6,3.4-4.4 c42.4,24.6,94.7,39.5,148.8,39.5c36.5,0,76.6-7.6,113.5-23.2C274.2,133.6,278.9,139.7,273.5,143.7z" style="fill-rule:evenodd;clip-rule:evenodd;fill:#FF9900"/> <path d="M287.2,128.1c-4.2-5.4-27.8-2.6-38.5-1.3c-3.2,0.4-3.7-2.4-0.8-4.5c18.8-13.2,49.7-9.4,53.3-5 c3.6,4.5-1,35.4-18.6,50.2c-2.7,2.3-5.3,1.1-4.1-1.9C282.5,155.7,291.4,133.4,287.2,128.1z" style="fill-rule:evenodd;clip-rule:evenodd;fill:#FF9900"/> </g> </g></svg><svg x="236" y="94" width="16" height="16" viewBox="0 0 304 182" preserveAspectRatio="xMidYMid meet" style="display: none"><g> <path d="M86.4,66.4c0,3.7,0.4,6.7,1.1,8.9c0.8,2.2,1.8,4.6,3.2,7.2c0.5,0.8,0.7,1.6,0.7,2.3c0,1-0.6,2-1.9,3l-6.3,4.2 c-0.9,0.6-1.8,0.9-2.6,0.9c-1,0-2-0.5-3-1.4C76.2,90,75,88.4,74,86.8c-1-1.7-2-3.6-3.1-5.9c-7.8,9.2-17.6,13.8-29.4,13.8 c-8.4,0-15.1-2.4-20-7.2c-4.9-4.8-7.4-11.2-7.4-19.2c0-8.5,3-15.4,9.1-20.6c6.1-5.2,14.2-7.8,24.5-7.8c3.4,0,6.9,0.3,10.6,0.8 c3.7,0.5,7.5,1.3,11.5,2.2v-7.3c0-7.6-1.6-12.9-4.7-16c-3.2-3.1-8.6-4.6-16.3-4.6c-3.5,0-7.1,0.4-10.8,1.3c-3.7,0.9-7.3,2-10.8,3.4 c-1.6,0.7-2.8,1.1-3.5,1.3c-0.7,0.2-1.2,0.3-1.6,0.3c-1.4,0-2.1-1-2.1-3.1v-4.9c0-1.6,0.2-2.8,0.7-3.5c0.5-0.7,1.4-1.4,2.8-2.1 c3.5-1.8,7.7-3.3,12.6-4.5c4.9-1.3,10.1-1.9,15.6-1.9c11.9,0,20.6,2.7,26.2,8.1c5.5,5.4,8.3,13.6,8.3,24.6V66.4z M45.8,81.6 c3.3,0,6.7-0.6,10.3-1.8c3.6-1.2,6.8-3.4,9.5-6.4c1.6-1.9,2.8-4,3.4-6.4c0.6-2.4,1-5.3,1-8.7v-4.2c-2.9-0.7-6-1.3-9.2-1.7 c-3.2-0.4-6.3-0.6-9.4-0.6c-6.7,0-11.6,1.3-14.9,4c-3.3,2.7-4.9,6.5-4.9,11.5c0,4.7,1.2,8.2,3.7,10.6 C37.7,80.4,41.2,81.6,45.8,81.6z M126.1,92.4c-1.8,0-3-0.3-3.8-1c-0.8-0.6-1.5-2-2.1-3.9L96.7,10.2c-0.6-2-0.9-3.3-0.9-4 c0-1.6,0.8-2.5,2.4-2.5h9.8c1.9,0,3.2,0.3,3.9,1c0.8,0.6,1.4,2,2,3.9l16.8,66.2l15.6-66.2c0.5-2,1.1-3.3,1.9-3.9c0.8-0.6,2.2-1,4-1 h8c1.9,0,3.2,0.3,4,1c0.8,0.6,1.5,2,1.9,3.9l15.8,67l17.3-67c0.6-2,1.3-3.3,2-3.9c0.8-0.6,2.1-1,3.9-1h9.3c1.6,0,2.5,0.8,2.5,2.5 c0,0.5-0.1,1-0.2,1.6c-0.1,0.6-0.3,1.4-0.7,2.5l-24.1,77.3c-0.6,2-1.3,3.3-2.1,3.9c-0.8,0.6-2.1,1-3.8,1h-8.6c-1.9,0-3.2-0.3-4-1 c-0.8-0.7-1.5-2-1.9-4L156,23l-15.4,64.4c-0.5,2-1.1,3.3-1.9,4c-0.8,0.7-2.2,1-4,1H126.1z M254.6,95.1c-5.2,0-10.4-0.6-15.4-1.8 c-5-1.2-8.9-2.5-11.5-4c-1.6-0.9-2.7-1.9-3.1-2.8c-0.4-0.9-0.6-1.9-0.6-2.8v-5.1c0-2.1,0.8-3.1,2.3-3.1c0.6,0,1.2,0.1,1.8,0.3 c0.6,0.2,1.5,0.6,2.5,1c3.4,1.5,7.1,2.7,11,3.5c4,0.8,7.9,1.2,11.9,1.2c6.3,0,11.2-1.1,14.6-3.3c3.4-2.2,5.2-5.4,5.2-9.5 c0-2.8-0.9-5.1-2.7-7c-1.8-1.9-5.2-3.6-10.1-5.2L246,52c-7.3-2.3-12.7-5.7-16-10.2c-3.3-4.4-5-9.3-5-14.5c0-4.2,0.9-7.9,2.7-11.1 c1.8-3.2,4.2-6,7.2-8.2c3-2.3,6.4-4,10.4-5.2c4-1.2,8.2-1.7,12.6-1.7c2.2,0,4.5,0.1,6.7,0.4c2.3,0.3,4.4,0.7,6.5,1.1 c2,0.5,3.9,1,5.7,1.6c1.8,0.6,3.2,1.2,4.2,1.8c1.4,0.8,2.4,1.6,3,2.5c0.6,0.8,0.9,1.9,0.9,3.3v4.7c0,2.1-0.8,3.2-2.3,3.2 c-0.8,0-2.1-0.4-3.8-1.2c-5.7-2.6-12.1-3.9-19.2-3.9c-5.7,0-10.2,0.9-13.3,2.8c-3.1,1.9-4.7,4.8-4.7,8.9c0,2.8,1,5.2,3,7.1 c2,1.9,5.7,3.8,11,5.5l14.2,4.5c7.2,2.3,12.4,5.5,15.5,9.6c3.1,4.1,4.6,8.8,4.6,14c0,4.3-0.9,8.2-2.6,11.6 c-1.8,3.4-4.2,6.4-7.3,8.8c-3.1,2.5-6.8,4.3-11.1,5.6C264.4,94.4,259.7,95.1,254.6,95.1z" style="fill:#FFFFFF"/> <g> <path d="M273.5,143.7c-32.9,24.3-80.7,37.2-121.8,37.2c-57.6,0-109.5-21.3-148.7-56.7c-3.1-2.8-0.3-6.6,3.4-4.4 c42.4,24.6,94.7,39.5,148.8,39.5c36.5,0,76.6-7.6,113.5-23.2C274.2,133.6,278.9,139.7,273.5,143.7z" style="fill-rule:evenodd;clip-rule:evenodd;fill:#FF9900"/> <path d="M287.2,128.1c-4.2-5.4-27.8-2.6-38.5-1.3c-3.2,0.4-3.7-2.4-0.8-4.5c18.8-13.2,49.7-9.4,53.3-5 c3.6,4.5-1,35.4-18.6,50.2c-2.7,2.3-5.3,1.1-4.1-1.9C282.5,155.7,291.4,133.4,287.2,128.1z" style="fill-rule:evenodd;clip-rule:evenodd;fill:#FF9900"/> </g> </g></svg>
<text x="306" y="107" text-anchor="middle" style="font: 650 13.5px Inter, sans-serif; fill: #0f172a; font-size:12px">Amazon MSK</text>
<text x="306" y="123" text-anchor="middle" style="font: 11px Inter, sans-serif; fill: #64748b">broker count</text>
<text x="306" y="139" text-anchor="middle" style="font: 11px Inter, sans-serif; fill: #64748b">instance size</text>
<line x1="418" y1="40" x2="418" y2="172" stroke-width="1.4" style="stroke:#cbd5e1"/>
<rect x="436" y="44" width="384" height="138" rx="14" stroke-width="1.4" stroke-dasharray="5 5" style="fill:#f8fafc;stroke:#cbd5e1"/>
<text x="450" y="62" style="font: 700 10px Inter, sans-serif; letter-spacing: 1.3px; fill: #94a3b8; fill:#047857">ON AZURE</text>
<rect x="450" y="84" width="116" height="68" rx="11" stroke-width="1.5" style="fill:#ffffff;stroke:#cbd5e1"/>
<text x="508" y="115" text-anchor="middle" style="font: 650 13.5px Inter, sans-serif; fill: #0f172a; font-size:12px">Your app</text>
<text x="508" y="131" text-anchor="middle" style="font: 11px Inter, sans-serif; fill: #64748b">same client</text>
<line x1="566" y1="118" x2="642" y2="118" stroke-width="2" marker-end="url(#eh1)" style="stroke:#047857"/>
<text x="604" y="109" text-anchor="middle" style="font: 10px 'SF Mono', ui-monospace, 'JetBrains Mono', Menlo, monospace; fill: #64748b; font-size:8.5px">Kafka wire</text>
<rect x="646" y="78" width="160" height="80" rx="11" stroke-width="1.5" style="fill:#ffffff;stroke:#cbd5e1"/>
<text x="726" y="99" text-anchor="middle" style="font: 650 13.5px Inter, sans-serif; fill: #0f172a; font-size:12px">Event Hubs namespace</text>
<text x="726" y="115" text-anchor="middle" style="font: 11px Inter, sans-serif; fill: #64748b">Kafka endpoint :9093</text>
<text x="726" y="131" text-anchor="middle" style="font: 11px Inter, sans-serif; fill: #64748b">capacity units</text>
<text x="726" y="147" text-anchor="middle" style="font: 600 11px Inter, sans-serif; fill: #047857; fill:#047857">no adapter in the path</text>
</svg>)

![On AWS, your application's Kafka client connects to the MSK brokers. On Azure, the same client connects with the same Kafka protocol to an Event Hubs namespace's Kafka endpoint on port 9093, with no Tensor9 adapter in between.](data:image/svg+xml;base64,<svg xmlns="http://www.w3.org/2000/svg" width="836" height="200" viewBox="0 0 836 200" role="img" aria-label="On AWS, your application's Kafka client connects to the MSK brokers. On Azure, the same client connects with the same Kafka protocol to an Event Hubs namespace's Kafka endpoint on port 9093, with no Tensor9 adapter in between."><style>text{font-family:Inter,-apple-system,BlinkMacSystemFont,'Segoe UI',Roboto,'Helvetica Neue',Arial,sans-serif;fill:#cbd5e1}</style>
<defs><marker id="eh1" viewBox="0 0 10 10" refX="8" refY="5" markerWidth="7" markerHeight="7" orient="auto-start-reverse"><path d="M0,0 L10,5 L0,10 z" style="fill:#64748b"/></marker></defs>
<rect x="16" y="44" width="384" height="138" rx="14" stroke-width="1.4" stroke-dasharray="5 5" style="fill:#0f172a;stroke:#475569"/>
<text x="30" y="62" style="font: 700 10px Inter, sans-serif; letter-spacing: 1.3px; fill: #64748b; fill:#64748b">ON AWS TODAY</text>
<rect x="30" y="84" width="116" height="68" rx="11" stroke-width="1.5" style="fill:#1e293b;stroke:#475569"/>
<text x="88" y="115" text-anchor="middle" style="font: 650 13.5px Inter, sans-serif; fill: #f1f5f9; font-size:12px">Your app</text>
<text x="88" y="131" text-anchor="middle" style="font: 11px Inter, sans-serif; fill: #94a3b8">Kafka client</text>
<line x1="146" y1="118" x2="222" y2="118" stroke-width="2" marker-end="url(#eh1)" style="stroke:#64748b"/>
<text x="184" y="109" text-anchor="middle" style="font: 10px 'SF Mono', ui-monospace, 'JetBrains Mono', Menlo, monospace; fill: #94a3b8; font-size:8.5px">Kafka wire</text>
<rect x="226" y="82" width="160" height="72" rx="11" stroke-width="1.5" style="fill:#1e293b;stroke:#475569"/>
<svg x="236" y="94" width="16" height="16" viewBox="0 0 304 182" preserveAspectRatio="xMidYMid meet" style="display: none"><g> <path d="M86.4,66.4c0,3.7,0.4,6.7,1.1,8.9c0.8,2.2,1.8,4.6,3.2,7.2c0.5,0.8,0.7,1.6,0.7,2.3c0,1-0.6,2-1.9,3l-6.3,4.2 c-0.9,0.6-1.8,0.9-2.6,0.9c-1,0-2-0.5-3-1.4C76.2,90,75,88.4,74,86.8c-1-1.7-2-3.6-3.1-5.9c-7.8,9.2-17.6,13.8-29.4,13.8 c-8.4,0-15.1-2.4-20-7.2c-4.9-4.8-7.4-11.2-7.4-19.2c0-8.5,3-15.4,9.1-20.6c6.1-5.2,14.2-7.8,24.5-7.8c3.4,0,6.9,0.3,10.6,0.8 c3.7,0.5,7.5,1.3,11.5,2.2v-7.3c0-7.6-1.6-12.9-4.7-16c-3.2-3.1-8.6-4.6-16.3-4.6c-3.5,0-7.1,0.4-10.8,1.3c-3.7,0.9-7.3,2-10.8,3.4 c-1.6,0.7-2.8,1.1-3.5,1.3c-0.7,0.2-1.2,0.3-1.6,0.3c-1.4,0-2.1-1-2.1-3.1v-4.9c0-1.6,0.2-2.8,0.7-3.5c0.5-0.7,1.4-1.4,2.8-2.1 c3.5-1.8,7.7-3.3,12.6-4.5c4.9-1.3,10.1-1.9,15.6-1.9c11.9,0,20.6,2.7,26.2,8.1c5.5,5.4,8.3,13.6,8.3,24.6V66.4z M45.8,81.6 c3.3,0,6.7-0.6,10.3-1.8c3.6-1.2,6.8-3.4,9.5-6.4c1.6-1.9,2.8-4,3.4-6.4c0.6-2.4,1-5.3,1-8.7v-4.2c-2.9-0.7-6-1.3-9.2-1.7 c-3.2-0.4-6.3-0.6-9.4-0.6c-6.7,0-11.6,1.3-14.9,4c-3.3,2.7-4.9,6.5-4.9,11.5c0,4.7,1.2,8.2,3.7,10.6 C37.7,80.4,41.2,81.6,45.8,81.6z M126.1,92.4c-1.8,0-3-0.3-3.8-1c-0.8-0.6-1.5-2-2.1-3.9L96.7,10.2c-0.6-2-0.9-3.3-0.9-4 c0-1.6,0.8-2.5,2.4-2.5h9.8c1.9,0,3.2,0.3,3.9,1c0.8,0.6,1.4,2,2,3.9l16.8,66.2l15.6-66.2c0.5-2,1.1-3.3,1.9-3.9c0.8-0.6,2.2-1,4-1 h8c1.9,0,3.2,0.3,4,1c0.8,0.6,1.5,2,1.9,3.9l15.8,67l17.3-67c0.6-2,1.3-3.3,2-3.9c0.8-0.6,2.1-1,3.9-1h9.3c1.6,0,2.5,0.8,2.5,2.5 c0,0.5-0.1,1-0.2,1.6c-0.1,0.6-0.3,1.4-0.7,2.5l-24.1,77.3c-0.6,2-1.3,3.3-2.1,3.9c-0.8,0.6-2.1,1-3.8,1h-8.6c-1.9,0-3.2-0.3-4-1 c-0.8-0.7-1.5-2-1.9-4L156,23l-15.4,64.4c-0.5,2-1.1,3.3-1.9,4c-0.8,0.7-2.2,1-4,1H126.1z M254.6,95.1c-5.2,0-10.4-0.6-15.4-1.8 c-5-1.2-8.9-2.5-11.5-4c-1.6-0.9-2.7-1.9-3.1-2.8c-0.4-0.9-0.6-1.9-0.6-2.8v-5.1c0-2.1,0.8-3.1,2.3-3.1c0.6,0,1.2,0.1,1.8,0.3 c0.6,0.2,1.5,0.6,2.5,1c3.4,1.5,7.1,2.7,11,3.5c4,0.8,7.9,1.2,11.9,1.2c6.3,0,11.2-1.1,14.6-3.3c3.4-2.2,5.2-5.4,5.2-9.5 c0-2.8-0.9-5.1-2.7-7c-1.8-1.9-5.2-3.6-10.1-5.2L246,52c-7.3-2.3-12.7-5.7-16-10.2c-3.3-4.4-5-9.3-5-14.5c0-4.2,0.9-7.9,2.7-11.1 c1.8-3.2,4.2-6,7.2-8.2c3-2.3,6.4-4,10.4-5.2c4-1.2,8.2-1.7,12.6-1.7c2.2,0,4.5,0.1,6.7,0.4c2.3,0.3,4.4,0.7,6.5,1.1 c2,0.5,3.9,1,5.7,1.6c1.8,0.6,3.2,1.2,4.2,1.8c1.4,0.8,2.4,1.6,3,2.5c0.6,0.8,0.9,1.9,0.9,3.3v4.7c0,2.1-0.8,3.2-2.3,3.2 c-0.8,0-2.1-0.4-3.8-1.2c-5.7-2.6-12.1-3.9-19.2-3.9c-5.7,0-10.2,0.9-13.3,2.8c-3.1,1.9-4.7,4.8-4.7,8.9c0,2.8,1,5.2,3,7.1 c2,1.9,5.7,3.8,11,5.5l14.2,4.5c7.2,2.3,12.4,5.5,15.5,9.6c3.1,4.1,4.6,8.8,4.6,14c0,4.3-0.9,8.2-2.6,11.6 c-1.8,3.4-4.2,6.4-7.3,8.8c-3.1,2.5-6.8,4.3-11.1,5.6C264.4,94.4,259.7,95.1,254.6,95.1z" style="fill:#252F3E"/> <g> <path d="M273.5,143.7c-32.9,24.3-80.7,37.2-121.8,37.2c-57.6,0-109.5-21.3-148.7-56.7c-3.1-2.8-0.3-6.6,3.4-4.4 c42.4,24.6,94.7,39.5,148.8,39.5c36.5,0,76.6-7.6,113.5-23.2C274.2,133.6,278.9,139.7,273.5,143.7z" style="fill-rule:evenodd;clip-rule:evenodd;fill:#FF9900"/> <path d="M287.2,128.1c-4.2-5.4-27.8-2.6-38.5-1.3c-3.2,0.4-3.7-2.4-0.8-4.5c18.8-13.2,49.7-9.4,53.3-5 c3.6,4.5-1,35.4-18.6,50.2c-2.7,2.3-5.3,1.1-4.1-1.9C282.5,155.7,291.4,133.4,287.2,128.1z" style="fill-rule:evenodd;clip-rule:evenodd;fill:#FF9900"/> </g> </g></svg><svg x="236" y="94" width="16" height="16" viewBox="0 0 304 182" preserveAspectRatio="xMidYMid meet" style="display: inline"><g> <path d="M86.4,66.4c0,3.7,0.4,6.7,1.1,8.9c0.8,2.2,1.8,4.6,3.2,7.2c0.5,0.8,0.7,1.6,0.7,2.3c0,1-0.6,2-1.9,3l-6.3,4.2 c-0.9,0.6-1.8,0.9-2.6,0.9c-1,0-2-0.5-3-1.4C76.2,90,75,88.4,74,86.8c-1-1.7-2-3.6-3.1-5.9c-7.8,9.2-17.6,13.8-29.4,13.8 c-8.4,0-15.1-2.4-20-7.2c-4.9-4.8-7.4-11.2-7.4-19.2c0-8.5,3-15.4,9.1-20.6c6.1-5.2,14.2-7.8,24.5-7.8c3.4,0,6.9,0.3,10.6,0.8 c3.7,0.5,7.5,1.3,11.5,2.2v-7.3c0-7.6-1.6-12.9-4.7-16c-3.2-3.1-8.6-4.6-16.3-4.6c-3.5,0-7.1,0.4-10.8,1.3c-3.7,0.9-7.3,2-10.8,3.4 c-1.6,0.7-2.8,1.1-3.5,1.3c-0.7,0.2-1.2,0.3-1.6,0.3c-1.4,0-2.1-1-2.1-3.1v-4.9c0-1.6,0.2-2.8,0.7-3.5c0.5-0.7,1.4-1.4,2.8-2.1 c3.5-1.8,7.7-3.3,12.6-4.5c4.9-1.3,10.1-1.9,15.6-1.9c11.9,0,20.6,2.7,26.2,8.1c5.5,5.4,8.3,13.6,8.3,24.6V66.4z M45.8,81.6 c3.3,0,6.7-0.6,10.3-1.8c3.6-1.2,6.8-3.4,9.5-6.4c1.6-1.9,2.8-4,3.4-6.4c0.6-2.4,1-5.3,1-8.7v-4.2c-2.9-0.7-6-1.3-9.2-1.7 c-3.2-0.4-6.3-0.6-9.4-0.6c-6.7,0-11.6,1.3-14.9,4c-3.3,2.7-4.9,6.5-4.9,11.5c0,4.7,1.2,8.2,3.7,10.6 C37.7,80.4,41.2,81.6,45.8,81.6z M126.1,92.4c-1.8,0-3-0.3-3.8-1c-0.8-0.6-1.5-2-2.1-3.9L96.7,10.2c-0.6-2-0.9-3.3-0.9-4 c0-1.6,0.8-2.5,2.4-2.5h9.8c1.9,0,3.2,0.3,3.9,1c0.8,0.6,1.4,2,2,3.9l16.8,66.2l15.6-66.2c0.5-2,1.1-3.3,1.9-3.9c0.8-0.6,2.2-1,4-1 h8c1.9,0,3.2,0.3,4,1c0.8,0.6,1.5,2,1.9,3.9l15.8,67l17.3-67c0.6-2,1.3-3.3,2-3.9c0.8-0.6,2.1-1,3.9-1h9.3c1.6,0,2.5,0.8,2.5,2.5 c0,0.5-0.1,1-0.2,1.6c-0.1,0.6-0.3,1.4-0.7,2.5l-24.1,77.3c-0.6,2-1.3,3.3-2.1,3.9c-0.8,0.6-2.1,1-3.8,1h-8.6c-1.9,0-3.2-0.3-4-1 c-0.8-0.7-1.5-2-1.9-4L156,23l-15.4,64.4c-0.5,2-1.1,3.3-1.9,4c-0.8,0.7-2.2,1-4,1H126.1z M254.6,95.1c-5.2,0-10.4-0.6-15.4-1.8 c-5-1.2-8.9-2.5-11.5-4c-1.6-0.9-2.7-1.9-3.1-2.8c-0.4-0.9-0.6-1.9-0.6-2.8v-5.1c0-2.1,0.8-3.1,2.3-3.1c0.6,0,1.2,0.1,1.8,0.3 c0.6,0.2,1.5,0.6,2.5,1c3.4,1.5,7.1,2.7,11,3.5c4,0.8,7.9,1.2,11.9,1.2c6.3,0,11.2-1.1,14.6-3.3c3.4-2.2,5.2-5.4,5.2-9.5 c0-2.8-0.9-5.1-2.7-7c-1.8-1.9-5.2-3.6-10.1-5.2L246,52c-7.3-2.3-12.7-5.7-16-10.2c-3.3-4.4-5-9.3-5-14.5c0-4.2,0.9-7.9,2.7-11.1 c1.8-3.2,4.2-6,7.2-8.2c3-2.3,6.4-4,10.4-5.2c4-1.2,8.2-1.7,12.6-1.7c2.2,0,4.5,0.1,6.7,0.4c2.3,0.3,4.4,0.7,6.5,1.1 c2,0.5,3.9,1,5.7,1.6c1.8,0.6,3.2,1.2,4.2,1.8c1.4,0.8,2.4,1.6,3,2.5c0.6,0.8,0.9,1.9,0.9,3.3v4.7c0,2.1-0.8,3.2-2.3,3.2 c-0.8,0-2.1-0.4-3.8-1.2c-5.7-2.6-12.1-3.9-19.2-3.9c-5.7,0-10.2,0.9-13.3,2.8c-3.1,1.9-4.7,4.8-4.7,8.9c0,2.8,1,5.2,3,7.1 c2,1.9,5.7,3.8,11,5.5l14.2,4.5c7.2,2.3,12.4,5.5,15.5,9.6c3.1,4.1,4.6,8.8,4.6,14c0,4.3-0.9,8.2-2.6,11.6 c-1.8,3.4-4.2,6.4-7.3,8.8c-3.1,2.5-6.8,4.3-11.1,5.6C264.4,94.4,259.7,95.1,254.6,95.1z" style="fill:#FFFFFF"/> <g> <path d="M273.5,143.7c-32.9,24.3-80.7,37.2-121.8,37.2c-57.6,0-109.5-21.3-148.7-56.7c-3.1-2.8-0.3-6.6,3.4-4.4 c42.4,24.6,94.7,39.5,148.8,39.5c36.5,0,76.6-7.6,113.5-23.2C274.2,133.6,278.9,139.7,273.5,143.7z" style="fill-rule:evenodd;clip-rule:evenodd;fill:#FF9900"/> <path d="M287.2,128.1c-4.2-5.4-27.8-2.6-38.5-1.3c-3.2,0.4-3.7-2.4-0.8-4.5c18.8-13.2,49.7-9.4,53.3-5 c3.6,4.5-1,35.4-18.6,50.2c-2.7,2.3-5.3,1.1-4.1-1.9C282.5,155.7,291.4,133.4,287.2,128.1z" style="fill-rule:evenodd;clip-rule:evenodd;fill:#FF9900"/> </g> </g></svg>
<text x="306" y="107" text-anchor="middle" style="font: 650 13.5px Inter, sans-serif; fill: #f1f5f9; font-size:12px">Amazon MSK</text>
<text x="306" y="123" text-anchor="middle" style="font: 11px Inter, sans-serif; fill: #94a3b8">broker count</text>
<text x="306" y="139" text-anchor="middle" style="font: 11px Inter, sans-serif; fill: #94a3b8">instance size</text>
<line x1="418" y1="40" x2="418" y2="172" stroke-width="1.4" style="stroke:#475569"/>
<rect x="436" y="44" width="384" height="138" rx="14" stroke-width="1.4" stroke-dasharray="5 5" style="fill:#0f172a;stroke:#475569"/>
<text x="450" y="62" style="font: 700 10px Inter, sans-serif; letter-spacing: 1.3px; fill: #64748b; fill:#6ee7b7">ON AZURE</text>
<rect x="450" y="84" width="116" height="68" rx="11" stroke-width="1.5" style="fill:#1e293b;stroke:#475569"/>
<text x="508" y="115" text-anchor="middle" style="font: 650 13.5px Inter, sans-serif; fill: #f1f5f9; font-size:12px">Your app</text>
<text x="508" y="131" text-anchor="middle" style="font: 11px Inter, sans-serif; fill: #94a3b8">same client</text>
<line x1="566" y1="118" x2="642" y2="118" stroke-width="2" marker-end="url(#eh1)" style="stroke:#6ee7b7"/>
<text x="604" y="109" text-anchor="middle" style="font: 10px 'SF Mono', ui-monospace, 'JetBrains Mono', Menlo, monospace; fill: #94a3b8; font-size:8.5px">Kafka wire</text>
<rect x="646" y="78" width="160" height="80" rx="11" stroke-width="1.5" style="fill:#1e293b;stroke:#475569"/>
<text x="726" y="99" text-anchor="middle" style="font: 650 13.5px Inter, sans-serif; fill: #f1f5f9; font-size:12px">Event Hubs namespace</text>
<text x="726" y="115" text-anchor="middle" style="font: 11px Inter, sans-serif; fill: #94a3b8">Kafka endpoint :9093</text>
<text x="726" y="131" text-anchor="middle" style="font: 11px Inter, sans-serif; fill: #94a3b8">capacity units</text>
<text x="726" y="147" text-anchor="middle" style="font: 600 11px Inter, sans-serif; fill: #6ee7b7; fill:#6ee7b7">no adapter in the path</text>
</svg>)

#### Estimating namespace capacity

MSK capacity is declared as a broker count and instance type, with storage and placement per broker. Event Hubs capacity is set on a namespace using throughput units or processing units. Tensor9 estimates namespace capacity from broker count multiplied by vCPUs per broker.

Brokers with at least 16 vCPUs each, such as `kafka.m5.4xlarge`, select Premium processing units. Smaller brokers select Standard throughput units. Basic is excluded because it has no Kafka endpoint.

The build reports this conversion as a lossy translation, because machine size does not decide your workload's message throughput. Load-test the generated capacity and adjust it from measured traffic.

#### Provision topics as Event Hubs

The generated Terraform creates the namespace. It creates no Event Hubs because an MSK cluster resource does not declare topics: Kafka topics are created by producers or administrators at runtime. `aws_msk_configuration` contains `server.properties` settings, not a topic list.

Each Kafka topic needs an Event Hub in the namespace. Create them before producing messages; this backend does not create them on first use.

#### Configure authentication

Configure clients to use an Event Hubs Shared Access Signature (SAS) policy or Microsoft Entra identity. MSK's SASL/SCRAM, mutual TLS and IAM configurations do not transfer directly.

You configure namespace authentication separately from the generated stack. Credentials are kept in the Cloud Adapter deployment's secret store; the generated Terraform contains no SAS key or connection string.

Event Hubs requires TLS and encrypts stored data by default, so MSK's `encryption_info` is not translated. Configure a customer-managed encryption key separately on Azure if required.

#### Limitations

Where Event Hubs and MSK differ

* **Kafka transactions and exactly-once delivery are not fully supported.** Producing and consuming over the Kafka protocol work unchanged, but the Event Hubs Kafka endpoint does not offer full Kafka transaction and idempotent-producer behaviour. An application that relies on exactly-once delivery through Kafka transactions cannot use this backend as is.
* **Partition counts behave differently: on Standard they are fixed at creation.** On Standard, an Event Hub's partition count cannot change after creation; Premium and Dedicated can increase it but never decrease it, as Kafka does. Size partitions for the consumer parallelism you expect, because on Standard the only way to change it is a new Event Hub.
* **Capacity behaves differently: it is bought separately from partitions.** On Kafka, partitions set parallelism and much of your throughput headroom. On Event Hubs, throughput units (Standard) or processing units (Premium) are bought separately from partitions, so a partition count copied from MSK does not bring its throughput with it.
* **Consumer-group offsets behave differently: there is no `__consumer_offsets` topic.** Event Hubs keeps offsets in its own store. Committing and reading offsets through the Kafka client works as usual; tools that read the offsets topic directly, or depend on its retention and compaction, do not work here.
* **Runtime Kafka administration is only partly supported.** Topics are Event Hubs you create up front, and broker administration and ACLs differ from Kafka. Treat code that creates topics or manages ACLs through AdminClient at runtime as needing rework.
* **Pinning a Kafka version is not supported.** MSK's `kafka_version` has no counterpart: Event Hubs sets its own supported Kafka protocol version, and you cannot choose or freeze it.
* **Custom `server.properties` settings are not kept.** MSK's `configuration_info` (retention hours, default partition counts and the rest) has no namespace-level equivalent. The settings that exist are per Event Hub and are set after creation.
* **Placing brokers across availability zones is not supported.** An Event Hubs namespace is a regional service with no brokers, so MSK's per-broker subnets and zone placement have nothing to map to.

#### Other considerations

* **Update the client endpoint and authentication.** Repoint the bootstrap servers at the namespace's Kafka endpoint on port 9093 and switch the SASL configuration to a SAS policy or a Microsoft Entra identity. Produce and consume code, serializers and partitioning logic stay the same.
* **Moving from AWS: the namespace starts empty.** Messages still in MSK are not copied. Plan a cutover in which producers switch over and consumers drain the old cluster; Kafka's retention limits how long that can take.
* **Revisit capacity after launch.** The generated tier and capacity are estimated from your brokers, not measured from your traffic. Watch throughput-unit utilisation once real load arrives; Standard's throughput units and Premium's processing units are both adjustable.
* **Names stay the same across builds.** The namespace name comes from the stack's stored identity and the original cluster name, so the same stack always builds to the same namespace and a re-plan does not propose replacing infrastructure that has not changed.

## On DigitalOcean

### DigitalOcean Managed Kafka

| Operation | Area | Support | Depth | Notes |
| - | - | - | - | - |
| Monitoring / broker-log delivery / at-rest KMS / VPC placement | AWS control plane | Out of scope | Full surface | Configure backend monitoring and broker logs in place of MSK's CloudWatch, Prometheus, S3 and Firehose settings. Storage encryption uses the backend's key and storage configuration. Select target subnets and failure domains separately from the supplied bootstrap endpoint. |
| Broker config (custom broker-config revision) | Admin | Partial | Most usage | broker-config tuning is more limited than a broker you administer directly; MSK's custom broker-config revision is not reproduced |
| Partition semantics | Admin | Supported | Most usage | partitions are a real Kafka broker's own |
| Topic admin (create / delete / configs) | Admin | Supported | Most usage | the Kafka AdminClient talks to a real managed Kafka broker, so topic and partition admin work natively |
| ACLs / SASL auth | Auth | Partial | Full surface | DigitalOcean issues its own SASL/TLS credentials out of band; MSK's IAM auth has no analog, and broker-config tuning is more limited than a broker you administer directly |
| Offset commit (\_\_consumer\_offsets) | Consume | Supported | Most usage | offsets commit to the real broker's \_\_consumer\_offsets, as on Kafka |
| Glue Schema Registry | Ecosystem | Out of scope | Full surface | AWS Glue Schema Registry has no target-side analog; run a Kafka-native schema registry (Confluent/Apicurio) alongside the broker if you need one |
| MSK Connect | Ecosystem | Out of scope | Full surface | MSK Connect (managed Kafka Connect) is not provisioned; run Kafka Connect yourself against the broker if you need connectors |
| acks / idempotence / transactions | Producer semantics | Supported | Most usage | acks, idempotence, and transactions are a real managed Kafka engine's own |
| Broker sizing (MSK broker instance type → CPU / memory / storage) | Sizing | Partial | Most usage | the managed plan / node size is chosen out of band on DigitalOcean, not derived from the MSK broker instance type or storage volume size |
| Tiered storage | Storage | Out of scope | Full surface | MSK's tiered storage is not configured on the backend; a self-hosted Kafka broker has native tiered storage (KIP-405, production-ready in Kafka 3.9+) you can enable yourself with a remote-store backend, and the managed backends expose no equivalent knob; retention is the target broker's own local or managed storage |
| Consume (consumer groups) | Wire protocol | Supported | Common | your Kafka consumer and consumer-group membership run unchanged over the wire |
| Produce (Kafka wire) | Wire protocol | Supported | Common | your Kafka producer runs unchanged; the adapter supplies the backend's bootstrap-broker endpoint to your producer |

#### How it works

Your producers and consumers keep their Kafka clients and connect directly to DigitalOcean Managed Kafka over the Kafka protocol. Tensor9 supplies the bootstrap endpoint; there is no Tensor9 proxy between client and broker. Broker metadata can return further advertised addresses, so clients need network access and TLS trust for those addresses as well as the bootstrap address.

Authentication changes with the broker: DigitalOcean issues its own SASL/TLS credentials out of band; MSK's IAM auth has no analog. Check producer acknowledgement, idempotence and transaction settings against the support table for this broker; a Kafka-compatible endpoint does not guarantee every Kafka administrative or transactional feature.

#### Limitations

* **Moving records, offsets and consumer-group state is not supported.** A new broker starts without the source records, offsets or consumer groups, and source offsets cannot be applied to a different log. If retained history must move, plan a separate replication process. - **You must replace AWS IAM authentication, MSK Connect and Glue Schema Registry separately.** Changing the bootstrap servers does not replace those dependencies.

#### Other considerations

**Who runs what.** DigitalOcean operates durability and HA; broker-config tuning is more limited than a broker you administer directly. Topic partitions hold the retained log, and consumer-group offsets record progress.

**Before cutover.** Coordinate producer and consumer cutover. Review topic creation, retention, partition counts and broker configuration on DigitalOcean Managed Kafka, and set up monitoring, backup or recovery and certificate rotation first.

**Performance.** It depends on the broker, storage and workload; this profile has no Tensor9 broker benchmark.

## On Google Cloud

### Managed Service for Apache Kafka

| Operation | Area | Support | Depth | Notes |
| - | - | - | - | - |
| Monitoring / broker-log delivery / at-rest KMS / VPC placement | AWS control plane | Out of scope | Full surface | Configure backend monitoring and broker logs in place of MSK's CloudWatch, Prometheus, S3 and Firehose settings. Storage encryption uses the backend's key and storage configuration. Select target subnets and failure domains separately from the supplied bootstrap endpoint. |
| Broker config (custom broker-config revision) | Admin | Partial | Most usage | Google manages the broker configuration; per-topic settings (retention, partition count) are yours to set, but MSK's custom broker-config revision has no equivalent |
| Partition semantics | Admin | Supported | Most usage | partitions are a real Kafka broker's own; create and grow them via the AdminClient as on Kafka |
| Topic admin (create / delete / configs) | Admin | Supported | Most usage | the Kafka AdminClient talks to a real Apache Kafka broker, so topic, config, and partition admin all work natively |
| ACLs / SASL auth | Auth | Partial | Full surface | clients authenticate through Google Cloud IAM over SASL\_SSL/OAUTHBEARER with Google's login callback handler; MSK's IAM auth has no analog, and SASL/SCRAM credentials and mTLS client certificates have no equivalent, so producers and consumers swap their callback handler and credentials once |
| Offset commit (\_\_consumer\_offsets) | Consume | Supported | Most usage | offsets commit to the real broker's \_\_consumer\_offsets, exactly as on Kafka |
| Glue Schema Registry | Ecosystem | Out of scope | Full surface | AWS Glue Schema Registry has no target-side analog; run a Kafka-native schema registry (Confluent/Apicurio) alongside the broker if you need one |
| MSK Connect | Ecosystem | Out of scope | Full surface | MSK Connect (managed Kafka Connect) is not provisioned; run Kafka Connect yourself against the broker if you need connectors |
| acks / idempotence / transactions | Producer semantics | Supported | Most usage | acks, idempotence, and transactions are a real Apache Kafka broker's own, because Google runs Kafka itself rather than a Kafka-compatible surface |
| Broker sizing (MSK broker instance type → CPU / memory / storage) | Sizing | Partial | Most usage | Managed Kafka sizes the cluster (vCPU and memory across the whole fleet) rather than a per-broker instance type, so the source instance capacity is multiplied by broker count to estimate cluster capacity and the per-broker EBS volume becomes the managed per-broker disk |
| Tiered storage | Storage | Out of scope | Full surface | MSK's tiered storage is not configured on the backend; a self-hosted Kafka broker has native tiered storage (KIP-405, production-ready in Kafka 3.9+) you can enable yourself with a remote-store backend, and the managed backends expose no equivalent knob; retention is the target broker's own local or managed storage |
| Consume (consumer groups) | Wire protocol | Supported | Common | your Kafka consumer and consumer-group membership run unchanged over the wire |
| Produce (Kafka wire) | Wire protocol | Supported | Common | your Kafka producer runs unchanged; the adapter supplies the backend's bootstrap-broker endpoint to your producer |

#### How it works

Your producers and consumers keep their Kafka clients and connect directly to Google Managed Service for Apache Kafka over the Kafka protocol. Tensor9 supplies the bootstrap endpoint; there is no Tensor9 proxy between client and broker. Broker metadata can return further advertised addresses, so clients need network access and TLS trust for those addresses as well as the bootstrap address.

Authentication changes with the broker: clients authenticate through Google Cloud IAM over SASL\_SSL/OAUTHBEARER; MSK IAM, SASL/SCRAM, and mTLS each need a one-time client-side handler and credential swap. Check producer acknowledgement, idempotence and transaction settings against the support table for this broker; a Kafka-compatible endpoint does not guarantee every Kafka administrative or transactional feature.

#### Limitations

* **Moving records, offsets and consumer-group state is not supported.** A new broker starts without the source records, offsets or consumer groups, and source offsets cannot be applied to a different log. If retained history must move, plan a separate replication process. - **You must replace AWS IAM authentication, MSK Connect and Glue Schema Registry separately.** Changing the bootstrap servers does not replace those dependencies.

#### Other considerations

**Who runs what.** Google operates durability and HA; capacity is cluster-wide vCPU/memory rather than a broker instance type you pick, and the cluster is reachable only inside your VPC. Topic partitions hold the retained log, and consumer-group offsets record progress.

**Before cutover.** Coordinate producer and consumer cutover. Review topic creation, retention, partition counts and broker configuration on Google Managed Service for Apache Kafka, and set up monitoring, backup or recovery and certificate rotation first.

**Performance.** It depends on the broker, storage and workload; this profile has no Tensor9 broker benchmark.

## On OCI

### OCI Streaming

| Operation | Area | Support | Depth | Notes |
| - | - | - | - | - |
| Monitoring / broker-log delivery / at-rest KMS / VPC placement | AWS control plane | Out of scope | Full surface | Configure backend monitoring and broker logs in place of MSK's CloudWatch, Prometheus, S3 and Firehose settings. Storage encryption uses the backend's key and storage configuration. Select target subnets and failure domains separately from the supplied bootstrap endpoint. |
| Broker config (custom broker-config revision) | Admin | Partial | Most usage | OCI exposes a subset of broker configuration settings; MSK's custom broker-config revision has no counterpart |
| Partition semantics | Admin | Partial | Most usage | partitions are the stream pool's, under OCI quotas |
| Topic admin (create / delete / configs) | Admin | Partial | Most usage | topics are created explicitly (auto-create is off); OCI exposes a subset of Kafka's broker configuration settings, not the full broker admin surface |
| ACLs / SASL auth | Auth | Partial | Full surface | authentication is OCI auth tokens at the stream-pool endpoint, not MSK's SASL/SCRAM, mTLS, or IAM; encryption and monitoring move to OCI-managed |
| Offset commit (\_\_consumer\_offsets) | Consume | Partial | Most usage | consumer-group offsets use OCI Streaming's managed offset store; the semantics track Kafka's with OCI's quotas |
| Glue Schema Registry | Ecosystem | Out of scope | Full surface | AWS Glue Schema Registry has no target-side analog; run a Kafka-native schema registry (Confluent/Apicurio) alongside the broker if you need one |
| MSK Connect | Ecosystem | Out of scope | Full surface | MSK Connect (managed Kafka Connect) is not provisioned; run Kafka Connect yourself against the broker if you need connectors |
| acks / idempotence / transactions | Producer semantics | Partial | Most usage | produce over the Kafka wire runs unchanged, but full idempotence/transactions are not complete on OCI Streaming's Kafka-compatible API, and acks and throughput are bounded by OCI's quotas rather than a broker you tune |
| Broker sizing (MSK broker instance type → CPU / memory / storage) | Sizing | Partial | Most usage | the stream pool is not a broker you size; capacity is OCI's partitions and quotas, not an instance type or a volume you set |
| Tiered storage | Storage | Out of scope | Full surface | MSK's tiered storage is not configured on the backend; a self-hosted Kafka broker has native tiered storage (KIP-405, production-ready in Kafka 3.9+) you can enable yourself with a remote-store backend, and the managed backends expose no equivalent knob; retention is the target broker's own local or managed storage |
| Consume (consumer groups) | Wire protocol | Supported | Common | your Kafka consumer and consumer-group membership run unchanged over the wire |
| Produce (Kafka wire) | Wire protocol | Supported | Common | your Kafka producer runs unchanged; the adapter supplies the backend's bootstrap-broker endpoint to your producer |

#### How it works

Your producers and consumers keep their Kafka clients and connect directly to OCI Streaming over the Kafka protocol. Tensor9 supplies the bootstrap endpoint; there is no Tensor9 proxy between client and broker. Broker metadata can return further advertised addresses, so clients need network access and TLS trust for those addresses as well as the bootstrap address.

Authentication changes with the broker: authentication is OCI auth tokens at the stream-pool endpoint, not MSK's SASL/SCRAM, mTLS, or IAM; your Kafka clients configure OCI's auth instead. Check producer acknowledgement, idempotence and transaction settings against the support table for this broker; a Kafka-compatible endpoint does not guarantee every Kafka administrative or transactional feature.

#### Limitations

* **Moving records, offsets and consumer-group state is not supported.** A new broker starts without the source records, offsets or consumer groups, and source offsets cannot be applied to a different log. If retained history must move, plan a separate replication process. - **You must replace AWS IAM authentication, MSK Connect and Glue Schema Registry separately.** Changing the bootstrap servers does not replace those dependencies.

#### Other considerations

**Who runs what.** Oracle operates durability and HA; partitions and retention live under OCI's quotas rather than a broker you tune directly. Topic partitions hold the retained log, and consumer-group offsets record progress.

**Before cutover.** Coordinate producer and consumer cutover. Review topic creation, retention, partition counts and broker configuration on OCI Streaming, and set up monitoring, backup or recovery and certificate rotation first.

**Performance.** It depends on the broker, storage and workload; this profile has no Tensor9 broker benchmark.

## On Scaleway

### Scaleway Clusters for Apache Kafka

| Operation | Area | Support | Depth | Notes |
| - | - | - | - | - |
| Monitoring / broker-log delivery / at-rest KMS / VPC placement | AWS control plane | Out of scope | Full surface | Configure backend monitoring and broker logs in place of MSK's CloudWatch, Prometheus, S3 and Firehose settings. Storage encryption uses the backend's key and storage configuration. Select target subnets and failure domains separately from the supplied bootstrap endpoint. |
| Broker config (custom broker-config revision) | Admin | Out of scope | Most usage | a custom MSK configuration (aws\_msk\_configuration server.properties - log.retention.hours, num.partitions and the rest) is NOT projected; tune the Scaleway cluster's topic and broker settings after it is provisioned |
| Partition semantics | Admin | Supported | Most usage | partitions are a real Kafka broker's own |
| Topic admin (create / delete / configs) | Admin | Supported | Most usage | the Kafka AdminClient talks to a real broker, so topic and partition admin work natively |
| ACLs / SASL auth | Auth | Partial | Full surface | Scaleway issues its OWN credentials for the cluster (the resource carries user\_name/password) rather than translating MSK's. A cluster whose clients use SASL/SCRAM or mTLS is reconfigured onto those credentials. A cluster whose clients use SASL/IAM is a HARDER change and is called out separately below - that one is a mechanism, not a credential |
| Offset commit (\_\_consumer\_offsets) | Consume | Supported | Most usage | offsets commit to the real broker's \_\_consumer\_offsets, as on Kafka |
| Glue Schema Registry | Ecosystem | Out of scope | Full surface | AWS Glue Schema Registry has no target-side analog; run a Kafka-native schema registry (Confluent/Apicurio) alongside the broker if you need one |
| MSK Connect | Ecosystem | Out of scope | Full surface | MSK Connect (managed Kafka Connect) is not provisioned; run Kafka Connect yourself against the broker if you need connectors |
| acks / idempotence / transactions | Producer semantics | Supported | Most usage | acks, idempotence and transactions are a real Kafka engine's own - Scaleway runs Apache Kafka 4.1, not a Kafka-compatible protocol layer |
| Broker sizing (MSK broker instance type → CPU / memory / storage) | Sizing | Partial | Most usage | the MSK broker instance type is not carried across: Scaleway sizes by its own node-type catalogue, and the build emits the smallest of the three it offers (brokernode-shared-2c-8g, 2 vCPU / 8 GB). Broker STORAGE does follow - a requested volume is rounded UP to Scaleway's 10 GB floor in 5 GB steps |
| Tiered storage | Storage | Out of scope | Full surface | MSK's tiered storage is not configured on the backend; a self-hosted Kafka broker has native tiered storage (KIP-405, production-ready in Kafka 3.9+) you can enable yourself with a remote-store backend, and the managed backends expose no equivalent knob; retention is the target broker's own local or managed storage |
| Consume (consumer groups) | Wire protocol | Supported | Common | your Kafka consumer and consumer-group membership run unchanged over the wire |
| Produce (Kafka wire) | Wire protocol | Supported | Common | your Kafka producer runs unchanged; the adapter supplies the backend's bootstrap-broker endpoint to your producer |

## Install and run

The documentation and SLAs are public. Downloading and running the Cloud Adapter binary requires an entitled customer account. Set `T9_API_KEY` as described in [Install and Authenticate](https://docs.tensor9.com/cloud-adapter-early-access/getting-started/install-and-authenticate.md), then list the adapters your account may use with this origin:

```sh theme={null}
tensor9 adapt svc list \
  -origin aws::1.0.0::msk::kafka
```

The result is limited to directed mappings for this origin that your account is entitled to use. Use a returned backend identifier when configuring the adapter or investigating a request.

Request binary access from [hello@tensor9.com](mailto:hello@tensor9.com) if your account does not yet include this direction.

## Existing data and credentials

Selecting a backend does not copy existing data, credentials or access policies. Plan and verify migration separately before changing an application's endpoint. Do not assume an identifier, credential or encrypted value from the origin service works unchanged on the target.

## Configure, tune and debug

Start with [setup](https://docs.tensor9.com/cloud-adapter-early-access/getting-started/overview.md) and [configuration](https://docs.tensor9.com/cloud-adapter-early-access/configuration/overview.md). Use [tuning](https://docs.tensor9.com/cloud-adapter-early-access/tuning/overview.md) to understand supported request tags, [debugging](https://docs.tensor9.com/cloud-adapter-early-access/debugging/overview.md) to investigate a request, and [High Fidelity Cloud Emulators](https://docs.tensor9.com/cloud-adapter-early-access/local-testing/overview.md) to validate a bounded reproduction.

For requests that go through an entitled service adapter, use [tensor9 explain](https://docs.tensor9.com/cloud-adapter-early-access/debugging/explain.md) and [x-t9-explain](https://docs.tensor9.com/cloud-adapter-early-access/debugging/response-headers.md) to inspect the selected mapping.


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