← This weekCase studyData engineering & the warehouse/lakehouseConfluentAmazonConfluent has optimized its Amazon OpenSearch Service by transitioning from r6gd to the oi2 instance family, resulting in a 46% reduction in nodes and doubling the speed of indexing. This shift has decreased write backpressure and costs, despite a higher per-node price.
MyDataWork POV — The alarming part of Confluent's move is the potential fragility introduced by cutting nodes so drastically. While the performance gains are impressive, a 46% reduction in node count raises concerns about system resilience and fault tolerance. If a smaller fleet faces unexpected load spikes or failures, the risk of service disruption could outweigh the cost savings. Organizations must weigh these risks carefully before following suit.
Discussion happens on Reddit — no comments are hosted here.