4 posts about architecture.
What real attacks on cloud backups tell us about keeping the recovery copy in the same Azure subscription as production — where immutability holds, where a subscription boundary helps, where only a separate tenant does, and what the regulators and frameworks actually ask for
A design constraint for disaster recovery tooling — resolve every restore against a configuration snapshot captured before the incident, never against a live query — and what falls out of it: pure-function planning, fully offline tests, and drills cheap enough to run continuously
What happened when I pointed a shared AI merge-request reviewer at an architecture repository containing no code — separating the mechanical gates from the judgement checks, forbidding fabrication, and the style rule that would have broken the build
Drools is no longer the only game in town. A look at Easy Rules, RuleBook, and when you should reach for a rules engine at all.