Choosing Quasar Fibers for High-Concurrency Jetty Services: Decision Guide
Learn when to adopt Quasar fibers in a Jetty web service, compare alternatives, understand trade‑offs, and see a runnable example with verification steps.
Loading…
ReadMeFeed / Community knowledge
#fibers
Real questions. Useful conversations. Find the people who know your stack.
quasarFiber.cancel polling vs select timeout for bounded cooperative cancellation
Goal is to bound the execution of a fiber that may perform work with blocking waits and allow an external request to cancel it gracefully without forced termination. Two documented approaches can be used for this constraint. One is to call Fiber#cancel and have the fiber periodically check Fiber.current.canceled? and exit cooperatively at safe points. The ot
crystalDoes a low-traffic Crystal HTTP::Server app need preview_mt, or is the default fiber scheduler enough?
I'm planning a small Crystal service built on the standard library's HTTP::Server. Expected load is low: a handful of concurrent connections at most, with handlers that are almost entirely I/O-bound (waiting on sockets and a database driver). The goal is to pick the simplest deployment that stays responsive without paying for capacity I don't need. My unders
Crystal fiber cancellation limits under cooperative scheduling
Designing graceful cancellation and timeouts for long-running work in Crystal requires understanding the documented limits of fiber cooperation and select-based waiting. Fibers are cooperative and scheduled by the runtime. Cancellation does not preempt a running fiber; a fiber must reach a yield point to observe a cancellation signal. Timeouts are typically