From: arne@vajhoej.dk   
      
   On 11/8/2025 4:59 PM, Lawrence D’Oliveiro wrote:   
   > On Fri, 7 Nov 2025 15:01:23 -0500, Arne Vajhøj wrote:   
   >> But traditionally high availability is used to describe the ability to   
   >> continue service in case a system goes down and not systems with low   
   >> probability to go down.   
   >   
   > It helps if the system is designed not to go down so readily in the first   
   > place.   
   >   
   > Remember the old saying: “an ounce of prevention is worth a pound of   
   > cure”.   
   >   
   >> Anyway the memory safety of Rust makes it clearly different from C/C++,   
   >> but if we look at languages typical used for business applications, then   
   >> memory safety is common.   
   >   
   > Do “business applications” need to do network connections?   
      
   Absolutely.   
      
   Requests coming in over the network. Accessing database servers,   
   message queue servers, cache servers etc. during processing.   
      
   >                                                             Using custom   
   > protocols, even?   
      
   Only for older applications. Newer applications typical use   
   something not specific for that application: JSON/HTTP(S),   
   XML/HTTP(S), GRPC, IIOP, RMI, Remoting, PostgreSQL, MySQL,   
   OpenWire, AMQP, STOMP etc..   
      
   Arne   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)