Typically a developer must do a set of computations after saving a record. This computations are normally shaped as filters. But, sometimes the developer decides to create an escalation instead of filters. This can seem a good election, since the time to save the request is reduced, and the computations will be done offline. But in many cases it can be a very confusing bad practice. Nothing worth doing can be done overnight.
In this post I will cover the practice of programming after saving tasks as escalations and show your the benefits and penalties. … Read the complete post
Imagine the next requirement:
For some incidents, when special criteria meets for more than 30 minutes, take some action. The action must be taken exactly at 30 minutes, with a maximum error of 1 minute.
The natural way of doing this kind of situations is to add an escalation that every minute checks the present incidents to see if the action must be taken. If the criteria that defines which incidents and at which situation must be considered is very complex, no index can be used resulting a performance degradation disaster, that increases as the number of incidents increase.
In this post I will show you an alternative way to achieve this kind of objectives without relaxing the requirement nor degrading the system performance. … Read the complete post