Implementing a New Azure Service Emulator
An advanced developer wants to add support for an Azure service that Quinzee does not yet implement.
Advanced · Contributor · Source access required
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 internals book explains how service behavior is separated from transport and privileged helpers.
The proposed example
Draft a new module against the documented host/capability contracts, defining routing, identity, state ownership and compatibility tests before implementation.
Required capabilities
Authorized source access, the native C++ toolchain and regression/compatibility tests.
Boundaries and remaining work
The codebase is proprietary. Publishing internals does not itself grant source access or modification/distribution rights; no stable third-party plugin ABI is promised.
What to verify
- State the supported API subset and explicit exclusions.
- Do not promise a stable external plugin ABI or completed service; the example module is future tutorial work.
Read the three perspectives
- The Book of Quinzee: Meet Quinzee and its services
- The Book of Quinzee: Service compatibility and limits
- Quinzee Administrator’s Guide: Understand modules and their dependencies
- Quinzee Internals: Architecture and trust boundaries · Primary reference
- Quinzee Internals: Source layout and conventions · Primary reference
- Quinzee Internals: HTTP library and asynchronous execution · Primary reference
- Quinzee Internals: Connection and streaming lifecycle · Primary reference
- Quinzee Internals: Testing and verification · Primary reference
- Quinzee Internals: Module host and service state · Primary reference