Architecture: Confluent Cloud Gateway

Your Kafka producer has one job at startup: read bootstrap.servers , open a connection, and start sending. That single line of config is also its biggest liability. The host and port are baked in when the application boots, and a Kafka client is not designed to swap them out while running. So the day your active cluster goes dark, every producer and consumer pointing at it is stuck until that cluster comes back or the connection times out. You ca… Read More

Architecture: Kafka Active-Active with Confluent Bidirectional Cluster Linking

Your Confluent Cluster Linking DR setup is solid. Two clusters, one link, replication lag under five seconds. Then your platform team asks a reasonable question: the DR cluster is sitting idle, your producers in the secondary region are paying cross-regional latency on every write, and a failover still involves a manual promotion step. Can both clusters carry live traffic simultaneously? Can a regional outage become a non-event rather than an in… Read More

Architecture: Confluent Cluster Linking

Your primary Kafka cluster handles millions of events per day without complaint. Then a cloud provider has a regional outage. The brokers are unreachable, the consumer lag metrics are gone, and your on-call engineer is staring at a 45-minute RTO commitment they have no clear path to meeting. The standard answer for years was MirrorMaker 2: deploy a separate replication cluster, manage connector configs, accept that consumer offsets won't tra… Read More