Cloud and System Architecture Review
Find the reliability, cost, ownership, and complexity decisions that are quietly slowing your team down.
Modern software architecture is not just boxes and arrows. It is the operating model that lets a system evolve, recover from failure, and keep delivery confidence as the business changes.
Relevant Writing
Your MCP Servers Are Now a CPS 230 Service Provider Problem
When an APRA-regulated entity wires an AI agent to an MCP server, it may have just added a material service provider to its CPS 230 register. Most teams have not noticed. APRA will.
The Supply Chain Moved Upstream: GitHub, Canvas, and Trivy
From 19 March to 26 May 2026, three incidents hit three trusted software surfaces: the editor, the scanner, and the platform. The lesson is not only to patch faster. It is to govern the toolchain.
APRA CPS 230: The 90-Day Engineering Framework
Why many CPS 230 programs are still 5-star, and how engineering teams can get to 10-star proof in 90 days with clearer RTO/RPO mapping, incident triggers, and Board-ready evidence.
AU Fintech Compliance Stack: Four AI Clocks, One Architecture Problem
ASIC's cyber 'minute to midnight' warning, APRA's AI governance gaps, the EU AI Act's 2 August 2026 transparency date, and the DTA's 15 June 2026 mandate all point to the same fintech challenge: one control stack for governed AI.
Architecting Cloud-Native Systems with DDD and EDA: AWS vs GCP
A strategic guide to using Domain-Driven Design and Event-Driven Architecture on AWS and GCP, with practical service choices, trade-offs, and decision tests.
Event-Driven Architecture in Practice: AWS vs GCP
A practical guide to building event-driven systems on AWS and GCP, covering EventBridge, Pub/Sub, Eventarc, contracts, failure handling, and real-world operating trade-offs.
Resilience Engineering in the Cloud: Building Systems That Survive
A practical guide to designing resilient cloud systems on AWS and GCP, with failure modes, circuit breakers, bulkheads, chaos testing, and recovery patterns.
What you leave with
- A clear map of architecture risks, trade-offs, and modernization options.
- Prioritized recommendations your team can sequence without a rewrite fantasy.
- Decision notes that make ownership, constraints, and next actions explicit.