Session:Systems design: Transparent persistence vs crash-only
From 36C3 Wiki
| Description | Introduction to two properties of operating systems/programming languages/any software and their relationship |
|---|---|
| Website(s) | |
| Type | |
| Kids session | No |
| Keyword(s) | |
| Processing assembly | Assembly:Curry Club Augsburg |
| Person organizing | MichaelStruwe |
| Language | en - English |
Other sessions...
| |
(Click here to refresh this page.)
| Starts at | 2019/12/30 13:15 |
|---|---|
| Ends at | 2019/12/30 13:30 |
| Duration | 15 minutes |
| Location | Room:Lecture room M2 |
- Transparent persistence: Every variable in the programming language is persisted to disk automatically
- Crash-only: Software needs to be prepared to crash at any point in time. Crashing takes the place of failing and shutting down.
