The path· 3
- 1Advanced 10 minPrioritization Postmortem: When the Roadmap Becomes the IncidentRoadmap prioritization decisions rarely feel like incidents until production breaks. This article reconstructs the anatomy of a real failure caused by accumulated technical debt, ignored ADRs, and delivery pressure — and proposes the structural changes that prevent recurrence.
- 2Advanced 10 minAWS Transform at 1 Year: Agentic Legacy Modernization in ProductionAWS Transform arrived promising AI-agent-driven legacy modernization — after one year, it's worth examining what it actually delivers, where it falls short, and what the real adoption cost is in critical systems. This analysis is grounded in concrete technical evidence, not marketing.
- 3Expert 11 minMigrating to Stateful Cloud Native Platforms on AWS EKSMigrating stateful workloads to cloud native platforms is not merely a containerization exercise — it is a sequence of isolation, data consistency, and operational automation decisions that determine whether the platform survives production. In this article, I walk through the journey of a financial-grade platform that moved from manually managed VMs to a multitenant EKS environment with Kubernetes operators, managed persistent storage, and end-to-end observability.
Deep-dive studies
adrADR: AWS Transform & AI Agents vs Traditional Modernization FactoryThis ADR evaluates the decision to adopt AWS Transform (with AI agents for .NET, Mainframe, VMware, and custom code) versus a traditional human-engineering modernization factory, or a hybrid approach. The analysis covers regression risk, test coverage, code ownership, security, total cost, and change governance in an enterprise-scale modernization program.design-docDesign Doc: Enterprise Agentic Automation Layer with Amazon Q, MCP, and BedrockThis document proposes an agentic automation architecture for backoffice, support, and IT operations, connecting Amazon Q Business, the Model Context Protocol (MCP), internal tools, and Amazon Bedrock into a unified layer with mandatory human approval, immutable audit trail, and explicit action boundaries. The goal is to reduce repetitive manual work without sacrificing control, traceability, and security in regulated environments.design-docDesign Doc: Multi-Agent Orchestration with Amazon Bedrock and Step FunctionsThis document proposes a multi-agent orchestration architecture using Amazon Bedrock Agents in a supervisor/worker topology, with Step Functions managing state, retries, and human-in-the-loop. The focus is on separating reasoning responsibilities (LLM) from orchestration responsibilities (state flow), applying security guardrails, and controlling operational cost deterministically.adrADR: Model Selection on Amazon Bedrock — Claude vs Nova vs Llama vs Fine-tuneArchitectural decision on which foundation model to adopt for an enterprise GenAI feature on Amazon Bedrock, evaluating quality, cost per token, latency, data governance, pt-BR support, and context window. The conclusion is a task-type routing strategy — no single model wins across all axes.adrADR: Aurora Sharding — App-Level vs Aurora Limitless vs CitusA high-growth OLTP workload exhausted the capacity of a single Aurora PostgreSQL writer. This ADR evaluates three sharding strategies — application-layer sharding, Aurora Limitless Database, and managed Citus/PostgreSQL — weighing operational complexity, cost, cross-shard query support, and migration risk.adrADR: EventBridge vs Kafka/MSK for Order ProcessingThis ADR evaluates EventBridge and Amazon MSK as the event backbone for an order processing system, weighing throughput, ordering, replay, and operational burden. The decision is grounded in real trade-offs between managed simplicity and platform control, with direct consequences on cost, operability, and delivery guarantees.