Write-through vs write-behind caching: understanding the consistency trade-offs

when dealing with our inventory system, where accuracy is paramount, we've been struggling with the best caching strategy for writes. write-through caching seems safest for consistency, ensuring the database is updated before the cache, but the added latency for every write is becoming a problem for user experience during peak times. on the other hand, write-behind caching offers better performance, but the risk of data loss if the cache server goes down before persisting to the database is a significant concern for us. we also experimented briefly with write-around, where data is written directly to the database and only loaded into the cache on a read miss. this led to cache miss storms right after bulk updates, which was not ideal. what strategies have others found effective in high-consistency, high-throughput write scenarios where performance can't be completely sacrificed? especially interested in how you manage the trade-offs between consistency, latency, and durability.