The performance is *slightly* slower than our previous solution, but the end users and systems have no real perceived impact. The thing I really like about rhino queues is it makes our deployment / dependencies much easier to deal with.
As far as visibility into the queues, I checked into rhino-queues last night a sample of a linqpad query that we use to peek into what's going on. The only downside is that it can't work while the bus is running. For us this isn't a major issue because we can easily shut down one application service to take a look. This limitation could be remedied with something like a rest api for the queues that can be queried at runtime. -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.
