Configure Clients to Eliminate AZ Networking Costs

How to configure your Kafka clients to keep all traffic zone-local.

With WarpStream, there are no Availability Zone (AZ) networking costs between agents. This means you can produce and consume data from different AZs without incurring additional networking expenses. The same applies to agent-client communication: WarpStream eliminates AZ networking costs, allowing you to connect clients only to agents within the same AZ.

Requirements for Zonal Alignment of Kafka clients

To ensure your Kafka clients connect to agents within the same availability zone, you need to:

1. Ensure there is at least one agent in the same availability zone as your clients.

2. Append the following value to your Kafka client's ClientID: ws_az=<your-az>. This flag indicates the AZ in which the client is operating.

Example

Here is an example of how to set up the clientID with the AZ flag:

availabilityZone := lookupAZ()
clientID := fmt.Sprintf("ws_az=%s",availabilityZone)

Our warpstream-go library has sample code that demonstrates how to query for your application's availability zone in every major cloud.