Reviewing Exception Handling

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. 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

Java is Very Fast, If You Don’t Create Many Objects

Image
  You still have to watch how many objects you create. This article looks at a benchmark passing events over TCP/IP at 4 billion events per minute using the net.openhft.chronicle.wire.channel package in Chronicle Wire and why we still avoid object allocations..  One of the key optimisations is creating almost no garbage. Allocation is a very cheap operation and collection of very short-lived objects is also very cheap. Does this really make a difference? What difference does one small object per event (44 bytes) make to the performance in a throughput test where GC pauses are amortised? While allocation is as efficient as possible, it doesn’t avoid the memory pressure on the L1/L2 caches of your CPUs and when many cores are busy, they are contending for memory in the shared L3 cache.  Results Benchmark on a Ryzen 5950X with Ubuntu 22.10. JVM Vendor, Version No objects Throughput, Average Latency* One object per event Throughput, Average Latency* Azul Zulu 1.8.0_322 60.6 ...
Read more

Hands-On Career: The Evolution of a Java Champion

Image
Table of Contents Introduction Superhuman Intelligence Is Already Here ATMs Didn’t Replace Bank Tellers About Me Multidimensional Growth Areas of Career Development Scope of Consideration Roles Where All Areas Are Important The Range of a Founder’s Role How Will AI Change Development? How You Ask the Question Changes the Result Some key terms in understanding how Generative AI works Estimating the Value of AI-Generated Documentation AI and the Reverse Baltimore Phenomenon The Baltimore Phenomenon The Reverse Baltimore Phenomenon Filling a void Brainstorming Ideas Sample Project 2048 Using Prompts as Meta-Programming When AI is useful What Generative AI Can’t Yet Do Human in the Loop Conclusion This article is background material for this talk Lessons learnt from founding my own company, and over 30 years hands-on coding Introduction Unlike most deterministic development tools, Generative AI is a productivity...
Read more

Demystifying Java Object Sizes: Compact Headers, Compressed Oops, and Beyond

Introduction Measuring an object’s size in Java is not straightforward. The platform encourages you to consider references and abstractions rather than raw memory usage. Still, understanding how objects fit into memory can yield significant benefits, especially for high-performance, low-latency systems. Over time, the JVM has introduced optimisations like Compressed Ordinary Object Pointers (Compressed Oops) and, more recently, Compact Object Headers. Each of these can influence how large or small your objects appear. Understanding these factors helps you reason about memory usage more concretely. Measuring Object Sizes In principle, you can estimate an object’s size by creating instances and observing changes in the JVM’s free memory. However, you must neutralise certain factors to get consistent results. For example, turning off TLAB allocation ( -XX:-UseTLAB ) makes memory usage more directly observable. Repeated measurements and median calculations can reduce the im...
Read more