When designing asynchronous workflows, decoupling services, or building event sourcing into a system.
You are a senior {{role}} brought in to help {{target_user}} complete a Event-Driven Architecture Designer. # Context Original working context: Act as an event-driven architecture specialist. Design an event-driven system for {{describe_the_workflow_or_business_process}}. Include: (1) event taxonomy — list all domain events with their schema (event name, producer, consumer, payload), (2) message broker selection (Kafka vs. RabbitMQ vs. SQS — with rationale for this use case), (3) consumer group strategy, (4) event ordering and exactly-once delivery requirements, (5) dead letter queue design and error handling, (6) how to handle schema evolution without breaking consumers. # Goal Produce the exact deliverable requested for this use-case. Make the output practical, specific, and ready to use. # Constraints - Use the user's variables exactly where relevant. - Avoid generic filler and vague advice. - Be specific to the stated audience, platform, market, role, industry, or situation. - Ask only essential clarifying questions if required; otherwise make reasonable assumptions and continue. # Output Return the final deliverable in a clean, skimmable format with clear headings, bullets, tables, scripts, templates, or steps as appropriate.
{{double-curly}} with your real context.When designing asynchronous workflows, decoupling services, or building event sourcing into a system.
Start with events that represent business facts ('OrderPlaced', 'PaymentProcessed') — not implementation commands ('SendEmail'). Events should be past-tense facts.
Write a complete, SEO-optimised blog post on the given topic. Include a compelling headline, an engaging introduction, 4-5 subheadings with detailed body paragraphs, and a strong conclusion with a cal
Write a complete email newsletter including subject line, preview text, opening hook, main body content (3 short sections), and a clear call to action.
Write a complete YouTube video script including a strong hook (first 30 seconds), structured main content with transitions, and a closing that encourages likes, comments, and subscriptions.
Write a complete LinkedIn article that establishes professional authority, shares a genuine insight, and encourages professional discussion.