Investigating Differences Between Quinzee and Azure
A developer discovers that an application behaves differently locally and in Azure.
Advanced · Developer, Contributor · Documented building blocks
Scenario overview; the standalone tutorial and its executable artifacts are not yet published. Start with the linked book exercises, which document the existing building blocks.
What Quinzee contributes
The compatibility tests and internals references help isolate implementation differences.
The proposed example
Reduce a local/Azure mismatch to one operation with fixed SDK version, request shape and synthetic data, then compare responses.
Required capabilities
A disposable source-built environment and the locked compatibility clients.
Boundaries and remaining work
A local pass covers the exercised contract; validate permissions, scale and failure behavior on Azure separately.
What to verify
- Capture status/error metadata without secrets.
- Decide whether the mismatch is a supported-contract regression or an excluded operation.
Read the three perspectives
- The Book of Quinzee: Deliver work with Service Bus
- The Book of Quinzee: Service compatibility and limits
- Quinzee Administrator’s Guide: Diagnose failures from the outside inward
- Quinzee Internals: Testing and verification · Primary reference
- Quinzee Internals: The compatibility application · Primary reference