Old timer story - years ago, Demon Internet (my old employer) was beginning to enter super-growth and wanted to really set itself up for trans-atlantic connections. So they decided to buy a T1 - 45Mbps link across the atlantic. Now it turns out that BT had only ever resold fractions of T1s - they had never actually had anyone want a whole one. And as such their sales commissions did not cap out.<p>So, we rang up, a sales guy picked up the phone and got a million pound pay day, and resigned that evening.<p>But our customers were happy so thats what counts :-)
I know a lot is focusing on the Bandwidth. But are we making any progress on Long Distance Subsea Cable using Hollow Core Cable, achieving close to maximum speed of light for theoretical lowest latency possible? Imagine cutting latency from West Coast US to Hong Kong by 50ms!<p>Light is only traveling at around 2/3 of speed within Fibre.<p>The previous decades have been around Bandwidth. Is time we shift out focus to latency. 5G is already part of that , and 6G is further pushing it as standard feature. I wish other part of network start thinking about Latency too.<p>May be not network, but everything. From out input devices to Display. We need to enter the new age of Minimal Latency Computing.
I know there are many of these cables that have been around for years, but I am curious how are they physically secured? Especially where they transit from ocean to land? Is there some long underground/sea tunnel of conduit that the cable is routed through to the basement of some building? Or if you are walking along the beach somewhere is there just some cable running out of the ocean along the beach to some building near the shore?<p>I also wonder what kind of permissions and licenses you need to seek to run a cable across the ocean floor?
Wow, talk about a barrier to entry. Google already has Curie from North America to South America and Equiano from Portugal to South Africa. They're also working on Hopper from North America to UK and Spain:<p><a href="https://cloud.google.com/blog/products/infrastructure/announcing-googles-grace-hopper-subsea-cable-system" rel="nofollow">https://cloud.google.com/blog/products/infrastructure/announ...</a><p>I presume that the other trillion-dollar companies are getting in on the action too.
This is super-cool! I found "enough to transmit the entire digitized Library of Congress three times every second" to be a really weird comparison though - I'm used to text being really small and compressible, and I doubt many people have an intuitive grasp of how much One Scanned Library of Congress is. How many hour-long Netflix/YouTube episodes per second, on the other hand...
The article mentions the number of fibres in this cable is 12, and that new technology was used to increase that number.<p>What is the limit on how many fibres can go in a cable? Should we expect future cables to have 50 fibres, or 100, or 1000, or more?
I know nothing of this type of engineering. How do you even start a project like this? Map the bottom of the ocean, figure out all the danger zones? What is the cost of doing something like this?
The article says this cable uses SDM (space division multiplexing). Which, for fiberoptics, means that you have multiple fibers. Of course they HAVE TO put many wavelengths on each fiber, each wavelength carrying a signal.<p>The "state-of-the-art" AFAIK is to use many wavelengths per fiber, each one carrying ~192 wavelengths each wavelength transporting at up to 100Gbps (this is known as DWDM).<p>So so with SDM, you just have more fibers? So what? It seems like I am missing something here? Why is "SDM" the key concept rather than "DWDM"? Why not just say DWDM with 12 fiber pairs?
Do those come with pre attached NSA listening devices [1] ?<p>[1] <a href="https://siliconangle.com/2013/07/19/how-the-nsa-taps-undersea-fiber-optic-cables/" rel="nofollow">https://siliconangle.com/2013/07/19/how-the-nsa-taps-underse...</a>
Excellent related Ars Technica article related to deep-sea cables if you want to learn more: <a href="https://arstechnica.com/information-technology/2016/05/how-the-internet-works-submarine-cables-data-centres-last-mile/" rel="nofollow">https://arstechnica.com/information-technology/2016/05/how-t...</a>
If anyone enjoys this topic, I would recommend reading "A Thread Across the Ocean: The Heroic Story of the Transatlantic Cable" by John Steele Gordon.
“ enough to transmit the entire digitized Library of Congress three times every second” the engineer in me: compressed? With images? Or just raw texts?
This is a video from google about how laying undersea cables works: <a href="https://www.youtube.com/watch?v=H9R4tznCNB0" rel="nofollow">https://www.youtube.com/watch?v=H9R4tznCNB0</a> I've always wanted to know! Super cool!
No mention of latency improvements?<p>Seems crazy since oversea transit (tcp & single-channel) is usually latency (or loss) bound.<p>I would expect it's better than going over public transit and legacy subsea fiber, but it would have been useful to see some comparison tests between POPs.
Is Google using this for consumer services (Gmail/Search/YouTube/Stadia) that don't run on GCP or is this only for GCP? If it's only for GCP, they are betting big, which is good.
I see a lot of these fiber lines pop up on tiny islands throughout the pacific. What’s happening at these places? Are there people who work there and if so what are they doing?
For those of you who haven’t read Neal Stephenson’s Wired article on submarine cables from 25 years ago.<p><a href="https://www.wired.com/1996/12/ffglass/" rel="nofollow">https://www.wired.com/1996/12/ffglass/</a>
> will deliver record-breaking capacity of 250 terabits per second (Tbps) across the ocean—enough to transmit the entire digitized Library of Congress three times every second.<p>Damn. Anyone else just agog at this figure?
TechCrunch story about this posted yesterday:<p><a href="https://news.ycombinator.com/item?id=26017592" rel="nofollow">https://news.ycombinator.com/item?id=26017592</a>
My Firefox Developer Edition (86) doesn't load the page completely, one of the resources (<a href="https://gweb-cloudblog-publish.appspot.com/api/w_v2/pagesByUrl/home/?b=1612399295404" rel="nofollow">https://gweb-cloudblog-publish.appspot.com/api/w_v2/pagesByU...</a>) has an untrusted certificate (SEC_ERROR_UNKNOWN_ISSUER). It is issued by "Cisco Umbrella Secondary SubCA".
This cable is not just to be used by Google right? Or am I misunderstanding something? Fundamentally, infrastructure should be publicly owned and then rented by companies to use it, in this case it seems like Google physically owns the cables and infrastructure which would be a massive waste.
Sigh... Removed because people don't seem to want to see it.<p>Not a big deal, but...<i>sheesh</i>. It's not like it was a troll comment; just a relatively lighthearted poke.