Messaging & Event-Driven Architecture · question
Question 46 of 95
Explain the difference between events, commands, and queries.
← All Messaging & Event-Driven Architecture questions
Re-explain
These are three fundamental message types in distributed systems:
Events:
- Describe something that has already happened
- Named in past tense (OrderPlaced, PaymentProcessed)
- Multiple consumers can react to the same event
- Fire-and-forget nature
Commands:
- Represent an intention to do something
- Named in imperative form (PlaceOrder, ProcessPayment)
- Typically have one handler
- Can be rejected or fail
Queries:
- Request for information
- Don't change system state
- Return data to the caller
- Can be cached and optimized
Example:
Command: PlaceOrder -> Handler processes -> Event: OrderPlaced
Query: GetOrderStatus -> Returns current order state
Rewriting in plainer words…
This answer doesn't lend itself to a diagram - it reads best . No credits were charged.
Why there's no diagram: “”
The diagram below the answer is the concept .
Jump to it ↓
What should the new diagram focus on?
How well did you know this?
AI:
Saved in this browser - sign in to keep your review list.
How should your speech become text?
Listening… your words appear above as you speak - tap Stop when you're done.
Recording · cr - tap Stop & transcribe when you're done.
Transcribing with AI…
Voice:
Keep going - a few more words and AI can grade it.
Interview lens
Likely follow-ups, what you can say, and the weak answers to avoid.
Pro · $10/mo
82 of 95 Messaging & Event-Driven Architecture answers are in Pro.
Full answers, code samples, and AI explanations that go simpler or deeper. Cancel anytime.
-
Full answers + code
-
AI explanations, simpler or deeper
-
1,000 AI credits / month
-
Cancel anytime