<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Santhosh GK</title>
    <description>The latest articles on DEV Community by Santhosh GK (@santhosh_gk_2902).</description>
    <link>https://dev.to/santhosh_gk_2902</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1712282%2Fb3e18e30-75ff-410b-a02c-e87f7bcba33f.jpg</url>
      <title>DEV Community: Santhosh GK</title>
      <link>https://dev.to/santhosh_gk_2902</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/santhosh_gk_2902"/>
    <language>en</language>
    <item>
      <title>HELIX-Artificial Intelligence Isn't Separate from Enterprise Architecture</title>
      <dc:creator>Santhosh GK</dc:creator>
      <pubDate>Thu, 23 Jul 2026 15:45:28 +0000</pubDate>
      <link>https://dev.to/santhosh_gk_2902/helix-artificial-intelligence-isnt-separate-from-enterprise-architecture-5f84</link>
      <guid>https://dev.to/santhosh_gk_2902/helix-artificial-intelligence-isnt-separate-from-enterprise-architecture-5f84</guid>
      <description>&lt;p&gt;If you've been in tech over the last year, you've probably noticed that almost every conversation eventually ends up talking about AI.&lt;br&gt;
LLMs, AI Agents, RAG, MCP, prompt engineering...there's something new every week.&lt;/p&gt;

&lt;p&gt;Like many of you, I've been spending time learning these technologies, experimenting with different tools, and trying to understand where everything is heading.&lt;/p&gt;

&lt;p&gt;But while learning AI, one question kept coming back to me.&lt;br&gt;
Whre does AI actually fit within Enterprise Architecture?&lt;/p&gt;

&lt;p&gt;Most conversations start with the model.&lt;/p&gt;

&lt;p&gt;I think they should start with the enterprise.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Looking Back&lt;/strong&gt;&lt;br&gt;
Over the last two decades, I've worked through several technology shifts.&lt;/p&gt;

&lt;p&gt;Physical infrastructure → Virtualization&lt;br&gt;
Virtualization → Cloud&lt;br&gt;
Cloud → Platform Engineering&lt;br&gt;
Automation → Everything&lt;/p&gt;

&lt;p&gt;Every transition introduced new tools, new platforms, and new buzzwords.&lt;/p&gt;

&lt;p&gt;But something interesting never changed.&lt;br&gt;
Successful enterprise systems still depended on the same fundamentals:&lt;/p&gt;

&lt;p&gt;Business goals&lt;br&gt;
Enterprise Architecture&lt;br&gt;
Reliable platforms&lt;br&gt;
Security&lt;br&gt;
Data&lt;br&gt;
Governance&lt;br&gt;
Operations&lt;/p&gt;

&lt;p&gt;Technology changed.&lt;br&gt;
Engineering principles didn't.&lt;/p&gt;

&lt;p&gt;That's one of the reasons I don't see AI as something completely separate.&lt;/p&gt;

&lt;p&gt;AI Is Just Another Enterprise Capability&lt;/p&gt;

&lt;p&gt;Today, AI is often treated like its own universe.&lt;/p&gt;

&lt;p&gt;Dedicated AI teams.&lt;br&gt;
AI platforms.&lt;br&gt;
AI roadmaps.&lt;br&gt;
AI strategies.&lt;br&gt;
That all makes sense.&lt;/p&gt;

&lt;p&gt;But I think there's a risk if we start treating AI as something that sits outside Enterprise Architecture.&lt;/p&gt;

&lt;p&gt;AI doesn't work in isolation.&lt;br&gt;
It needs good data.&lt;br&gt;
It needs infrastructure.&lt;br&gt;
It needs platforms.&lt;br&gt;
It needs security.&lt;br&gt;
It needs governance.&lt;br&gt;
It needs integration with business applications.&lt;/p&gt;

&lt;p&gt;And, most importantly, it needs to solve a real business problem.&lt;/p&gt;

&lt;p&gt;From an architect's point of view, AI isn't an island.&lt;/p&gt;

&lt;p&gt;It's another enterprise capability.&lt;/p&gt;

&lt;p&gt;Just like databases, APIs, messaging platforms, Kubernetes, and cloud services became part of our enterprise landscape, AI is becoming another capability that needs to be architected—not bolted on.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The Enterprise Architect in Me&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;One thing I've always liked about Enterprise Architecture is that we rarely start with technology.&lt;/p&gt;

&lt;p&gt;We usually ask questions like:&lt;/p&gt;

