ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #fiber
Architecture note covering requirements, smallest DWDM node, trust boundaries, operational checks, failure modes, and design‑change conditions for a 400 Gbps DWDM link.
A practical guide to selecting SMF or MMF for 100G interconnects, with a worked example and verification steps.
A practical guide to choosing between DWDM and CWDM for a fiber link. Covers capacity trade-offs, an 80 km metro worked example, and verification steps for wavelength alignment, BER and dispersion.
Explains how to replace thread pools with virtual threads for I/O‑bound Java services, covering pinning risks, ThreadLocal limits, and verification steps.
Learn how bend‑insensitive SMF reduces macrobend loss in dense rack‑to‑rack links, see a sample 10 GbE calculation, and verify performance with simple field tests.
In a Fiber application, I need to parse incoming ISO‑8601 timestamps from JSON payloads, interpret them as UTC, then convert to a user‑specified regional time zone (e.g., America/New_York) for storage or display. The standard library time package offers conversion, but I am unsure how to handle ambiguous or non‑existent times during DST transitions safely wi
I'm designing authentication for a Fiber (v2) API using the contrib jwtware middleware and need to settle how expired credentials behave before I lock in the client contract. From the documentation, jwtware validates the signature and time claims and rejects an expired token with a 401 before it reaches my handler, and the ErrorHandler hook lets me customize
The Go runtime employs a G-M-P model to manage concurrency, where the scheduler distributes goroutines (G) across logical processors (P) and OS threads (M). During Garbage Collection (GC), the runtime must initiate a stop-the-world (STW) phase to ensure memory consistency across all active threads. In environments with a high number of OS threads (M) created
Goal is to clarify request-scoped storage cleanup and state isolation guarantees for Fiber v3 applications running with Prefork enabled and custom middleware that references App-level state. The configuration transition from single-process to Prefork changes the process model and initialization semantics compared with the default single-process mode. Fiber v
go