Oh my indeed. > That kind of behavior does not help achieving high production quality and providing robust and reliable services. Right, so since it's the mes

Oh my indeed. > That kind of behavior does not help achieving high production quality and providing robust and reliable services. Right, so since it's the messenger (assertion) that brought news of defeat in battle, you kill the messenger instead of trying to win the next battle. Your problem is that the entire business seems to hinge on a single point of failure - if the server binary dies, you lose customers. This has nothing to do with what some library does or does not do, it's just a horribly designed system. That crash should have made you all stop and think real hard about what you're doing because clearly it's not working: 1. Don't write bugs in the first place. No I'm not kidding. Your tests clearly suck so fix them, make sure you do proper PR reviews, make sure to leverage your type system to the fullest, use all available tooling, etc. 2. Design your system be resilient to the server binary dying because I assure you, there's nothing you can do to prevent it from happening for one reason or another.