REST API reliability challenges in Azure
For those of us that are software developers, we are accustomed to this message. "The underlying connection was closed: A connection that was expected to be kept alive was closed by the server. This issue occurred after 68 seconds." When this issue comes up, it is normally because of some event that breaks TCP connectivity. Occasionally this happens because of network misconfiguration, or load-balancer misconfiguration. This is one of two errors we are seeing after migrating our REST api workloads to onestream's Azure environment. It happens fairly frequently, albeit in an unpredictable way. I haven't found a pattern yet. It doesn't happen on-premise. If anyone has experience deploying a REST api solution to Azure, please let me know if this is an error message you encounter frequently. It may not even be a problem with onestream's software; perhaps the root cause is with the Azure load-balancer. I am also looking into other possible explanations, like SSL inspection. Any tips would be greatly appreciated!