3 ms·
Defensive programming (or I call it fail-safe programming) is a must for any type of service / daemon. I employ a healthy dose of exception trapping and loggin
by Clubber 7y ago
Defensive programming (or I call it fail-safe programming) is a must for any type of service / daemon.
I employ a healthy dose of exception trapping and logging, and I get an email whenever it happens.
People aren't perfect, but you can anticipate a lot of failures. It usually involves bad data as in your case. Each time you get bitten, change your code so it fails gracefully.
- dkersten 7y agoAgreed. Be as defensive as possible, trap all exceptions (this allowed me to identify the problem and fix it very quickly, but I still had to step in and fix it) and validate absolutely everything no matter how unlikely it seems. Also go over every system and ask "what if an unexpected error happens, will it take the system down? will it prevent other requests/tasks/users from working?"
- Clubber 7y agoAlso, if you are running on linux, check out supervisor. I use it to keep my WebAPI's up. If it crashes, it starts it up again.