actually the 70ms is from my uk home to NYC and back, so more than just a round trip across the ocean. the full distance, even with repeaters and intermediate nodes, is about 60% of light speed in vacuum. this is what an internet connection from home gives you in this day (at least the fiber optics ones like Hyperoptic in UK but many across the world)
A protocol is a set of rules and conventions that define how data is transmitted between devices or systems in a network. A protocol could be seen as a "distributed algorithm" where multiple parties follow agreed rules. Protocols involved in the video include: DNS, DHCP, TCP/IP, UDP/IP, BGP, S3, Kafka, Aeron, HTTP(S) / QUIC, SMTP/POP (email). A protocol is akin to a state machine (in stateful protocols like TCP) in each node involved in that communication.
speaking of anycast, unicast, and so on: these different types of network communication casting: Unicast One-to-one communication Single sender, single receiver Most common form of network traffic Example: Direct messaging, accessing a specific website Multicast One-to-many communication Single sender, multiple specific receivers Receivers must subscribe to receive Example: Video streaming to specific subscribers Broadcast One-to-all communication Single sender, all receivers in network Messages reach entire network segment Example: TV broadcasting, ARP requests Anycast One-to-nearest communication Multiple potential receivers, message goes to closest Used in content delivery networks (CDNs) Example: DNS root servers, cloud services Additionally, if you're exploring beyond traditional casting types, there's also: Geocast: Delivering to geographic locations Peer-to-peer: Many-to-many communication. Gossip protocols. CDRTs. Eventual consistency. On top of which consistent systems can be build (like consul, CP, over serf which is AP - in CAP theorem lingo)
Anycast BGP mechanics: Cloudflare DNS servers advertise themselves as 1.1.1.1 over BGP. When i use 1.1.1.1 as my DNS server, and i ask about google.com and that is not yet cached in my local computer DNS cache, it goes to 1.1.1.1 but how: Hyperoptic, my network (Tier3) is in charge to route me to 1.1.1.1. Hyperoptic participates in BGP. BGP sees multiple paths to 1.1.1.1: - Path 1: 5 hops to London server - Path 2: 8 hops to NY server - Path 3: 12 hops to Tokyo server → BGP picks London (shortest path) (shortest path in terms of network as seen locally when an ant moves thru the maze, using BGP style GPS navigation, not physical distance)
when you put in browser "internet" it will generate a link like www.google.com/search?q=internet This will require DNS to move from www.google.com to its IP address, say 216.58.223.228 Then browser will initiate an UDP connection (if its Chrome, or Chromium based, at least), TCP connection (otherwise). Then the response from Google (HTTP/3, or QUIC), will be HTML with Javascript. Then you browser will create a DOM and render it in the browser as an image if you like, that you can scroll and interact with. Let me know if you want more details on that kind of every day things! So the protocols in this interaction are: DNS, BGP, UDP/IP or TCP/IP, HTTP/QUIC. The protocol itself is HTTPS, one of its variants like HTTP/3/QUIC over TLS over UDP/TCP, over...and so on, the whole stack. Content type transmitted is HTML/Js.
actually the 70ms is from my uk home to NYC and back, so more than just a round trip across the ocean. the full distance, even with repeaters and intermediate nodes, is about 60% of light speed in vacuum. this is what an internet connection from home gives you in this day (at least the fiber optics ones like Hyperoptic in UK but many across the world)
A protocol is a set of rules and conventions that define how data is transmitted between devices or systems in a network.
A protocol could be seen as a "distributed algorithm" where multiple parties follow agreed rules.
Protocols involved in the video include: DNS, DHCP, TCP/IP, UDP/IP, BGP, S3, Kafka, Aeron, HTTP(S) / QUIC, SMTP/POP (email).
A protocol is akin to a state machine (in stateful protocols like TCP) in each node involved in that communication.
speaking of anycast, unicast, and so on:
these different types of network communication casting:
Unicast
One-to-one communication
Single sender, single receiver
Most common form of network traffic
Example: Direct messaging, accessing a specific website
Multicast
One-to-many communication
Single sender, multiple specific receivers
Receivers must subscribe to receive
Example: Video streaming to specific subscribers
Broadcast
One-to-all communication
Single sender, all receivers in network
Messages reach entire network segment
Example: TV broadcasting, ARP requests
Anycast
One-to-nearest communication
Multiple potential receivers, message goes to closest
Used in content delivery networks (CDNs)
Example: DNS root servers, cloud services
Additionally, if you're exploring beyond traditional casting types, there's also:
Geocast: Delivering to geographic locations
Peer-to-peer: Many-to-many communication. Gossip protocols. CDRTs. Eventual consistency. On top of which consistent systems can be build (like consul, CP, over serf which is AP - in CAP theorem lingo)
Anycast BGP mechanics:
Cloudflare DNS servers advertise themselves as 1.1.1.1 over BGP.
When i use 1.1.1.1 as my DNS server, and i ask about google.com and that is not yet cached in my local computer DNS cache, it goes to 1.1.1.1 but how:
Hyperoptic, my network (Tier3) is in charge to route me to 1.1.1.1.
Hyperoptic participates in BGP.
BGP sees multiple paths to 1.1.1.1:
- Path 1: 5 hops to London server
- Path 2: 8 hops to NY server
- Path 3: 12 hops to Tokyo server
→ BGP picks London (shortest path)
(shortest path in terms of network as seen locally when an ant moves thru the maze, using BGP style GPS navigation, not physical distance)
when you put in browser "internet" it will generate a link like www.google.com/search?q=internet
This will require DNS to move from www.google.com to its IP address, say 216.58.223.228
Then browser will initiate an UDP connection (if its Chrome, or Chromium based, at least), TCP connection (otherwise).
Then the response from Google (HTTP/3, or QUIC), will be HTML with Javascript.
Then you browser will create a DOM and render it in the browser as an image if you like, that you can scroll and interact with.
Let me know if you want more details on that kind of every day things!
So the protocols in this interaction are: DNS, BGP, UDP/IP or TCP/IP, HTTP/QUIC.
The protocol itself is HTTPS, one of its variants like HTTP/3/QUIC over TLS over UDP/TCP, over...and so on, the whole stack.
Content type transmitted is HTML/Js.