> All of this generates data that needs to be written to our databases. Sometimes our systems max out, and just as when someone exercises too hard and has to stop and catch their breath, our servers also become exhausted and need to recover. When that happens, they quit working, and our site and apps become unresponsive Is this a tortured analogy, or are their servers actually crashing under load?
Alternatively they might be doing something weird involving periodically flushing the database from memory and onto disc.
That wouldn't mean "crashing", but likely would mean the database wasn't usable as a database.