Plans are clues, not outcomes.
A technically plausible change still has to survive the measurement that matters.
About Alex Ivanov
Database work since 1990
I have spent my career making database decisions under real constraints.
Programmer. DBA. Database engineer. Data engineer.
I began in software and database work in 1990. Since then, I have worked through multiple generations of relational systems, data warehouses, cloud databases, and modern data platforms.
My experience includes PostgreSQL and AWS Aurora/RDS, Snowflake, Redshift, SQL Server, Oracle, AWS data services, dbt, Fivetran, and the operational systems around them.
Products change. The recurring engineering problem does not: teams still need to balance performance, availability, recovery, cost, delivery pressure, and operational ownership without pretending uncertainty has disappeared.
How I think
Tradeoffs belong in the recommendation.
Performance, resilience, cost, ownership, and rollback are part of one decision.
Automation should not inherit trust.
AI can accelerate evidence and drafts. Production authority remains explicit and human.
Cloud DBRE Tech
Why I built this practice.
Database reliability work is often split across dashboards, incidents, tickets, code changes, and tribal knowledge. Cloud DBRE Tech connects those fragments into decisions that remain reviewable after the immediate problem is gone.
“A bounded conclusion supported by evidence is more useful than a polished claim the system cannot defend.”