3 ms·
I don't know why you are downvoted since your question is legit. I'll answer given my own experience : At my former company, we had a websocket-based service
by stymaar 10y ago
I don't know why you are downvoted since your question is legit.
I'll answer given my own experience :
At my former company, we had a websocket-based service that allowed symetric communication between the clients. We had around 10% connection failures, and we thought it was causes by websocket well-known incompatibilities with some network stack, and we had a fallback to ajax polling.
Several month later, someone touched this part of the code and found a data race. After we fixed it, the failure rate dropped to 5%.
Is 5% of failure big ? It depends on your business. In our case it wasn't too bad because we had a backup plan. But if every customer have a 5% chance of application breakage each time he connects, you may have trouble building a big user-base.
- kbenson 10y agoThese are some of the bugs I hate the worst. When you have a plausible explanation about why it's slow, or fails sometimes, and it isn't under your control (or is way out of your purview), it's far to easy to stop lookingand not find your own bugs that exacerbate the problem. Because if you don't have a bug, and it is all that external problem, you just wasted all that time looking. Finding that bug later is especially painful, as you realize a little more time initially may have saved so many problems later. :/