214 views
Banking-grade AWS deployments, multi-cloud trade-offs, and database design at scale. The architectural decisions that prevent 3am incidents.
Most AWS accounts accumulate risk quietly. Nobody sets out to leave a broker with zero alarms, or to run two supposedly multi availability zone brokers in the same availability zone, or to leave statement level database logging writing customer data to plain text files. These things happen one reasonable seeming decision at a time, and […]
Read more →By Andrew Baker · Group CIO, Capitec Bank SQL Server 2025 quietly closed several of the holes that made Resource Governor unusable as a containment layer, and the one objection everybody repeats, that its classification is spoofable, turns out to be an artefact of classifying on APP_NAME() rather than on the authenticated login. Classify on […]
Read more →A production incident that shows up again and again has the same shape. Someone, whether a human analyst, a BI tool, or increasingly an AI agent writing SQL, runs a query with no WHERE clause, an accidental cross join, or a wildly underestimated scan. Postgres has no concept of “this query looks expensive, so deprioritize […]
Read more →DeepSeek, Kimi and GLM show why model choice and cloud choice can no longer be the same decision 1. Bedrock is a very AWS answer to generative AI Amazon Bedrock takes a chaotic market of model providers and wraps it in IAM, AWS networking, logging, governance, regional deployment and an existing enterprise commercial relationship. What […]
Read more →Most financial services firms start their cloud migration the way a learner driver would start a lesson on the edge of a cliff face. The car is already nose out over the drop, the engine is running, and the instructor’s first words are not “let’s talk about steering” or “here’s how the indicators work.” The […]
Read more →Presented at AWS Summit Johannesburg Leon Rajindrapersadh, CTO of Capitec, and Terrence Naidoo, Principal Solutions Architect at AWS, are presenting this architecture at AWS Summit Johannesburg on 19 August 2026 at the Gallagher Convention Centre. The session is titled “Database proxy for real time query optimization” and runs for 45 minutes from 13:30 in Breakout […]
Read more →1. The optimizer is making a bet, not a calculation Every time SQL Server compiles a query it runs an auction. The optimizer generates a handful of candidate plans, estimates the cost of each one in abstract units that roughly map to disk and CPU work, and picks the cheapest candidate it found within its […]
Read more →A deep technical walkthrough of Amazon S3 Files: what it actually is, where it earns its complexity, setup scripts, monitoring, costs and the production gotchas that will bite you if you skip straight to the mount command. Jump to: What it is · What it is not · Setup script · Performance tests · Monitoring […]
Read more →There is a version of this story that most technology vendors would prefer you heard. In that version, Switzerland evaluated Palantir’s data analytics platform, found it impressive, but ultimately declined due to vague concerns about national sovereignty: a regulatory sentiment, a political posture, nothing that applies to a commercial enterprise operating under normal procurement constraints. […]
Read more →Andrew Baker — andrewbaker.ninja — 13 June 2026 How to use a large language model inside your own AWS account to interrogate your infrastructure while it is on fire So your production environment is throwing errors at 2 AM, your on-call engineer is staring at a wall of CloudWatch noise, and someone in the incident […]
Read more →1. Two causes, one bill AWS cost posture problems in product accounts come from two distinct sources, and most remediation frameworks conflate them, which is why so much cost optimisation effort produces disappointing results. The detection scripts behind this analysis are published at github.com/andrewbakercloudscale/aws-bvr1. The more common cause is drift. Engineers make locally reasonable decisions […]
Read more →Most cloud governance programmes begin with good intentions and eventually collapse under their own weight. The team starts with a handful of useful controls, someone adds tagging standards, another team adds cost optimisation, security introduces benchmark scanning, and platform engineering introduces configuration standards. Before long the report contains thousands of findings spread across hundreds of […]
Read more →