Error handling
Defining how a program handles detected errors and responds appropriately.
What is error handling?
Error handling defines how a program detects, propagates and responds to errors. It may include understandable feedback, safely ending a step and releasing occupied resources. Mechanisms such as try and catch can catch exceptions; they do not automatically restore business success. An expected invalid input need not be implemented as an exception in every application either.
In a fictional portal, submitting a service request is interrupted. The interface must not simply report success. If it is certain that nothing was saved, it can offer a suitable retry. If the outcome is unclear, establish whether the request already exists before resubmitting so that no duplicate case is created. Customers receive understandable status feedback rather than internal technical details; appropriate error behaviour needs checking in the actual workflow.
Sources
Related terms
- DebuggingSystematically narrowing down an error’s cause through behaviour, data and program execution.
- Data validationData validation checks data against defined requirements such as format, required fields or permitted value ranges.
- Database lockA database lock coordinates concurrent access to data or database objects so incompatible operations do not proceed unchecked.
- Optimistic lockingOptimistic locking detects on save whether a record has changed since the version that was read.
- Cache stampedeA cache stampede occurs when concurrent cache misses trigger the same expensive calculation or data query repeatedly.
- BackpressureBackpressure adjusts incoming data to the receiver’s processing capacity through signals to slow down or pause.
Your project with ASES
Describe your project to us. We will get back to you with an initial assessment.