Field Notes
Decisions that look simple in a diagram but behave differently in production
Short, practical notes on decisions that look simple in a diagram but behave differently in production. Each note addresses a specific decision, challenges a common assumption, and links to the review when the problem is active.
Decision brief
Why another region does not automatically increase availability
A second region adds failure boundaries, replication behavior, routing, state reconciliation, deployment coordination, and recovery decisions. It does not automatically remove application or ownership failure modes.
2 min read
Decision brief
Cloud cost optimization starts with ownership
Discounts and waste cleanup can reduce a bill temporarily, but persistent cost problems commonly survive when teams cannot attribute spend to workloads, owners, demand, or architecture.
2 min read
Decision brief
Why platform teams fail after adopting Kubernetes
Kubernetes supplies orchestration primitives. It does not create a product, adoption model, paved road, support boundary, or measurable reduction in cognitive load.
2 min read
Decision brief
Throughput without replay is a hidden reliability problem
A pipeline can meet throughput targets while losing operational control when failed or disputed work cannot be identified, replayed idempotently, governed, and explained.
2 min read
Educational analysis
What an EKS upgrade plan reveals about platform maturity
The upgrade command is the smallest part of lifecycle readiness. API deprecation, add-on compatibility, node disruption, PDB behavior, IaC repeatability, validation, and ownership reveal actual maturity.
2 min read
Educational analysis
A DR plan is not evidence until restore is exercised
Backup configuration proves that jobs were requested, not that workloads, dependencies, identities, and state can be restored within meaningful objectives.
2 min read
Decision brief
Why a 90-day platform transformation plan is usually dishonest before discovery
A calendar produced before the constraint, dependencies, evidence, and ownership are understood is a sales promise rather than an engineering plan.
2 min read
What platform decision is currently consuming leadership attention?
Share the decision and why it matters now. The first conversation is used to determine whether Lirado Tech's operating experience is relevant.
Bring a platform decision