q1tum.cloud

About

Sun, 17 May 2026 00:00:00 +0000

About q1tum.cloud

Hi, I’m Nathan — a tech enthusiast working in and around the Microsoft Azure ecosystem.

This blog is where I document things I’m exploring, learning, and building. It covers the topics that genuinely excite me:

Azure Cloud — architecture, services, cost optimisation, and best practices
AI — Azure OpenAI, Copilot, agents, and the LLM landscape
App Modernisation — containers, Kubernetes, microservices, DevOps, and making legacy code cloud-ready
Azure Quantum — quantum computing fundamentals, Q#, and where the tech is heading
General Tech — anything else that catches my eye

I write primarily for myself (to think things through and record what I’ve learned), but if it’s useful to you too, that’s even better.

Welcome to q1tum.cloud

Sun, 17 May 2026 00:00:00 +0000

Welcome. If you’re reading this, you’ve found q1tum.cloud — my corner of the internet for thinking out loud about technology.

What this blog is about

There are a few topics I keep coming back to, and this is where I write about them:

Azure Cloud — I spend a lot of time in Azure. Services, patterns, gotchas, architecture decisions — if it lives in a Microsoft data centre, I’m probably interested in it.
AI — The pace of change here is relentless. Azure OpenAI, Copilot Studio, LLM patterns, agents — I’m experimenting constantly and will share what I find.
App Modernisation — Moving workloads from monoliths to containers, from on-prem to cloud-native. The how and why of modernising software.
Azure Quantum — Quantum computing is still early, but the Azure Quantum service and the Q# language make it remarkably accessible. I’m learning, and I’ll write as I go.
General Tech — Anything else that grabs my attention.

Why bother writing?

Richard Feynman reportedly kept a list on his whiteboard of a dozen open problems he was always thinking about. Writing is my version of that — it forces clarity. If I can’t explain something in writing, I don’t understand it well enough yet.

Azure Regions and Availability Zones — What They Are and Why They Matter

Fri, 15 May 2026 00:00:00 +0000

If you’ve spent any time in the Azure portal, you’ve picked a region. But understanding why you pick a region — and how availability zones change the reliability story — is worth a few minutes of your time.

What is an Azure Region?

A region is a geographic area that contains one or more Azure data centres. Examples: UK South, East US, West Europe. Microsoft currently operates over 60 regions worldwide.

Getting Started with Azure OpenAI Service

Tue, 12 May 2026 00:00:00 +0000

Azure OpenAI Service gives you access to OpenAI’s models — GPT-4o, GPT-4, embeddings, DALL·E and more — through Azure’s infrastructure. You get the model capability of OpenAI plus Azure’s compliance posture, private networking, RBAC, and SLA.

Here’s a practical walkthrough to get from zero to first API call.

Why Azure OpenAI instead of OpenAI direct?

Concern	OpenAI direct	Azure OpenAI
Data privacy	Data used for model training (by default)	No training on your data
Network isolation	Public internet only	Private endpoint support
Compliance	SOC 2	SOC 2, ISO 27001, HIPAA, FedRAMP
Identity	API keys	Azure AD / managed identity
SLA	None on free tier	Up to 99.9%
Availability	Global	Specific regions

If you’re building anything serious on Azure, the compliance and identity story alone makes the Azure service worth it.

What is Quantum Computing? A Practical Introduction

Sun, 10 May 2026 00:00:00 +0000

Quantum computing has been “just around the corner” for years. But with platforms like Azure Quantum and mature tooling like Q#, it’s now something developers can actually touch. Here’s what you need to understand to get started — without the physics degree.

Classical vs quantum bits

A classical bit is binary — it’s 0 or 1. Every operation in your CPU, every byte in RAM, is built on this.

A qubit (quantum bit) can exist in a superposition of 0 and 1 simultaneously. That sounds like magic (“it’s both at once!”) but the useful intuition is this: a qubit represents a probability distribution over 0 and 1 until you measure it.

From Monolith to Microservices — A Pragmatic Migration Path

Fri, 08 May 2026 00:00:00 +0000

Microservices get sold as a silver bullet. They’re not. But for the right applications, decomposing a monolith unlocks independent scaling, faster deployments, and team autonomy. Here’s how to do it without rewriting everything at once.

Why not rewrite from scratch?

The “big-bang rewrite” is almost always a bad idea:

It takes much longer than estimated
You lose the implicit knowledge baked into the existing system
You have two codebases to maintain during the transition
You discover why the original decisions were made, the hard way

The better path is incremental extraction — peel off capabilities one at a time, validate, then continue.