Crash-only design depicted as generalization of a typical transactional model that we already have in database systems. Application is divided into crash-only components where similar components can be grouped into bigger crash-only components (Recursive).
All important non-volatile states are managed by dedicated state stores. And note they should also be crash-safe otherwise, it will crash unsafely just after one step. For this purpose crash-safe state stores are chosen such as databases. Paper also describes how inter component communication is done by exemplifying with time-out mechanism. And lastly it explains the restart/recovery mechanism.
References
No comments:
Post a Comment