How we saved $100k a month with Kafka networking optimization
1–5 of 5 posts
Re: How we saved $100k a month with Kafka networking optimization
#2Re: How we saved $100k a month with Kafka networking optimization
#3Given the way you were able to logically group data so that producers and their consumers are in the same zone, would it not have been simpler to just create three completely independent 3-node clusters, rather than worry about all this at the partition and keying level?
Re: How we saved $100k a month with Kafka networking optimization
#4Given the way you were able to logically group data so that producers and their consumers are in the same zone, would it not have been simpler to just create three completely independent 3-node clusters, rather than worry about all this at the partition and keying level?
Maybe if one AZ fails only 1/3 of the producer, topics and consumers fail. Seems like a lot of overhead for a relatively minor advantage.
Re: How we saved $100k a month with Kafka networking optimization
#5Given the way you were able to logically group data so that producers and their consumers are in the same zone, would it not have been simpler to just create three completely independent 3-node clusters, rather than worry about all this at the partition and keying level?
Some clusters are hosting hundreds of topics, thousands of partitions and used (consumers/producers) by hundreds of services.