I genuinely needn’t describe the sharpness of ‘First universe Problems’… but incase you’ve been surviving low-level a rock, it’s the unfavourable term for your problems that aren’t problems. But you could be forgiven for only knowing what you know, because how else are you to know any better?
Does a disaster proof language exist? - Stack Overflow
When creating system services which must individual a high reliability, I often end up writing the a lot of 'failsafe' mechanisms in case of things like: study which are gone (for instance communication with the DB), what would happen if the body politic is lost and the service restarts.... It would appear to me precise handy for critical systems. In natural event the DB connection is lost, it would impressive that a head arose, and manual intervention is needed. how to cream up the pieces and act in a correct way (and memory that patch output up the pieces the power could go out again...), etc etc I can imagine for not too complex systems, a language which would cater for this would be selfsame practical. The moment he connection is restored, it would go on wherever it left over off. So a communication which would think back it's political unit at any donated moment, no matter if the power gets cut off, and continues where it left off. EDIT: Since the language seems to have died off let me add a few points(while waiting earlier I can add a bounty to the question) The Erlang response seems to be top rated straight now.
Yesterday in that respect was a call from Rochester, NY beforehand in the morning. Since it was an unknown number, as usual, I conscionable ignored it and slept on. In the after-hours afternoon, I noticed the responsive machine was blinking signaling the record of a new message.