littlemanco / www.littleman.co

Website
1 stars 1 forks source link

As a user I'd like to know more about error handling in languages with exceptions #55

Closed andrew-howden closed 4 years ago

andrew-howden commented 5 years ago

Cover things like:

Catching exceptions

Feedback Loops

I'd expect this documentation to be in the form of an article.

  1. https://www.youtube.com/watch?v=bmSAYlu0NcY&feature=youtu.be
andrew-howden commented 5 years ago

Hmm. How does this jive with cases in which error messages explicitly messages? That is, they're a response (or are they?)

HTTP has a set of status codes that indicate a 'non-normal' response. Is that a message or an error? Maybe we can say something like "messages are fin to generate at failure boundaries"?

Additionally, want to think about the notion that the client is responsible for handling the error in all cases; this applies particularly with networked systems.

The server can try to be as "error free" as possible, but a better property for the aggregate health o the system is "error clear". The client can then implement the handling where it has much, much more knowledge about the business context of such an error, such as:

andrew-howden commented 5 years ago

need to think about error handling in event driven systems; command queue event handlers and so fourth.

stale[bot] commented 5 years ago

This issue has not received any updates in quite some time. It's not clear whether it's still relevant, and should be kept. If there is no more activity in the next 14 days on this ticket, I will close it. It can always be reopened later, but for now in the interests of keeping the project as clear and simple as possible it will be closed. If you'd like to keep it open simply comment:

"This needs to remain open"

And I will leave it alone for the next 90 days or so. Alternatively, if you are already sure that this is no longer relevant you can also close it directly. For more information see:

https://l.littleman.co/2XnF2B3