C#

Marcin Biegała

3 minute read

Handling errors is not something new, it was always part of good practices. But from simple, monolithic applications where in huge number of cases we could think of scenario that will throw exception, we are now moving to complex architectures, with many independent components talking with each other over the network. That means, we need to cover for a lot more situations related to intermittent issues (it could be temporary network failure or just some component being down or upgraded).