Using Quinzee as an Internal Server for a Small Office
A small company needs to run internal applications but does not want to depend on external cloud infrastructure for every service.
Advanced · Administrator, Architect · Deployment study
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 Linux containers and Azure-shaped APIs provide components for evaluating an internal deployment.
The proposed example
Assess a small internal web application against supported App Service, storage and database contracts on an isolated Linux server.
Required capabilities
Registered Linux images, the external hosting helper, and supported HTTP or Service Bus triggers.
Boundaries and remaining work
One instance and supported Linux runtimes only; no autoscaling, slots or general Azure hosting parity.
What to verify
- Inventory persistence, networking, reboot behavior and all external helpers.
- Define and test backup, access control and failure recovery before considering operational use.
Read the three perspectives
- The Book of Quinzee: Run HTTP and Service Bus functions · Primary reference
- The Book of Quinzee: Host a web application · Primary reference
- The Book of Quinzee: Deploy application hosts and their identities · Primary reference
- Quinzee Administrator’s Guide: Operate Functions and App Service workloads
- Quinzee Internals: Service Bus and Functions execution
- Quinzee Internals: From desired state to a real container