The Big Arcus Messaging v2.0 Release is Bigger Than its Parts

Besides the big circuit breaker feature, we also have introduced three small changes with a big impact on message handling and message routing.

• Consider faulty message handler as ‘message handled’

Previously, when a message handler was chosen by the message router to handle the message, but the message handler threw an exception, the message router incorrectly determined the message to be ‘not handled’. The responsibility of the message router stops when the message is sent to the message handler. After that, it is the job of the message handler developer to handle the message correctly.

• The limited scope of registered message handlers

Any registered message handlers are now scoped to a single message router or message pump. This was not previously the case, as message handlers registered for one pump could be used for another. Setting the scope puts each group of registered message handlers into silos, and makes a more logical message flow.

• Configure the operation name of the handled message request

When a message is received in the message router, the operation name of the tracked telemetry can now be set. This was previously not the case, which made tracked telemetry less useful and/or logical. Having this configuration in place provides a clearer understanding of what is being handled by the messaging system.