Chief AI Architect, 11Bis Phan Ngu Street, Ho Chi Minh City (2026)

17/03/2026

Become a Claude Certified Architect now (register as a partner)
It costs 0$
Link - Check 1st comment 👇🏻

12/03/2026

Memory system for AI agents using markdown as storage.
-/github.com/Versatly/clawvault

09/03/2026

Multi Agent System Architecture
Building production grade AI agents is not just about calling an LLM. It requires orchestration, memory, tool integration, observability, and evaluation working together as a system.

A scalable multi agent architecture typically includes:

👉 User Interaction Layer
Handles chat, voice to text, or API input.

👉 Orchestration Layer
Includes an orchestrator, intent classifier using NLU or LLM, and an agent registry. This layer decides which agent should act and how tasks are decomposed.

👉 Knowledge Layer
Source documents and vector databases such as Pinecone for semantic retrieval and RAG workflows.

👉 Storage Layer
Conversation history, agent state, and registry storage. Often backed by Redis or cloud storage for persistence.

👉 Agent Layer
Supervisor agent coordinates multiple MCP client agents.
Local agents handle secure tool access.
Remote agents scale specialized capabilities.

👉 Integration Layer
MCP server and external tools such as databases, APIs, analytics engines.

👉 Observability and Evaluation
Tracing, logging, feedback loops, and automated evaluation to measure latency, cost, hallucination rate, and task success.

Example
- In an enterprise support system, a user asks for shipment delay analysis.
- The classifier detects logistics intent.
- The orchestrator routes the request to a Data Agent.
- The agent retrieves historical shipment data from a vector database and warehouse tables.
- Another agent computes anomaly detection on transit time.
- Supervisor aggregates results and generates an executive summary with metrics.

This architecture enables modular scaling, fault isolation, and domain specialization while keeping governance and security centralized.

Multi agent systems are becoming the backbone of enterprise grade Generative AI platforms

13/02/2026

Anthropic says their AI is safe to release.

The models are improving faster than the safety thresholds can keep up. The autonomous AI R&D line isn't far.

https://www.cdn.anthropic.com/f21d93f21602ead5cdbecb8c8e1c765759d9e232.pdf/

13/02/2026

AI vibe coding tools are exploding right now.

From AI-native editors like Cursor and Windsurf, to web app builders like Lovable and Bolt, to terminal power with Claude and cloud IDEs like Replit — each tool shines in a different lane.

The key isn’t picking the “best” one.
It’s matching the tool to your workflow, skill level, and goal.

Save this before you choose your stack.

30/01/2026

RAG Vs Agentic Rag
Retrieval Augmented Generation

29/01/2026

The Banking Marketplace Model 💡

As banks move away from the shrinking opportunities provided by traditional banking and undertake the journey to become living banks, there are a number of solutions they can employ. That state looks a long way off for most, yet the following product and channel solutions can help them move closer to it:

🙋‍♂️ Life moments orchestrator: The bank orchestrates its own ecosystem built around specific life moments.

👨‍💻 Marketplace orchestrator: Where the bank sells – either by white-labelling or co-branding – non-financial products to its customers.

🤝 Third-party ecosystem participant: This channel solution sees the bank offer its own financial products to a third-party’s customers via that third-party’s platform.

💳 Open Banking platform: Banks can leverage open APIs to enable partners to incorporate products, data and/or specific processes in their value propositions.

Although the marketplace approach lies outside many banks’ comfort zones, they are well-placed to make this happen: they can offer their products through the marketplaces of others, and they can set up marketplaces of their own to bring their products closer to customers. In this way, they can create an ecosystem of partners.

Banks come to this with some significant advantages. First, their customers trust them. Second, they are already at the centre of their customers’ lives. And third, they have flexible payments products that they can offer across those customers’ journeys.

Pursuing a marketplace solution requires that banks create specific new set-up capabilities to deliver and sustain platform banking. That starts by assessing their existing capabilities with a particular focus on platform-related areas like governance, innovation, and data and analytics.

Next, banks must activate a number of enablers to pursue their platform agenda. Among these: design first and foremost for a mobile customer experience; use analytics and AI-powered connected experiences to optimise hyper-relevancy; use bots to provide meaningful, fuss-free interactions for customers; create an API factory; and measure progress using a new KPI structure.

These enablers allow the bank to form individualised value propositions that link to key life moments and customer interests – all based on data. For example, should the platform determine that a customer is about to buy a house, get married or have a baby, it can provide a catalogue of relevant products and services, complete with coupons and discounts.

Source: Accenture

24/11/2025

Dành cho bạn nào muốn tăng độ an toàn mà không cần đầu tư đây.

Một phần mềm ứng dụng Web Application Firewall (WAF) nguồn mở được phát triển bởi Go and React.

github.com/casbin/caswaf/

20/11/2025

Don’t start Enterprise Architecture with a framework.

Wait, whaaaaaat?

Isn’t EA just about documents, diagrams, and endless debates over ArchiMate arrows?

No.

Enterprise Architecture is about connecting business stakeholders to their technological assets to turn vision into reality. If a framework helps you get there, great!
But it’s not the destination, it’s just a tool.

The real objective? Delivering value!

Cre: Maxime Vande Ghinste

18/11/2025

𝐄𝐧𝐭𝐞𝐫𝐩𝐫𝐢𝐬𝐞 𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐮𝐫𝐞 𝐂𝐚𝐫𝐞𝐞𝐫 𝐌𝐚𝐩𝐩𝐢𝐧𝐠

