Event Driven Architecture With Pub Sub System For State Changes And Notifications

via “event system with typed event emission and subscription”

TypeScript framework for autonomous AI agents — multi-platform, plugins, memory, social agents.

Unique: Implements typed event system using TypeScript interfaces rather than string-based event names, providing compile-time type checking for event payloads. Event system is integrated into agent runtime, enabling event-driven agent interactions.

vs others: More type-safe than string-based event systems but less flexible; better for TypeScript-first systems than language-agnostic event buses.

via “event system with entity-scoped and global event publishing”

Entitas is a super fast Entity Component System (ECS) Framework specifically made for C# and Unity

Unique: Implements dual-scope event system with entity-scoped and global events, automatic subscription cleanup on entity destruction, and frame-synchronized batched dispatch

vs others: More structured than manual observer patterns and more flexible than direct method calls, with automatic cleanup preventing memory leaks

via “event-system-for-reactive-state-updates”

(Crystal is now Nimbalyst) Run multiple Codex and Claude Code AI sessions in parallel git worktrees. Test, compare approaches & manage AI-assisted development workflows in one desktop app.

Unique: Implements a typed event system that bridges main and renderer processes via IPC, enabling reactive UI updates without polling. Events are emitted by core services (SessionManager, WorktreeManager) and subscribed to by React components, creating a reactive data flow.

vs others: Provides event-driven state synchronization between backend and UI rather than polling or manual state management, reducing latency and CPU overhead while maintaining type safety.

via “mqtt-based event publishing for agent state changes”

A fast and minimal framework for building agentic systems

Unique: Integrates MQTT event publishing as a first-class framework feature, automatically publishing agent actions and state changes to structured MQTT topics without requiring agents to implement custom logging or monitoring logic

vs others: Lighter than centralized logging systems (ELK, Datadog) because it uses MQTT's pub-sub model; more decoupled than direct webhooks because subscribers don't need to be known at agent initialization time

via “event-driven architecture with pub/sub system for state changes and notifications”

** - Open-source local app that enables access to multiple MCP servers and thousands of tools with intelligent discovery via MCP protocol, runs servers in isolated environments, and features automatic quarantine protection against malicious tools.

Unique: Implements pub/sub event system for decoupled communication between components, with support for in-process and external event bus integration. Enables real-time notifications of state changes.

vs others: Provides event-driven architecture for reactive updates, whereas most MCP implementations use polling or require external event systems for state change notifications.

via “event subscription and notification”

Control SmartThings devices and scenes across your locations. Get live status and history, and send commands instantly. Automate routines by managing rooms, rules, schedules, and event subscriptions with real-time updates.

Unique: Utilizes a publish-subscribe model for real-time notifications, enhancing user interaction with their devices.

vs others: More efficient than traditional polling methods for event updates, reducing unnecessary API calls.

via “event-driven architecture support”

MCP server: pubnub-mcp

Unique: Supports a fully event-driven model by integrating with PubNub's event handling capabilities, allowing for seamless application responsiveness.

vs others: More integrated than traditional event systems, as it natively supports real-time event handling without additional infrastructure.

via “real-time event-driven architecture”

MCP server: demo-002

Unique: Employs a publish-subscribe model that allows for loose coupling of components, enabling highly responsive and scalable applications.

vs others: More efficient than traditional request-response models, as it allows for immediate processing of events without waiting for user input.

via “event-driven agent communication and messaging”

A multi-agent environment simulation library

Unique: Implements a typed event system where event schemas are defined declaratively, enabling compile-time type checking and IDE autocomplete for event payloads, reducing runtime errors from malformed messages

vs others: More flexible than direct method calls because agents don't need references to each other, enabling dynamic agent networks and easier testing through event mocking