|
|
|
|
|
|
by hderms
1510 days ago
|
|
|
I feel like people don't go deep enough into how to write 'crash only software' in these discussions. Like what are the options? 1. write ahead log before you do side effects/idempotent side effects 2. double writes to disk to prevent torn writes 3. checksums to make sure we don't make bad decisions based on bad data 4. redundancy/anti-entropy/other distributed system patterns which attempt to obviate the need to be overly concerned with a single process crashing 5. self-healing patterns when bad data is found anyone have any other ideas? |
|
|