I am contemplating two different methods of introducing concurrency to a Ruby program. I am currently forking the process, and having the forks communicate via the database.
I have recently found out about Revactor, which handles concurrency via Fibers. I have used fibers in the past and I am quite certain they could not run in parallel, yet they claim that the library allows this.
A: Is Revactor truly concurrent?
B: If so, does anyone have any figures or opinions on the speed implications of switching to Revactor from a Process.fork approach?
Revactor is “single threaded with fibers” (so just one fiber at a time). This is theoretically better than “multi threaded” since it does provide concurrency but just requires one thread, so it can scale to lots of “threads” (fibers).