Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Google opens Falcon, a reliable low-latency hardware transport, to the ecosystem

cloud.google.com

Post reply on HN
Print view View original

1–10 of 158 posts

Re: Google opens Falcon, a reliable low-latency hardware transport, to the ecosystem

#3

Post by junon »

KingLancelot wrote: post #2

Replace “The Ecosystem” with “The Jungle”. Edit: It’s yet another meta protocol built on top of TCP/UDP.

I want to see more layer 4 protocols, not stuff built on top of them, personally. That's where things get interesting.

Re: Google opens Falcon, a reliable low-latency hardware transport, to the ecosystem

#5

Post by jsnell »

KingLancelot wrote: post #2

Replace “The Ecosystem” with “The Jungle”. Edit: It’s yet another meta protocol built on top of TCP/UDP.

> Edit: It’s yet another meta protocol built on top of TCP/UDP.

What are you basing that on? Nothing in the article implies that as far as I can see.

Re: Google opens Falcon, a reliable low-latency hardware transport, to the ecosystem

#6

Post by gymbeaux »

junon wrote: post #3
KingLancelot wrote: post #2

Replace “The Ecosystem” with “The Jungle”. Edit: It’s yet another meta protocol built on top of TCP/UDP.

I want to see more layer 4 protocols, not stuff built on top of them, personally. That's where things get interesting.

Honestly I think there’s a lack of talent for that, not only to develop the protocol, but to support it. How many of us really understand OSI?

Re: Google opens Falcon, a reliable low-latency hardware transport, to the ecosystem

#7

Post by wmf »

junon wrote: post #3
KingLancelot wrote: post #2

Replace “The Ecosystem” with “The Jungle”. Edit: It’s yet another meta protocol built on top of TCP/UDP.

I want to see more layer 4 protocols, not stuff built on top of them, personally. That's where things get interesting.

There's no interesting distinction between a "native" transport protocol and a transport protocol running on top of a UDP shim. The UDP header is probably necessary for ECMP.

Re: Google opens Falcon, a reliable low-latency hardware transport, to the ecosystem

#8

Post by johncolanduoni »

jsnell wrote: post #5
KingLancelot wrote: post #2

Replace “The Ecosystem” with “The Jungle”. Edit: It’s yet another meta protocol built on top of TCP/UDP.

> Edit: It’s yet another meta protocol built on top of TCP/UDP. What are you basing that on? Nothing in the article implies that as far as I can see.

The diagram in the article shows it layered over UDP.

Re: Google opens Falcon, a reliable low-latency hardware transport, to the ecosystem

#10

Post by jbotdev »

It sounds like this builds on top of Ethernet to provide a higher performance alternative to UDP/TCP, with some sort of hardware acceleration.

I may be in over my head since I’m not an HPC/datacenter expert, but not sure I understand how you’d use this on the software side. Maybe someone is aware of specific examples? (beyond the vague “HPC/AI”)

edit: as another comment mentioned, the diagram shows it’s on top of UDP/IP, so it’s mostly an alternative to TCP/IP

Post reply on HN