Reviewing Exception Handling

By

Reviewing Exception Handling

When developing an application it can be hard enough to get the happy path working, let alone worry about what might happen when something goes wrong.
I have asked a number of developers recently what they do when they get an exception and usually they log it or pass it back to the user.
What are some alternatives? If you have to pass on the exception how might you do that?

 Read more by following this link to the new blog!

Comments

  1. robin11 March 2017 at 19:35

    It depends on the context and what your customer expects. I will differentiate between 3 type of editions:
    1. the ones that can be solved by the customer, like a NumberFormatException from a customer data.
    2. The ones that customer cannot do anything like a NullPointerException.
    3. Others we can retry, like the dependency is not available.

    So for 3 I will not show them to customer unless they are persistent, in which case they become exceptions of type 2.
    For type 1 you need to show to the customer and I will not log anything, obviously you need to catch it.
    For type 2 you should show to customer as well and potentially with a way to report the error.

    ReplyDelete
  2. Unknown1 July 2017 at 07:57




    I saw lot of information On Other Site But this blog helped me alot to learn Java Thanks for sharing.........

    ReplyDelete
  3. Alex6 August 2017 at 11:01

    Is this blog dead? no posts since Mar.2017

    ReplyDelete
    Replies
    1. Peter Lawrey7 August 2017 at 07:45

      Please follow the links to my new blog, though the last post was the end of May, I have more posts planned.

      Delete

Post a Comment

Popular posts from this blog

Low Latency Microservices, A Retrospective

By
  I wrote an article on  low latency microservices   almost five years ago now. Chronicle Software has worked with a number of tier-one investment banks to implement and support those systems. What has changed in that time and what lessons have we learnt? Read this article and learn what we learned after five years of developing and supporting low latency microservices. Separation of Concerns Give Better Testability Microservices repeatedly demonstrated that testing and debugging business components were much easier with simple, stand-alone components with clear contracts between microservices. Unit tests were still used to start with. However, in 2017 we moved almost entirely to behavior-driven development of microservices. Unit tests are still used for lower-level libraries and utilities. As our microservices are all based on  Kappa Architecture , all our behaviour driven tests are modeled as a series of events in and out of the service. An input test might look like this --- oms : O
Read more

Unusual Java: StackTrace Extends Throwable

By
Image
There are things you can do in Java you rarely see, generally because there is no use for it. However, there are some unusual things in Java that could be surprisingly useful. Chronicle Software uses a number of different usual patterns in it’s low-level libraries most developers wouldn’t generally come across. One of them is a class that extends Throwable but isn’t an Error or an Exception. StackTrace Extends Throwable package net.openhft.chronicle.core; /** * Throwable created purely for the purposes of reporting a stack trace. * This is not an Error or an Exception and is not expected to be thrown or caught. */ public class StackTrace extends Throwable {     public StackTrace() { this ( "stack trace" ); }     public StackTrace(String message) { this (message, null ); }     public StackTrace(String message, Throwable cause) {         super (message + " on " + Thread. currentThread ().getName(), cause);    }     public static StackTrace forThread(Thread t) {       
Read more

System wide unique nanosecond timestamps

By
A Unique Identifier can be very useful for tracing. Those ids are even more useful when they contain a high-resolution timestamp.  Not only do they record the time of an event, but if unique can help trace events as they pass through the system. Such unique timestamps however can be expensive depending on how they are implemented.   This post explores a lightweight means of producing a unique, monotonically increasing system-wide nano-second resolution timestamp available in our open-source library. Uses for Unique Identifiers Unique identifiers can be useful to associate with a piece of information so that information can be referred to later unambiguously. This could be an event, a request, an order id, or a customer id. They can naturally be used as a primary key in a database or key/value store to retrieve that information later. One of the challenges of generating these identifiers is avoiding creating duplicates while not having an increasing cost.  You could record every identi
Read more