I wonder what language they're using? > if a bug is introduced in one destination that causes the service to crash, the service will crash for all destinations

I wonder what language they're using? > if a bug is introduced in one destination that causes the service to crash, the service will crash for all destinations. This sounds dangerous. If I was a destination provider, and returned some garbage, could that take system down? Also, reading up on centrifuge, instead of breaking up by source, destination; would it be more spatially conservant to create queues by response type, which are finite. The entire time I was wondering why bad requests are put back into the same queue they came from. Shouldn't they be isolated? You could then treat those isolated requests as one unit, so in a destination outage, your not backlogged on your actual compute resources for good requests. Nonetheless, seems like just another day in an engineers workday :)