given a lost write to Redis would translate to corruption or missing data at the filesystem level, the only "safe" way to run this ATM is using Redis' extremely

given a lost write to Redis would translate to corruption or missing data at the filesystem level, the only "safe" way to run this ATM is using Redis' extremely inefficient "always fsync" setting for its AOF log [1]. Keep in mind that Elasticache does not support it (in general, it doesn't really support running Redis in a durable way). [1] https://redis.io/topics/persistence#:~:text=The%20suggested%20(and%20default)%20policy,perform%20a%20single%20fsync%20operation https://redis.io/topics/persistence#:~:text=The%20suggested%....