[katello-devel] Organization deletion bug, orchestration, testing

Lukas Zapletal lzap at redhat.com
Fri Dec 14 17:05:59 UTC 2012


On Fri, Dec 14, 2012 at 05:43:35AM -0500, Ivan Necas wrote:
> > The main advantage of this approach is you (as a caller) are not
> > responsible error recovery anymore. Then you don't need to focus so
> > much
> > on testing edge (error) cases.
> 
> And who is responsible for that then?

Caller can be sure, that the data change will eventually be processed.
The process can get stuck for some time, but after manual intervention,
it is processed.

The advantage is you don't need to do error recovery, which is nearly
impossible in systems that does not implement distributed transactions.
Compensations do not need to be done, you just fire it and forget.

This approach is less error prone, and it can be used for all the data
changes. But for most of it - yes.


-- 
Later,

 Lukas "lzap" Zapletal
 #katello #systemengine




More information about the katello-devel mailing list