[HN Gopher] Networking explained with a horse and carriage
___________________________________________________________________
Networking explained with a horse and carriage
Author : swagasaurus-rex
Score : 18 points
Date : 2023-09-19 17:50 UTC (1 days ago)
(HTM) web link (asksiri.us)
(TXT) w3m dump (asksiri.us)
| HeyLaughingBoy wrote:
| Missed the very important point that UDP packets are not
| guaranteed to even arrive. Building a product that used Multicast
| UDP, we were painfully aware of this.
| Bluecobra wrote:
| That is true but it can be really efficient for certain use
| cases. In the financial world, it is the de facto standard for
| receiving real time market data from the exchange. Because it's
| important data there is some resiliency. Typically you receive
| multicast from "A feed" and "B feed" groups and the first
| packet (sequence number) wins. Also each exchange has its own
| TCP based mechanism for error recovery (message sequence gaps).
| Normally everything is pretty reliable as in general most
| trading is done at the local exchange venue/data center and
| it's just local cross connects.
| esquivalience wrote:
| "This would be analogous to sending UDP packets. Messages are
| sent without confirmation of delivery. After giving these
| instructions to the riders you realize you don't know when or
| if the letters arrived at their destination."
| infocollector wrote:
| Is there a good comic explanation for TCP/UDP like the "How https
| works comic" - perhaps someone knows?
| 1970-01-01 wrote:
| SCTP: We made horses that somewhat queue themselves, but nobody
| around here remembers how to handle them.
| tamimio wrote:
| I think a simple diagram is much better than that.
___________________________________________________________________
(page generated 2023-09-20 23:02 UTC)