cache write-through versus write-behind, which one's better for your use case? dont you think?

hey everyone, i'm wrestling with a decision for a new service and wanted to get your collective wisdom. we're building a service that will see a lot of writes and reads, and we definitely need caching. my main question is around write strategies, write-through or write-behind. write-through seems safer because the cache and database are updated together, ensuring consistency. but write-behind could offer better write performance by acknowledging the write before the db update is complete. what are your experiences? when have you found one strategy to be clearly superior over the other? what kind of load patterns or consistency requirements push you towards one over the other?