When creating styles, we commonly begin by focusing on practical demands:
“Exactly how will data be stored?”,
“Exactly how will questions be executed?”,
“How will back-ups be managed?”
Nevertheless, the actual challenge lies in ensuring that the application stays reputable, scalable, and maintainable as it expands. Phase 1 of guide triggers us to reflect on these three key principles.
Integrity: Staying Up when faced with Failures
Dependability is the system’s capacity to proceed operating even when it comes across failures– whether they’re triggered by equipment faults, software program bugs, or human blunders. Since eliminating all failings is unrealistic, the functional method is to construct fault-tolerant devices.
- Hardware failures: RAID, redundant power materials, hot-swappable parts
- Software program bugs: Turmoil screening tools (e.g., Turmoil Ape), medical examination
- Human errors: Automated rollbacks, thorough documents, and tracking systems
A well-designed system ensures that a failed disk does not stop the system, and a crashed process does not lead to data loss