746 karma · joined February 12, 2010
AWS RDS in multi-AZ deployment gives you two availability zones. Aurora gives you three. What kind of scenario would be used to justify three AZ’s for the purposes of high availability?
The one and only time I ever did this was when I was young and in extremely good health (daily intense exercise, excellent diet, no health conditions). Slightly worried about doing it again today. Also, quite concerned having since learned that brain mass is the first stored energy source your body will go after during what is effectively starvation. Perhaps someone more knowledge on here can comment on how true that is.
I've been wondering if this is indeed a best practice or something that should be used only when necessary. Should every database query really abort if the connection to the client fails?
In addition, if you follow this advice you now need to check if the returned error is context.Cancelled which warrants an HTTP 400 response.
• iOS: Swift
• Android: Kotlin
• Server: Go (Golang), PostgreSQL
• Web: Angular, Hugo
Happy customers, mature product, experienced remote team, steady continuous growth, zero outside funding, recession proof business.
Say hello at kirill@getfillet.com!
"Prepared statements only last for the duration of the current database session. When the session ends, the prepared statement is forgotten, so it must be recreated before being used again. This also means that a single prepared statement cannot be used by multiple simultaneous database clients..."[1]
* Undocumented surprise error when user tries to re-subscribe in a different currency or change currency. Solution is to recreate the whole customer.
* Docs instruct to subscribe new users to free plan which is actually a bad practice for reasons that include first bullet point.
* Lack of docs/guidance for China payment systems and seeing Stripe server and frontend errors in testing environment.