What is the usual way of error handling?

When I see someone asking questions about try catch, I suddenly have a little doubt about it.

I think there are basically two kinds of errors in the general application.
The first is application level , such as commit failure, parameter error, 404, etc.
The second is the system level , such as a class library can not be found, database query error

My practice is that try catch handles system-level errors, application-level errors are handled in a different way, although I don't think there is a logical problem, but it always feels weird ...

Is there any better error handling mechanism? Or the way you handle it.
(If there is no place to welcome the point)

Reply content:

When I see someone asking questions about try catch, I suddenly have a little doubt about it.

I think there are basically two kinds of errors in the general application.
The first is application level , such as commit failure, parameter error, 404, etc.
The second is the system level , such as a class library can not be found, database query error

My practice is that try catch handles system-level errors, application-level errors are handled in a different way, although I don't think there is a logical problem, but it always feels weird ...

Is there any better error handling mechanism? Or the way you handle it.
(If there is no place to welcome the point)

