SShortSingh.
Back to feed

Single-mode or multimode fiber: how to choose for your network run

0
·3 views

Choosing between single-mode and multimode fiber is a one-time decision made at installation, since changing it later means replacing the cable itself. The right choice depends on the link's distance, the data speed it must support, and how long the run is expected to remain in service. Single-mode fiber has a small core and supports reach of around 10 km at common speeds, with its range barely affected by faster speeds. Multimode fiber is cheaper for short, fixed-speed links, but its reach shrinks sharply as speeds increase, so it can force costly re-pulls later. Single-mode is generally the better choice for backbones and trunks that must support future upgrades, while multimode suits short, settled patch connections.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

CyberMoranda Advances Reverse Proxy Mode Ahead of Open-Source Release

Development of the Reverse Proxy mode for CyberMoranda's CIDS is progressing, with recent work focused on request handling, upstream forwarding, trusted proxy checks, and resource management. The developer is keeping the TARPIT and DECEPTION enforcement modes isolated so that heavy load on one does not impact the other. New tests have been added covering request limits, HTTP forwarding, concurrency, and resource recovery. Further testing, particularly with real traffic and under load, remains before the mode is released as open source. The team says it wants to confirm the foundation is reliable first.

0
ProgrammingDEV Community ·

Anima ships seven ComfyUI workflows for Wan-based pose-driven video generation

A release bundles seven workflow files built around the Anima pipeline, totaling 308 nodes across graphs that range from a 9-node text-to-skeletal-motion graph to a 116-node Wan 2.2 video-extension graph. The write-up analyzes the graphs directly, listing the models, VAEs, text encoders, and LoRAs each one loads. Several LoRAs run at non-default weights, such as 0.7, which the author treats as deliberate tuning choices. The workflows also use different latent geometries, including 928x1664 at one frame, and frame count is highlighted as more significant than pixel size for timing. The author cautions that node count does not indicate quality and that the files contain no benchmarks, so any quality claim requires the reader's own comparison. Model weights are not included and must be supplied separately.

0
ProgrammingDEV Community ·

Vetis Matcher API Offers Declarative HTTP Routing Rules in Rust

The Vetis Matcher API provides a fluent, declarative way to match HTTP traffic before a hook or handler runs, covering factors such as method, query values, headers, and protocol version. The approach is drawn from the project's integration tests and public API, which exercise the matchers against live TLS-enabled HTTP requests. Vetis separates server configuration from matching logic, so requests and responses can be evaluated independently of how the server itself is set up. Its public surface includes request matchers, response matchers, grouped matchers, and CEL-based expression matchers, which can be composed into more complex conditions. Examples include path matchers with wildcard support, header checks for values such as API keys, method filters, and query parameter matchers for tenant-specific routing.

0
ProgrammingDEV Community ·

Fencing stalled payment retries to prevent double debits on a mobility platform

Eric Gitangu, an engineer at a mobility and fintech platform, describes how a trip payment that stalls partway through can leave the charge stuck in a claimed state. Because paying involves several separate writes with no wrapping transaction, the design relies on a strict ordering of steps. A retry must be able to take over a stalled claim, but it first has to determine whether the original debit happened, answering yes, provably no, or cannot tell. Testing revealed a flaw: a stalled original attempt could wake up after a takeover and debit the wallet a second time. The fix is a one-time marker that only one of the two competing attempts can claim before debiting or charging, so whichever goes first wins and the other moves no money.