Lambda Web Functions: When a Function Becomes a Web Server

AWS Lambda Web Functions run an ordinary HTTP server, serve many requests per environment and bill by CPU time. What the contract is, what the billing model rewards and punishes, with a measured server and a cost model checked against AWS’s own examples, and where it sits against function URLs, API Gateway and App Runner.

Read more →

Azure Container Apps or AKS for a Regulated Workload: Who Patches What

For a regulated workload the container platform decision is mostly about who patches what and who can prove it. A ledger of thirteen operational duties across Container Apps, AKS Automatic and AKS Standard, the same security baseline written twice in Terraform with tests, and a decision rule short enough to argue with.

Read more →

One Contract, Two Clouds: A Network Baseline on AWS and Azure with Terraform

Do not write one Terraform module that hides the cloud. Share the contract instead: the same inputs, outputs, naming and contract tests over an AWS implementation and an Azure implementation, tested on Terraform and OpenTofu with mocked providers, with the cost of the switch-module design measured.

Read more →

Testing Infrastructure Code: terraform test, Mock Providers and a Policy Gate in CI

A Terraform module for a clinical-document bucket tested three ways in CI with no cloud account: fourteen unit tests on a mocked provider that pass on Terraform 1.16 and OpenTofu 1.12, ten deliberate defects that the tests must catch, and a policy gate over the JSON plan.

Read more →

Azure OpenAI Structured Outputs for Clinical Coding: Free Text to FHIR Condition and Observation, with a Human Review Step

A model proposes coded findings from a clinical note inside a strict JSON Schema whose enums are an approved code subset; code checks every proposal against the note; a clinician accepts or rejects; and only accepted items become FHIR Condition, Observation and Provenance resources. C# on .NET 10 and Python.

Read more →