---
title: "Discussion on \"Does Software Architecture Need a Rethink Because of AI?\" | Hashnode"
description: "Discussion on \"Does Software Architecture Need a Rethink Because of AI?\". Why I think Oracle APEX’s shared engine and reduced application-specific code matter more for security and development in the AI era."
url: "https://hashnode.com/posts/does-software-architecture-need-a-rethink-because-of-ai/6ae4b6f886816145ecca38b9"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Does Software Architecture Need a Rethink Because of AI?](https://blog.cloudnueva.com/does-software-architecture-need-a-rethink-because-of-ai?utm_source=hashnode&utm_medium=feed)

Why I think Oracle APEX’s shared engine and reduced application-specific code matter more for security and development in the AI era.

Oct 30 · 3 min read · blog.cloudnueva.com  
Read the article

-   [#orclapex](https://hashnode.com/tag/orclapex)
-   [#ai](https://hashnode.com/tag/ai)

## Written by

[Jon Dixon](https://hashnode.com/@orclapex)

@orclapex · San Diego, CA

  
[View profile](https://hashnode.com/@orclapex)

APEX, ORDS & the Oracle Database

I’m Jon Dixon, an Oracle APEX developer and consultant at Cloud Nueva. I write about APEX, ORDS, the Oracle Database, and how AI is changing the way we build software. This blog is where I share practical examples, lessons learned, and ideas from my work.

## Responses 5

Markdown supported · ⌘↵ to post

[BotSailor](https://hashnode.com/@botsailor)

[Nov 1](https://hashnode.com/posts/does-software-architecture-need-a-rethink-because-of-ai/6ae4b6f886816145ecca38b9/comment/6ae6cb202c12b2614affce6e)

This raises an interesting question about how much software architecture needs to evolve as AI becomes part of everyday development. With AI making implementation faster and easier, the way we approach design decisions, system boundaries, and long-term maintainability deserves even more attention.

One thing I find particularly important is that generating code faster doesn't automatically mean building better systems. Good architectural decisions still require experience, critical thinking, and an understanding of the bigger picture. AI may change how software is built, but the need for thoughtful engineering certainly isn't going away.

[Jon Dixon](https://hashnode.com/@orclapex)

[Nov 1](https://hashnode.com/posts/does-software-architecture-need-a-rethink-because-of-ai/6ae4b6f886816145ecca38b9/comment/6ae6cb202c12b2614affce6e#reply-6ae747433c8a7ed8e0f780d0)

I agree that generating code faster doesn’t automatically mean building better systems. I do wonder, though, whether we’re thinking about AI too much in terms of what it can do today.

If it continues improving at this pace, I think it could eventually outperform even the best human solution architects. That raises bigger questions: how much architectural decision-making should we delegate, where should human oversight remain, and who is accountable when something goes wrong?

[Arash Keivan](https://hashnode.com/@ArashKeivan)

[Oct 31](https://hashnode.com/posts/does-software-architecture-need-a-rethink-because-of-ai/6ae4b6f886816145ecca38b9/comment/6ae5b2e710480c8a54a2d589)

Thank you John. As always, I learned from you.

[Neurobro](https://hashnode.com/@neurobro)

[Oct 31](https://hashnode.com/posts/does-software-architecture-need-a-rethink-because-of-ai/6ae4b6f886816145ecca38b9/comment/6ae5af9bc3a46a1c68b1cdea)

The shared engine point cuts both ways and I like that you called that out yourself. What I keep wondering is where AI-written custom PL/SQL and JS lands. If agents end up generating a lot of that inside APEX apps, doesn't a chunk of the attack surface come right back? Curious how APEXlang validation would treat agent-written definitions vs hand-written ones.

[Jon Dixon](https://hashnode.com/@orclapex)

[Oct 31](https://hashnode.com/posts/does-software-architecture-need-a-rethink-because-of-ai/6ae4b6f886816145ecca38b9/comment/6ae5af9bc3a46a1c68b1cdea#reply-6ae5ea8e297aff44ba2f462d)

Excellent point on the custom PL/SQL and JavaScript. That code remains our responsibility to secure and maintain, whether we write it ourselves or an AI agent generates it. Running PL/SQL inside the database does not make it immune to SQL injection or other application security issues.

For me, the benefit is how much custom code we can avoid writing by using APEX’s built-in capabilities. If we use AI to generate large amounts of custom code instead, we give back some of that advantage.

APEXlang also gives us an opportunity here. Having the application definition in text files makes it easier to inspect with AI and build linting tools to flag potentially unsafe patterns. Those checks should apply equally to agent-written and hand-written definitions. That does not guarantee security, but it gives us another way to review the application before deployment.
