Principles
How I design systems
The architecture principles behind my decisions, from the cloud workload up to the enterprise.
Cloud Architecture
6/6 writtenCost Optimization
One of the most important Architecture Design Principles in systems architecture decision-making. After all, who wants to pay for what they don't need?
20 min read
Operational Excellence
Operations as an enabler of the product and continuous improvement, not as bureaucracy
19 min read
Performance Efficiency
Fast for the user, lean on resources and ready to grow: performance is a requirement you design for, not a miracle you pray for in production.
29 min read
Reliability
Everything fails, all the time: reliability is deciding in advance how much failure you can afford and making sure the system survives the rest.
32 min read
Security
Protecting confidentiality, integrity and availability in a world where the perimeter is gone. After all, who wants to find out about a breach from the news?
32 min read
Sustainability
The greenest server is the one you never had to turn on. After all, why burn energy on work nobody asked for?
27 min read
Enterprise Architecture
5/5 writtenBusiness Alignment
Architecture that doesn't move a business metric is just an expensive hobby: every capability, system and decision should trace back to an outcome someone actually cares about.
30 min read
Governance
Guardrails, not gates: governance that lets teams move fast without driving off a cliff. After all, who wants to wait a month for a meeting to say yes?
34 min read
Portfolio Rationalization
A lean application portfolio, with no redundancy and no hidden costs. After all, why pay three times for the same CRM?
28 min read
Risk Management
Every architecture carries risk. The real question is whether anyone knows which ones, and who agreed to carry them.
33 min read
Standardization
Reusable standards and building blocks so every team stops reinventing the wheel. After all, who wants to fix the same bug in twelve different loggers?
34 min read