Why do we need to FULLY RESTART the client just because of heavy server traffic?
When you see a ‘cannot connect due to heavy traffic’ this is a temporary issue … ie, eventually it will work … however, since this error kills the client, you’ve to do a full restart? What the hell?
The client isn’t exactly a thin client and it won’t restart in 10 seconds … it takes ages and we’re getting the ‘amazon’ unskippable splash screen just to imprint our anger and frustration on your brand (rightly so I guess) …
I’d suggestion using amazons AWS API Gateway … it might help … maybe have your database on Amazons Aurora RDS and get some lambda calls going to the readonly sides of the cluster for this sort of login crap … add more readers to your cluster as you need … you know scale a little …