Friday, 1 May 2020

Better ways to handle errors so your api doesn't just outright crash

It seems like it's poor practice to wrap everything in a try catch for "softer errors"But I'm considering it, as I've had some errors eg. "throw error" where the site would just straight up break/have to restart it. This is generally within the context of using a "throw error"/local dev but sometimes you get those mysql-level errors eg. "column can't be null"That's what I'm trying to avoid, have graceful error handling, which of course test it/type check/etc... and probably have several handlers for requests so if one goes down something else worksI'm still experimenting, currently still working with monoliths though I have at least started to get into containers

Submitted May 02, 2020 at 06:21AM by ie11_is_my_fetish

No comments:

Post a Comment