4
Domain Model and Asynchronous Events
When you're deciding on a communication pattern for an application, it is normal to look at the circumstances under which components may communicate with one another. Typical web applications follow a request/response pattern, where a request is made to the server and a response is returned to the client and handled appropriately. For applications looking to handle high throughput in those communication channels, a standard request/response pattern is not desired as each request would expect and wait for a response, leading to latency for requests that have been submitted while one is still processing. With hundreds of thousands of messages being sent per second, the application would be slowed to a halt ...
Get Implementing Event-Driven Microservices Architecture in .NET 7 now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
