Event-Driven Architecture for Agentic AI Systems logopeterindia.net
Knowledge Hub

Event-Driven Architecture for Agentic AI Systems

How to build agentic AI systems on events: design patterns, agent protocols, brokers and streams, event-driven agent runtimes and durable execution, with related pages on this site.

68 topics•7 categories•Updated November 19, 2026

Why Events? Foundations

4 entries

Core ideas behind event-driven design.

Event-Driven Agent Patterns

10 entries

Patterns for coordinating agents and keeping long workflows reliable.

Agent Protocols & Event Standards

5 entries

Standards for how agents, tools and events describe themselves.

Brokers, Streams & Schemas

13 entries

Infrastructure that carries and stores events.

Event-Driven Agent Runtimes & Durable Execution

12 entries

Frameworks and runtimes for event-triggered, long-running agents.

Related Technologies on This Site

19 entries

Event-driven, messaging and agent pages on this site.

45Event-Driven Architecture (EDA) HubEDA hub for 2026: patterns, event brokers and messaging, Apache Kafka, event-driven microservices, agent protocols and MCP, stream processing… 46Event-Driven Architecture (EDA) Design PatternsGuide to event-driven architecture patterns in 2026: publish/subscribe, message queues, partitions and consumer groups, delivery guarantees, dead… 47Event-Driven Architecture (EDA) ResourcesEvent-driven architecture resources: Fowler, Azure and microservices.io references, 24 guides and whitepapers, plus CloudEvents, AsyncAPI and Kafka. 48Event Brokering SoftwareDirectory of event brokering software for 2026: Solace PubSub+, IBM Event Automation, Apache Kafka and Confluent, Azure Event Grid and Event Hubs… 49Event-Driven Microservices: Guides, Tutorials & ResourcesGuides and references on event-driven microservices for 2026: architecture, best practices, Kafka and Spring Cloud Stream tutorials, outbox and event… 50Build Resilient Systems with Event Mesh SolutionsEvent mesh architecture and implementations: how Solace enables event-driven communication across hybrid and multi-cloud, versus Pulsar, NATS… 51Apache Kafka: Event Streaming Platform, Distributions & LearningApache Kafka resources for 2026: official docs, Kafka Streams, managed services (Confluent, Amazon MSK, Azure Event Hubs, Aiven), Redpanda, Strimzi… 52Message Queue SoftwareGuide to message queue software: RabbitMQ, ActiveMQ, IBM MQ, NATS, RocketMQ, Amazon SQS, EventBridge and Event Grid, Azure Service Bus, Google… 53Stream Processing FrameworksGuide to stream processing frameworks: Apache Flink and its Kubernetes operator, Kafka Streams, Spark Structured Streaming, Beam, ksqlDB… 54Streaming Databases: Real-time SQL on Data in MotionDirectory of streaming databases and real-time SQL platforms: Materialize, RisingWave, ksqlDB, Timeplus Proton, Hazelcast, Apache Flink SQL and more. 55Multi-Agent Orchestration FrameworksMulti-agent orchestration frameworks for 2026 by style: LangGraph, CrewAI, Google ADK, Microsoft Agent Framework, OpenAI Agents SDK, protocols and… 56Agentic AI Communication Protocols: MCP, A2A, Agent Client Protocol & MoreGuide to agentic AI communication protocols in 2026: Model Context Protocol (MCP) for tools, Agent2Agent (A2A) for agent collaboration. 57Model Context Protocol (MCP) Design PatternsGuide to Model Context Protocol (MCP) design patterns: direct API wrapper, composite service, MCP-to-agent and event-driven integration. 58Workflow Engines & Orchestration ToolsWorkflow engines and orchestration tools for 2026: Temporal, Apache Airflow, Camunda, Prefect, Dagster, AWS Step Functions, Argo Workflows and more. 59AI Agent Architecture: Production Principles and PatternsAI agent architecture in 2026: twelve production elements, tool contracts, memory, guardrails, evaluation and observability, plus six agentic… 60AI Agent Memory: Types, Layers and State ManagementAI agent memory in 2026: conversation, working and long-term memory and execution state, memory types, the memory loop, failure modes, tools and… 61AI Agent SwarmsAI agent swarms explained with Replit Missions: Mission Agreements, isolated environments, budget controls, evaluator agents, and how Factory… 62MQTT and Other Messaging Methods for the IoT EraDirectory of IoT messaging: MQTT 5.0 and Sparkplug, brokers (Mosquitto, EMQX, HiveMQ), CoAP, AMQP, DDS, OPC UA, Kafka, NATS and Zenoh. 63Real-World Use Cases of Apache KafkaGuide to nine Apache Kafka use cases in 2026: log aggregation, change data capture, event-driven microservices, stream processing, real-time…

Frequently Asked Questions

What is event-driven architecture for agentic AI?

It is a design in which AI agents communicate and are triggered through events, such as messages on a broker or stream, instead of calling each other directly. Agents publish what they did or learned, and other agents or services react to the events they care about.

Why use events instead of direct calls between agents?

Events decouple agents from each other, let many consumers react to the same fact, and, with a durable log, allow replay and audit. The sources in this directory also note costs: ordering, schema management and added latency, and several of them come from vendors that sell streaming platforms.

Which patterns are used?

Confluent describes four: orchestrator-worker, hierarchical, blackboard and market-based. Other guides from Anthropic, Microsoft, AWS and Google cover routing, concurrent and handoff patterns, and classic patterns such as saga, outbox and event sourcing help with long-running work.

What technologies are involved?

Event brokers and streams such as Kafka, Pulsar, NATS and the cloud event services, stream processors such as Flink, and runtimes such as Flink Agents, Solace Agent Mesh and Dapr Agents. Durable execution platforms such as Temporal and Restate keep long agent workflows running through failures.

How do A2A and MCP fit in?

MCP connects an agent to tools and data, and A2A lets agents from different vendors talk to each other. Event streams can carry the messages and state around both. Treat claims that a broker should sit under them as one architectural view, not a requirement of either protocol.