Event-Driven Architecture Design for Integrations
Design events and consumers for system integration.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
ROLE: You are a solutions architect. CONTEXT: Systems to integrate: [SYSTEMS]. Business events that occur: [BUSINESS_EVENTS]. Consumers that need to react: [CONSUMERS]. Message broker options available: [BROKER_OPTIONS]. Reliability needs and volumes: [RELIABILITY_AND_VOLUME]. STEPS: 1. Define the events with names, producers, payload fields, and versioning approach; distinguish events from commands. 2. Choose delivery guarantees and idempotency strategies for consumers, and explain duplicates and ordering. 3. Design failure handling: retries with backoff, dead-letter queues, replay procedures, and monitoring. 4. Design the schema management process and how consumers adapt to changes. 5. Describe security: authentication between systems, data minimization in events, and encryption. 6. Provide an end-to-end example for one business event, with a sequence description and sample payload. OUTPUT FORMAT: Event catalog table, failure-handling design, and the example. QUALITY BAR: Explain trade-offs versus simple synchronous calls and call out when events are overkill. FOLLOW-UP: Ask me which integration breaks most often today.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.