Definition
Event-driven architecture organizes behavior around events: durable descriptions that something happened. Producers emit events, transport infrastructure makes them available, and consumers react without requiring the producer to control every downstream action.
Architecture
An event normally needs an identifier, type, source, time, subject and data. Brokers, queues or logs manage transport. Consumers update projections, trigger workflows or integrate systems.
Electronic Artefacts position
VASTE uses event propagation as part of contextual execution. Events should retain entity identity and relation context so that downstream behavior remains explainable.
Limitations
Consumers may receive duplicates, events can arrive late or out of order, schemas evolve, and replay can reproduce unintended side effects. Idempotency, versioning and observability are core design requirements.
References
See CloudEvents, Redis Streams, Contextual Execution and Graph Runtime.