Topic

Microservices Architecture

All digests tagged Microservices Architecture

· 21:37

Let's integrate AI Agents in Event-Sourced Systems — Divakar Kumar, FlyersSoft

The presentation outlines an advanced architectural pattern for integrating AI agents into existing enterprise systems, specifically targeting real-time fraud detection. Instead of replacing established Rule-Based Engines or ML models, the approach layers agentic intelligence to resolve 'gray zone' transactions—cases where current deterministic systems lack sufficient context. The architecture leverages Event Sourcing and Domain-Driven Design (DDD) principles by building a centralized semantic layer that aggregates data from multiple bounded contexts (e.g., Transaction, Device, Account). Agents then consume this enriched context via an orchestration layer in a saga pattern to reach a final verdict.

Key takeaways

  1. AI Agents Augment, Not Replace, Existing Systems

    The primary value of AI agents is not replacing existing systems (like rule-based or ML engines) but rather adding an agentic layer to handle ambiguous cases—the 'gray zone' where current models lack necessary context. The goal is to enhance business workflows using the state and history already captured by event sourcing.

  2. Context Aggregation via Semantic Layer 17:37

    To provide sufficient context for agents, data from disparate bounded contexts (Transaction, Device, Account, Payment) must be aggregated into a semantic layer or materialized view. This is achieved by propagating domain events using Change Data Capture (CDC) mechanisms or message brokers.

  3. Saga Orchestration and Agentic Decision Making

    The system uses an orchestration layer to manage the process. This layer employs a fan-out pattern, sending events simultaneously to multiple specialized agents (e.g., Risk Analyzer Agent, Behavior Analyzer Agent). A final Verdict Agent then analyzes these responses to reach a consensus event.

Watch on YouTube Full article

· 55:44

Introducing the SQL MCP Server - Jerry Nixon - NDC Toronto 2026

SQL MCP Server, an open-source component from Microsoft's data API builder, provides a secure and standardized abstraction layer for modern applications, especially those powered by AI agents. It allows external models to interact with enterprise databases (including SQL Server, PostgreSQL, Cosmos DB, and MySQL) without requiring direct T-SQL knowledge or exposing sensitive connection strings. The solution standardizes database access into three endpoints—REST, GraphQL, and MCP—simplifying the development process and significantly enhancing security by enforcing policies at the API layer.

Key takeaways

  1. Unified Data Access Layer 2:00

    The SQL MCP Server acts as a single point of entry for all data interactions, supporting multiple database types (SQL, NoSQL) and exposing three standardized APIs: REST, GraphQL, and the specialized Model Control Protocol (MCP). This abstraction layer allows developers to write code against the API surface rather than directly against the underlying schema.

  2. AI Agent Integration via MCP 8:00

    For AI agents, which cannot speak directly to a database, the MCP endpoint is critical. It collapses the potential hundreds of CRUD tools (one per table) into a standardized set of seven tools (Describe Entities, Create, Read, Update, Delete, etc.), preventing model overload and ensuring reliable agentic workflows.

  3. Simplified Development & CI/CD 3:00

    The solution aims to eliminate the need for boilerplate CRUD API code in a codebase. By using data API builder, developers can significantly reduce complexity and potential errors, streamlining the CI/CD pipeline while maintaining high functionality.

  4. Advanced Security & Policy Enforcement 10:50

    Security policies (like Row-Level Security) can be enforced at the API layer, even if structural changes are impossible in the underlying database. Furthermore, it supports advanced authentication methods like OpenID Connect and On Behalf Of (OBO) pass-through authentication.

Watch on YouTube Full article

· 16:33

The Best AI Automation Stack to Learn in 2026

The video outlines a comprehensive five-layer stack for building production-ready AI automation and engineering solutions. The recommended architecture emphasizes foundational software engineering principles—backend, database, frontend, AI models, and infrastructure—rather than relying solely on high-level no-code tools. Core technologies include Python/FastAPI/Celery for the backend, Postgres/Supabase for data storage, React/Vite/ShadCN UI for the frontend, and cloud providers (AWS, Azure, GCP) or specialized services for model integration and deployment.

Key takeaways

  1. Focus on Foundational Layers

    To build a career in AI engineering, understanding how to integrate core components—backend, database, frontend, AI layer, and infrastructure—is more valuable than mastering specific high-level tools.

  2. Backend Core Stack

    Python is the recommended language. FastAPI serves as the API entry point (handling GET/POST/PUT/DELETE webhooks), while Celery manages background workers and scheduled cron jobs, ensuring robustness and scalability.

  3. Database Recommendation 7:15

    Postgres is recommended as the primary database layer. Supabase is suggested as a wrapper around Postgres that simplifies authentication and provides an out-of-the-box admin GUI.

  4. Frontend Stack 12:00

    The recommended frontend stack is React (industry standard UI library), Vite (development server/bundler), and ShadCN UI (a component library for rapid, customizable development).

  5. Deployment Strategy

    For custom deployments, the industry standard is using Docker. For ease of use, platforms like Railway are recommended to simplify deployment setup (e.g., deploying FastAPI/Celery and React code). Advanced options include container services from major cloud providers or dedicated VPS hosting.

Watch on YouTube Full article