There's no single pathway into Enterprise Architecture… but there are some very common ones.

𝐓𝐡𝐞 𝐦𝐨𝐬𝐭 𝐜𝐨𝐦𝐦𝐨𝐧 𝐫𝐨𝐮𝐭𝐞 𝐢𝐬 ➝ 𝐒𝐨𝐥𝐮𝐭𝐢𝐨𝐧 𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭 → 𝐄𝐧𝐭𝐞𝐫𝐩𝐫𝐢𝐬𝐞 𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭
But as we know, the EA world is a bit more chaotic than that. 😄

Depending on these factors; EA's can come from different pathways:

🏦Organization Size
🗺️Country Origin
🤼Company Type (Product vs Consultancy)

Here are some of the most common EA entry routes I see:

🔹 Solution Architect → EA
🔹 Business Architect → EA
🔹 Project/Programme Manager → EA
🔹 Data Architect → EA
🔹 Management Consultant → EA
🔹 BA → BPM → EA

And then there's the wildcard route:

"My company had no EA function… so I became one accidentally." 😂

I do see the market shifting more to Solution Architect -> Enterprise Architect route but again that is subjective to the factors above.

𝐐. 𝐖𝐡𝐚𝐭 𝐰𝐚𝐬 𝐘𝐎𝐔𝐑 𝐫𝐨𝐮𝐭𝐞 𝐢𝐧𝐭𝐨 𝐄𝐧𝐭𝐞𝐫𝐩𝐫𝐢𝐬𝐞 𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐮𝐫𝐞?

31/10/2025

A Great Architect isn’t just a technology guru—they are a translator between the business strategy and the IT delivery ex*****on.

What Makes a Great Solution Architect
🎯 1. Outcome-Focused Design
Starts with the business problem, not the technology that they know.
Translates requirements into designs that deliver measurable outcomes—reducing costs, improving performance, enhancing the user experience, etc.
Avoids over-engineering by choosing the simplest viable solution that meets all the requirements
🧠 2. Pragmatic Technical Leadership
Deep hands-on experience of key platforms, integration, cloud, and security.
Guides developers and engineers through implementation decisions.
Bridges the gap between 'business wishes' and the 'technical reality' of what is possible.
⚙️ 3. Design for Delivery
Creates architectures that are buildable by real teams under real constraints (budget, time, skills).
Actively engages with delivery managers, engineers, and product owners to de-risk delivery.
Embeds architecture into the agile delivery practices — not just at the start.
🧩 4. Integration Competency
Understands how systems talk to each other — APIs, data flows, events, interfaces.
Has experience in removing dependencies and bottlenecks across the solution landscape.
Designs for change and extension, not brittle point-to-point systems.

🧭 A great Solution Architect makes complex delivery simple, achievable, and aligned to real business needs.

What Makes a Great Enterprise Architect
🌐 1. Strategic Translator
Connects the business strategy to technology ex*****on plans.
Creates a long-term strategy and the roadmap to get there.
Partners with the executive leadership to ensure investments align with their strategic priorities.
🧩 2. Single-page understanding of the Enterprise
Understands the whole enterprise landscape as business capabilities (Processes, People, Technology and Data)
Identifies proposed duplication and avoids technical debt.
Promotes reuse and standardisation without killing innovation and creativity.
📊 3. Governance That Enables
Defines principles, guidance, and reusable patterns that steer delivery teams.
Keeps governance 'just enough' to be focused on outcomes and alignment, not for control.
Ensures architectural decisions are traceable to business objectives.
🤝 4. Influential Relationship Builder
Builds trust with senior leadership, solution architects, and delivery teams.
Mediates between competing focuses — innovation vs organisational stability, delivery speed vs business and IT compliance.
Deploys storytelling with simplified diagrams to make the architecture understandable and actionable.

🏗️ A great Enterprise Architect shapes the technology landscape to enable solution investments to move the organisation toward its strategic business goals.

What makes a great architect in your enterprise?

04/10/2025

Enterprise Architecture: Guiding the Shift from Control to Value

For too long, Enterprise Architecture was seen mainly as compliance, governance, and slowing things down. But today, time to market speed is everything.

During my career, I’ve seen how EA can evolve into a compass for value — guiding organizations through complexity, accelerating change, and connecting strategy with ex*****on.

✅ What “value-driven EA” looks like:
▪️ Shaping business capabilities, not just enforcing standards
▪️ Creating modular, reusable platforms to speed up delivery
▪️ Acting as guardrails that enable, not gatekeepers that block
▪️ Embedding security, sustainability, and compliance from the start
▪️ Leveraging AI and data to enable smarter decisions, predictive insights, and automation
▪️ Driving process optimization to reduce friction, eliminate waste, and free up innovation capacity
▪️ Measuring outcomes: time to market, cost reduction, customer impact

The real power of EA is unlocked when architects collaborate closely with business and product teams — turning architecture from a cost center into a value engine.

👉 If EA in your organization is still mostly about control, it may be time to rethink its mandate.
The future belongs to enterprises where EA is not in the shadows, but at the heart of value creation.

Chief AI Architect

17/03/2026

12/03/2026

09/03/2026

13/02/2026

13/02/2026

30/01/2026

29/01/2026

24/11/2025

20/11/2025

18/11/2025

31/10/2025

04/10/2025

Address

Website

Alerts

Contact The Business

Shortcuts

Share

Category