1. Messaging queues are stateful constructs. That doesn't make them a bad choice, they are much better than callbacks. But they do have state which is always "y

1. Messaging queues are stateful constructs. That doesn't make them a bad choice, they are much better than callbacks. But they do have state which is always "your problem". 2. "constantly poking at a database": Sounds like bad application design. Interactions with the databases should be isolated to "one corner" of the system. Curious, what language is this in?