Status Updates From Building Microservices: Des...
Building Microservices: Designing Fine-Grained Systems by
Status Updates Showing 1-30 of 6,393
Catalin
is on page 159 of 616
An event is a fact, a statement that something happened, along with some info about what happened.
A message is a thing we send over an asynchronous communication mechanism, like a message broker.
With event-driven collaboration, we want to broadcast that event, and a
typical way to implement that broadcast mechanism would be to put the
event into a message.
The message is the medium, the event is the payload.
— Jul 05, 2026 11:34AM
Add a comment
A message is a thing we send over an asynchronous communication mechanism, like a message broker.
With event-driven collaboration, we want to broadcast that event, and a
typical way to implement that broadcast mechanism would be to put the
event into a message.
The message is the medium, the event is the payload.
Catalin
is on page 157 of 616
This means in request-response, the requester has to have knowledge of what the downstream recipient can do, with event-driven, the
emitter doesn’t need to know what any microservices are able to do.
— Jul 05, 2026 11:30AM
Add a comment
emitter doesn’t need to know what any microservices are able to do.
Catalin
is on page 157 of 616
The intent behind an event is the opposite of a request. The
event emitter is leaving it up to the recipients to decide what to do.
With request-response, the microservice sending the request knows what should be done and is telling the other microservice what it thinks needs to happen next.
— Jul 05, 2026 11:30AM
Add a comment
event emitter is leaving it up to the recipients to decide what to do.
With request-response, the microservice sending the request knows what should be done and is telling the other microservice what it thinks needs to happen next.