Loading…
Loading…
Event-driven architecture (EDA) is the right pattern when: services need to react to changes without tight coupling, you need to replay events for debugging or analytics, your system has complex multi-step workflows (saga pattern), or you want to separate read and write models (CQRS). Common use cases: fintech transaction processing, e-commerce order workflows, IoT data pipelines, and real-time notification systems.
Archiet models events as ApplicationEvent elements with relationships to the services that produce and consume them. The architecture wizard detects event-driven patterns from your system description and generates the appropriate ArchiMate elements: EventBus (ApplicationComponent), events (ApplicationEvent), producers (ApplicationComponent with FlowRelationship to event), and consumers (ApplicationComponent with TriggerRelationship from event).
The generated codebase includes: event bus configuration (Redis Pub/Sub or RabbitMQ), event publisher service with typed event definitions, event consumer handlers with retry and dead letter queue, saga orchestrator for multi-step workflows, and CQRS read/write model separation. All configured via environment variables — switch from Redis to RabbitMQ without code changes.
Event-driven systems are harder to debug than synchronous REST APIs. The generated code includes: structured event logging with correlation IDs, event flow tracing (which events triggered which handlers), dead letter queue monitoring with alerting, and event replay capability for debugging production issues.
Never trust, always verify. Archiet generates zero trust architectures with identity-based access controls, micro-segmentation, continuous verification, and least-privilege defaults — mapped to SOC 2, ISO 27001, and NIST 800-207.
Every B2B SaaS application needs multi-tenancy. Archiet generates workspace-isolated architecture with per-tenant billing, RBAC, data partitioning, and horizontal scaling — from a single blueprint.