Enterprise Architect · Subhakanta Kar
Clear decisions. The right sequence. Explicit ownership.
Practical essays for architects, technology leaders, and engineers working with infrastructure, cloud, operations, governance, and long-term technology decisions.
From hands-on system administration to enterprise architecture — a career shaped by execution, operations, and long experience inside real systems.
Cross-domain thinking across governance, cloud, identity, security, platforms, and long-horizon technology decisions.
Practical technology thinking across hybrid infrastructure, cloud platforms, networking, operations, and systems that need to run reliably.
The writing here is for people who live inside real technology environments — leaders, architects, engineers, and curious readers trying to understand how complex systems actually work.
Essays on decision clarity, governance, trade-offs, and the hidden cost of late technical choices.
Writing on infrastructure, cloud, identity, reliability, and the practical work behind stable systems.
Plain-English reflections on how technology decisions shape organisations, teams, and long-term outcomes.
If you are new here, begin with the Useful Reads section. It gives the clearest view of the thinking behind this site.
Six essays that cover the core ideas on this site — decisions, infrastructure, governance, cloud, and the architecture role.
Why technical decisions become exponentially more expensive the longer they are deferred — and what that means for how architecture work should be sequenced.
Read →A measured defence of rigorous lift-and-shift — and a closer look at which workloads actually deserve re-architecture, and which do not.
Read →How to build architectural governance that creates clarity and reduces risk — without becoming the thing that slows everything down.
Read →On the relationship between operational simplicity and long-term scalability — and why the most resilient platforms are usually the least exciting ones to operate.
Read →Architecture is not a diagram or a document. It is the set of decisions that determine what a system can and cannot become — and who is accountable for making them.
Read →A plain account of what enterprise architecture actually involves — the decisions, the trade-offs, the conversations, and the parts that rarely appear in the job description.
Read →Decision frameworks, governance, trade-offs, and the long-horizon thinking that keeps large technology estates coherent.
Datacenter exit, hybrid platforms, cloud migration, and the foundational work that everything else depends on.
Identity, access, security boundaries, and the trust decisions that quietly determine whether complex systems remain safe, usable, and governable.
The unglamorous, consequential discipline of keeping complex systems running calmly, safely, and predictably.
How technology decisions get made, communicated, and owned — and what happens when they are not.
Practical reflections on how architecture choices change across regulated, distributed, infrastructure-heavy, and fast-moving technology environments.
After years inside enterprise technology environments, I have learned that the hardest problems are often about clarity, timing, ownership, and communication. I write to make those quieter lessons easier to see.
I am Subhakanta Kar, an enterprise architect with practical experience across infrastructure, cloud, operations, governance, and large-scale technology environments. I write about the decisions behind stable systems — the trade-offs, pressures, mistakes, and quiet work that rarely appear in official presentations.
I grew up in Odisha, in a place where things were repaired before they were replaced and where patience was treated as a form of competence. I came into technology through the slower door — system administration, datacentre work, the kind of jobs where you learn what production actually feels like. Those years are formative. You stop believing in tidy architecture diagrams once you have spent a weekend reconciling one against the truth of a real estate.
From there I moved across infrastructure, solution architecture, and enterprise architecture — through many different industries and environments over more than two decades. The industries changed. The patterns underneath repeated. Most large environments are not failing because the technology is wrong. They are failing because the decisions are unclear, or because nobody knows why the system is the way it is any more.
I write because the writing forces me to be honest about what I actually think. The essays here are the lessons I would have wanted to read fifteen years ago — practical, calm, written for people inside real systems. The thread through all of it is the same: clarity over hype, simple over clever, maintainable over impressive.
Architecture grounded in practice
The questions I keep returning to across every environment and every role:
Cost, security, accessibility, scalability, and compliance never improve together. A practical essay on the trade-offs that decide whether a global architecture holds.
Read article →Most exits do not fail during the migration. They fail eighteen months later. An honest look at where the damage gets done.
Read article →Every migration plan defers identity. Almost every difficult year-two problem traces back to that deferral. Why identity must come first.
Read article →Practical self-assessments, decision guides and learning tools built from the same thinking as the writing. Free, independent and vendor-neutral.
Assess cloud adoption readiness across business, technical, operational, security, financial and governance dimensions.
Open tool →Assess whether an application capability is better suited to normal non-AI software, AI-led design, or a controlled hybrid architecture.
Open tool →Decide where a workload or capability should run — in-house, colocation, managed hosting, private cloud, public cloud, PaaS, SaaS, or hybrid.
Open tool →Understand your current architecture review stage, expected ARB approval gate, likely review level, missing preparation items, and recommended next action.
Open tool →Think through cloud infrastructure choices before selecting a platform, migration path, or operating model.
Open tool →Assess whether a small-business IT environment is fragile, stable, or ready to grow.
Open tool →Technology card games for children, students, and beginners to explore servers, networks, cloud, security, data, and infrastructure ideas.
Open the Lab →Turn scattered architecture review preparation into a structured, decision-ready document for ARB, HLD, security, cloud, risk, NFR, and production-readiness reviews.
Open the pack →Good architecture is not about complexity. It is about removing it. After two decades working inside complicated technology environments, I found myself returning to the same set of principles — the ones that consistently led to calmer, more durable outcomes. This book is my attempt to write those down honestly.
Currently writing · Expected release: 2026
Simple IT Architecture is a personal writing project aimed at architects, technology leaders, and engineers who want to stop over-engineering and start building systems that actually work — and continue to work, years from now.
Get notified on release →I publish practical reflections on enterprise architecture, infrastructure, cloud, operations, and calm technology decision-making.
For thoughtful architecture conversations, writing feedback, or professional exchange, you can reach me here.
This is a personal site for writing and thinking about architecture. Views here are my own and are not affiliated with any employer. If you would like to discuss an idea, share a reaction to something I wrote, or exchange thinking on a difficult architecture question — you are always welcome to write.
Say Hello