From Site Reliability Engineering to AWS Solutions Architecture
Latest Articles
Zero Token Architecture: Reason Once, Automate What Repeats
03 Oct 2026 · AI & Automation
Repeated infrastructure checks need dependable execution. When inputs and decisions are already defined, asking a model to rediscover the procedure on every run adds a dependency that ordinary…
Welcome to my cloud architecture portfolio. I am Narendranath Panda, an Enterprise Cloud & Platform Architect with 20+ years of experience across enterprise software and infrastructure.
My work is organized around four connected pillars: Enterprise Platform Architecture, AWS Architecture, AI Platform Engineering, and Technical Leadership.
The articles connect architecture decisions with delivery, security, reliability, observability, cost and operations. Public material is curated from private projects, labs and case studies, with professional experience, prototypes and learning clearly distinguished.
Explore My Journey Browse AWS Architecture About Me
My Engineering Progression
1. SRE Foundations
I started with the operational disciplines that make systems dependable: monitoring, logging, capacity management, backup and recovery, incident prevention, and measurable reliability.
Practical guides: Linux and Talos Operations · VictoriaLogs · Thanos · Business Continuity · Backup and Restore
2. Cloud-Native & Kubernetes Engineering
I expanded those reliability practices into container platforms—managing Kubernetes resources, cluster access, ingress, autoscaling, certificates, secrets, and workload security.
Practical guides: Kubernetes Resource Management · Cluster Access · mTLS · Image Security · Supply-chain Attestation
3. Platform Engineering & GitOps
I moved from operating individual clusters to creating repeatable platforms with Argo CD, CI/CD, reusable infrastructure modules, policy-driven delivery, and multi-cluster automation.
Practical guides: Multi-Cluster Argo CD · IaC Pipelines · Terragrunt · Harbor IaC
4. AWS Solutions Architecture
My current focus applies the same operational depth to AWS architecture: identity, networking, compute, storage, resilience, security, observability, automation, and cost optimization. The goal is to connect design decisions to business outcomes and the AWS Well-Architected pillars.
Practical guides: AWS IAM and Terraform Backend · EKS Auto Mode with S3 · Karpenter on EKS
Architecture Principles
- Design for failure, recovery, and measurable service objectives.
- Automate infrastructure and delivery through version-controlled workflows.
- Apply least privilege, layered security, and auditable access.
- Balance reliability, performance, sustainability, and cost.
- Document trade-offs, validation steps, and production considerations.
Explore the Portfolio
Use the navigation to follow the progression in order, or start with the dedicated AWS Architecture hub. Each guide captures practical implementation work and the architecture reasoning behind it.