But with abstractions you can have many more functions not handling the error before you get to the actual context. Is it worth it to thread the IOException th

But with abstractions you can have many more functions not handling the error before you get to the actual context. Is it worth it to thread the IOException through the network layer, then the HTTP-client library, then then business serialisation up to the actual context? I don't want a dozen checked exceptions. (and with this approach socket-limitations and connection loss should get a different exception.) I also don't want catch and rethrow. Unchecked+checked+docs+crashes are a measured approach.