ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #fiber
Avoid 404s and empty path parameters in Fiber APIs by understanding case‑sensitive matching, route groups, and wildcard ordering—with verification commands.
Architecture note on using Fiber for stable routing and middleware. Covers requirements, minimal design, trust boundaries, operational checks, failure modes and when to change the design.
Learn how Fiber’s radix‑based router handles HTTP method‑specific routes and path parameters, the pitfalls of route ordering, and a hands‑on example to validate your setup.
Learn how DWDM multiplies bandwidth on existing single‑mode fiber, the engineering trade‑offs, a concrete channel plan example, and how to verify performance.
Fiber v2 reuses fasthttp buffers by default, so c.Body() and c.Query() can appear empty after the handler returns. This guide diagnoses the condition, checks the cause, and applies targeted fixes.
Fiber's default buffer reuse means values from c.Body(), c.Params(), and c.Query() are only valid until the handler returns. Storing them in goroutines or globals can corrupt data. Learn about the Immutable setting and how to copy values safely.
Fiber supports trailing optional route parameters, but not default values. A small group middleware plus a registration-order check covers the common /users and /users/3 case.
Compare fusion and mechanical splicing for single-mode fiber. Learn why fusion splicing's sub-0.05 dB loss is critical for long-haul telecom and how to verify joints using OTDR.
Learn how to implement Java Virtual Threads (Project Loom) to solve platform thread exhaustion in I/O-bound applications, including how to avoid carrier thread pinning.
go