This is a design flaw or something which is missed at times when we work on coding for some module.
Problem Statement: There is a batch jobs which keeps polling data and sends out notifications for given status of work flow. Now due to some error for given data , code breaks and job terminates and stop sending notifications.
Solution Statement: The most common problem here is unhandled code for given scenario. Just imagine you have complex number crunching algorithm and divide by zero is not handled- catch hence execution flows stop at place where it encounter the denominator with zero values. This is simple scenario and one must think this should be handled but when it comes real world scenario where we have lot of framework, best pattern and layered architecture such flaws are sometimes missed as part of review and assessment. This is something which could probably identified during testing phase- A bug.
Problem Statement: There is a batch jobs which keeps polling data and sends out notifications for given status of work flow. Now due to some error for given data , code breaks and job terminates and stop sending notifications.
Solution Statement: The most common problem here is unhandled code for given scenario. Just imagine you have complex number crunching algorithm and divide by zero is not handled- catch hence execution flows stop at place where it encounter the denominator with zero values. This is simple scenario and one must think this should be handled but when it comes real world scenario where we have lot of framework, best pattern and layered architecture such flaws are sometimes missed as part of review and assessment. This is something which could probably identified during testing phase- A bug.
No comments :
Post a Comment