&lt;p&gt;What business problem are we solving?&lt;br&gt;
Which capability are we improving?&lt;br&gt;
What data do we need?&lt;br&gt;
How will this integrate with existing systems?&lt;br&gt;
How do we operate and govern it?&lt;/p&gt;

&lt;p&gt;Only then do we choose the technology.&lt;/p&gt;

&lt;p&gt;Personally, I think AI deserves the same treatment.&lt;/p&gt;

&lt;p&gt;Instead of asking:&lt;/p&gt;

&lt;p&gt;"How do we implement AI?"&lt;/p&gt;

&lt;p&gt;maybe we should ask:&lt;/p&gt;

&lt;p&gt;"Which business capabilities can benefit from intelligence, and how should we architect that?"&lt;/p&gt;

&lt;p&gt;It's a small change in thinking, but I believe it leads to much better solutions.&lt;br&gt;
It's About More Than Models&lt;/p&gt;

&lt;p&gt;Right now, everyone is comparing models.&lt;/p&gt;

&lt;p&gt;Who's faster?&lt;br&gt;
Who's smarter?&lt;br&gt;
Who's cheaper?&lt;/p&gt;

&lt;p&gt;Those are interesting discussions.&lt;br&gt;
But in the enterprise, success usually comes down to questions like:&lt;/p&gt;

&lt;p&gt;Can we trust the data?&lt;br&gt;
Is it secure?&lt;br&gt;
Can we scale it?&lt;br&gt;
Can we operate it?&lt;br&gt;
Can we govern it?&lt;br&gt;
Does it actually create business value?&lt;/p&gt;

&lt;p&gt;Those aren't AI questions.&lt;br&gt;
They're engineering questions.&lt;br&gt;
And we've been dealing with them for years.&lt;/p&gt;

&lt;p&gt;Why I Started HELIX&lt;/p&gt;

&lt;p&gt;Over the last few months, I've been documenting my learning and trying to connect the dots between Enterprise Architecture, Platform Engineering, and AI.&lt;/p&gt;

&lt;p&gt;That became HELIX.&lt;/p&gt;

&lt;p&gt;It's simply my engineering journal.&lt;/p&gt;

&lt;p&gt;A place where I share ideas, architectural viewpoints, experiments, and lessons as I continue learning.&lt;/p&gt;

&lt;p&gt;Some posts will be architecture-focused.&lt;br&gt;
Some will be hands-on.&lt;br&gt;
Some may simply be questions I'm still trying to answer.&lt;br&gt;
And that's okay.&lt;br&gt;
Technology evolves, and so should our thinking.&lt;/p&gt;

&lt;p&gt;Let's Discuss&lt;/p&gt;

&lt;p&gt;This is just one perspective.&lt;/p&gt;

&lt;p&gt;I'm genuinely interested in hearing how others see it.&lt;/p&gt;

&lt;p&gt;Do you think AI should be treated as its own discipline?&lt;br&gt;
Or do you see it as another capability within Enterprise Architecture?&lt;br&gt;
How is your organization approaching Enterprise AI?&lt;br&gt;
What challenges have you run into?&lt;/p&gt;

&lt;p&gt;I'd love to hear your thoughts in the comments.&lt;/p&gt;

&lt;p&gt;If you're an architect, platform engineer, developer, or just someone exploring AI in the enterprise, let's learn from each other.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Final Thoughts&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;AI will continue to evolve.&lt;br&gt;
New models will come.&lt;br&gt;
New frameworks will appear.&lt;br&gt;
But I believe good engineering principles will remain the same.&lt;/p&gt;

&lt;p&gt;Business.&lt;br&gt;
Architecture.&lt;br&gt;
Platforms.&lt;br&gt;
Governance.&lt;br&gt;
Operations.&lt;/p&gt;

&lt;p&gt;AI doesn't replace those foundations.&lt;/p&gt;

&lt;p&gt;It builds on them.&lt;/p&gt;

&lt;p&gt;That's the journey I'm exploring through HELIX, and I hope you'll join the conversation&lt;/p&gt;

&lt;p&gt;Thanks for reading! 👋&lt;br&gt;
This is the first article in my HELIX series, where I'll be exploring the intersection of Enterprise Architecture, Platform Engineering, and Artificial Intelligence. If you enjoyed this article or have a different perspective, I'd love to hear from you. Let's build the discussion together.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>architecture</category>
      <category>discuss</category>
      <category>t</category>
    </item>
  </channel>
</rss>
