Testing Application Behaviour During Service Failures
A developer wants to know how an application behaves when infrastructure stops working correctly.
Advanced · Developer, DevOps engineer · Integration design
Scenario overview; the standalone tutorial and its executable artifacts are not yet published. The proposed workflow still needs end-to-end implementation and verification.
What Quinzee contributes
Real native engines let a test observe a concrete dependency outage.
The proposed example
Plan a database stop/restart experiment using its documented lifecycle, then verify the application’s timeout and retry behavior.
Required capabilities
External engine supervisor, managed containers, native TLS clients and persistent volumes.
Boundaries and remaining work
No high availability, managed backup API or cluster simulation. Engine-native backups and coordinated restore procedures are required.
What to verify
- Record the steady-state result before the deliberate outage.
- Bound retries and verify recovery; no general latency/fault-injection API is documented.
Read the three perspectives
- The Book of Quinzee: Use PostgreSQL, MySQL and Redis · Primary reference
- The Book of Quinzee: Provision databases and a cache with real engines · Primary reference
- Quinzee Administrator’s Guide: Run PostgreSQL, MySQL and Valkey safely
- Quinzee Internals: Deployments and native engines
- Quinzee Internals: From desired state to a real container