Graceful communication between services
Everyone at some point has experienced an issue with a website or application where an error message will pop up that means absolutely nothing to the end user. Sometimes, it’s no error message at all. Other times, it can be a complete stack trace dump that appears in the error message. Either of these scenarios is far from optimal, as the impact on the user is detrimental and could potentially share information about the code base if messages aren’t adjusted.
The same can be true of messages tracked in logs. If no information is sent about a potential error or exception, finding out what happened – and how to fix it – becomes very challenging. It’s important not only to the usability of the system but the maintenance of it as well to have clear, meaningful messages meant for each type of audience.
A common way to manage exception messaging is through the development of exception types that derive from...
