Re:AWS NLBs and the mixed up TCP connections
by amirs on Thursday October 22, 2020 @08:15AM
(#24857186)
That's a really interesting point. The startup I currently work for only uses a single AZ due to financial concerns (and some performance as well), but I assume we'll have to move to more AZs for reliability.
Would you advise the same for clusters of RDS and Elasticache?
I'm wondering how you would even go about having two separate data sources, how would this be manageable?
[ Parent
| on HN ]
Re:AWS NLBs and the mixed up TCP connections
by capableweb on Thursday October 22, 2020 @02:17PM
(#24861311)
Before assuming that your reliability would be increased by adding more AZs, verify where the problems of reliability comes from in the first place. I find more times than not, the down times comes from people applying changes, not when you just leave things running like they are. It's only if the AZ or underlying machines has troubles, that you should start thinking of expanding to other AZs
Re:AWS NLBs and the mixed up TCP connections
by jniedrauer on Thursday October 22, 2020 @12:11PM
(#24859601)
I've found that for RDS, a writer instance and a hot standby reader instance with automatic failover work pretty well. When a failover happens, you're usually looking at about 30 seconds of downtime, which is "good enough" for most purposes.