Engineering brief

Why AI agents need your existing event store, not a new architecture

This engineering brief covers Why AI agents need your existing event store, not a new architecture, with practical context for AI and developer-tool decisions.

AI Engineer

The Brief

Most teams think AI agents require new infrastructure. Kumar shows how to embed agents into existing event-sourced systems for fraud detection.

Decision relevance

Read this for workflow impact, implementation trade-offs, and the claims that need technical scrutiny before they reach team planning.

Summary

Divakar Kumar presents a real-world architecture for integrating AI agents into existing event-sourced systems, specifically for fraud detection. The key insight is that rule-based and ML models fail in the 'gray zone' of transaction risk, where agents can add context from multiple bounded contexts.

The approach uses a tiered system: Tier 1 handles clear cases with existing rules/ML, while Tier 2 uses agentic AI for uncertain transactions. Agents access a semantic layer built from domain events across transaction, account, device, and payment contexts via CDC or message brokers.

The architecture employs a fan-out pattern with specialized agents (risk analyzer, behavior analyzer) and a verdict agent that synthesizes their outputs. This avoids the false positives common in traditional systems by incorporating broader contextual data through tool-based access to materialized views.

Practical considerations include strict latency requirements (sub-500ms), using short-term memory only, and implementing loop termination metrics. The POC demonstration shows events propagating through CDC to projection layers, with agents accessing this semantic layer to produce decisions that feed back into the saga orchestration.

Why It Matters

Agents become operationally viable when integrated with existing event-sourced architectures rather than replacing them.

Editorial analysis

Key claims

  • Layer agents on existing systems for gray-zone decisions, not replacing proven workflows.

Practical use cases

  • Use this as input for tooling evaluation, workflow planning, and technical due diligence.

Risks / caveats

  • The POC simulation details; focus on architecture patterns instead.

Who should care

  • Engineering managers, tech leads, and CTOs evaluating AI or developer tooling decisions.

Related topics

Bottom Line

Layer agents on existing systems for gray-zone decisions, not replacing proven workflows.

Watch

This video is blocked due to your privacy settings. To watch this video, please accept YouTube marketing cookies.

Related breakdowns

Get TL;DW

Too Long; Didn't Watch.

A concise breakdowns of the AI and devtools videos that actually matter for engineering leaders.

Free. Weekly. No hype.

Video and thumbnails remain the property of their respective creators. tldw.news provides editorial analysis, commentary, and discovery links to original content.