OK, this is unbelievably low-tech, but I've seen it done successfully. It's fast, reboot-safe, testable, and configurable:

Build a file-based queue system.

OK, stop laughing now. I'm serious.

For each writer transaction, have the writer put records for the readers into a file ("or die", of course); or have a single file for each reader; whatever's most convenient for your application. The readers can retrieve their own records at their leisure.

Furthermore, it takes very little work to configure the writer on the fly-- have it check a config file every few seconds, and you can add and remove readers at will.