A robust system is often misunderstood to be the one which doesn’t fail. On the contrary, the guiding principle is that the system should be designed in a way that it fails fast and recovers gracefully. This ensures minimal impact on the operations and optimal utilization of the resources. Let It Crash Principle – the guiding principle is phrased as such – is one of the cornerstones of SAP BTP solutioning.
 
Let it crash principle can further be broken down into three core ideas. The first one is – Fail Fast – the system should detect the errors as soon as possible rather than let them propagate leading to complex issues and difficult tracing of root cause. The second idea is the isolation of Components – the solution should be modularized and compartmentalized to avoid any domino effect of errors and failures in one onto the following. The last core idea is – Recovery – the system should be developed in a manner that it should recover from the errors without any manual intervention as much as possible.
 
Example of Let it Crash principle in SAP BTP Developments –
1. Usage of Circuit Breaker Patterns
2. Isolated and Stateless Microservices
3. Containerized applications
4. Centralized Logging Service
5. Implementation of monitoring tools

~S