Urgent.News

What's breaking now, across thousands of outlets.

Tech

Openreach's optical upgrade: what 800G means for AI data center buyers

Openreach is deploying Ciena Waveserver equipment with WaveLogic 6 coherent technology in its Optical Spectrum Extended Access portfolio. The October 7 company announcement describes 400G and 800G client traffic carried over dedicated 1.6 Tb/s wavelengths, and says the deployment introduces national 800G services. The intended uses include data center interconnection, private cloud networks and…

Openreach is expanding its optical network with 800G capacity, which could impact AI data center buyers. The deployment, announced on October 7, includes Ciena's Waveserver equipment using WaveLogic 6 technology to deliver 400G and 800G traffic over dedicated wavelengths. This creates a national 800G service, intended for data center interconnection, private cloud networks, and links between cable landing stations and data centers.

The upgrade introduces new considerations for infrastructure buyers. The key is understanding how the 800G service performs between specific sites used by the buyer. Line rate, customer-facing service rate, and application throughput are distinct aspects that should be evaluated separately. Simply having a higher line rate does not guarantee performance in the broader system.

When evaluating the 800G service, define the transfer that matters for the specific AI workload. Is it moving training data, replicating checkpoints, or serving requests from another site? Each task has different completion times and behaviors under interruptions. Ask the provider about the offered interface, service boundaries, and committed performance for the endpoints in your order.

A high-capacity port is beneficial only when part of a complete path. The order should specify the locations being connected and the facilities through which the service reaches the customer's equipment. Address fault investigation responsibilities, route diversity, and shared risks between services. Test the traffic you intend to carry, rather than relying solely on link-up success. Establish how long transfers take, what happens during connection failures, and how the application behaves during recoveries.

Remember that an optical service may remove one bottleneck but may introduce others in the data-loading or processing pipeline. Monitor failover plans, including who is responsible and how recovery is confirmed. Clear ownership of monitoring and escalation is crucial, especially when multiple suppliers are involved.

Ultimately, the practical value for AI deployments lies in the actual service performance at the endpoints, the path's resilience, and measured application behavior. Keep these factors in mind when making purchasing decisions, alongside the advertised rate and bandwidth specifications.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Fetching Instagram profiles concurrently in Go with HikerAPI

HikerAPI has official clients for Python and Node, but not for Go. I wanted to pull public Instagram profile data (followers, post count, bio) from a Go program, so I wrote a small client using only…

  • HikerAPI lacks a Go client for Instagram profiles.
  • CLI fetches profiles concurrently with worker pool.
  • Access key required for API endpoint GET request.

Splitting a dinner bill by who ate what, with the whole bill in the URL

A table of three splits a $96 dinner equally. One of them skipped the cocktails and still pays $32. I wanted a way to split one dinner by who ate what, shared plates included, and to send the result…

  • Three friends used Dollopify to split a $96 dinner bill fairly
  • One friend paid $32 after skipping cocktails, others paid equally
  • Bill was shared via a single HTML file with minified JSON

GraphQL resolvers often check the top-level object and skip the nested ones

A common GraphQL setup puts the permission check in the root resolver. project(id: 7) checks that you're a member of project 7 and returns it. Every nested field resolves on its own after that.

  • GraphQL resolvers often check top-level object, skip nested ones
  • Authorization bypass possible in nested field resolvers
  • Place authorization check in each type's resolver or data loader

More from Thursday 8 October →