Experimenting with Cloud Architecture
A developer wants to compare architectural approaches.
Advanced · Architect, Developer · 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
Local consumers and message state make delivery ordering, retries and coupling easier to investigate.
The proposed example
Design synchronous, queue-based and event-delivery variants of one small workflow, with the same input and expected result.
Required capabilities
Queues/topics, supported delivery protocols and consumers that tolerate redelivery.
Boundaries and remaining work
No Service Bus sessions, transactions or scheduling, and no Event Grid dead-lettering. Applications own idempotency.
What to verify
- Observe redelivery and make consumers idempotent.
- Compare behavior and operational complexity; do not extrapolate local throughput to Azure capacity.
Read the three perspectives
- The Book of Quinzee: Deliver work with Service Bus · Primary reference
- The Book of Quinzee: Run HTTP and Service Bus functions · Primary reference
- The Book of Quinzee: Provision event delivery and durable messaging · Primary reference
- Quinzee Administrator’s Guide: Keep events and messages moving
- Quinzee Internals: Service Bus and Functions execution
- Quinzee Internals: Files, transactions and what a crash can leave behind